mirror of
https://github.com/excaliburpartners/OmniLinkBridge
synced 2024-12-22 10:42:24 +00:00
- Always enable first area to support Omni LTe and Omni IIe
This commit is contained in:
parent
ff02e1fd44
commit
23dd321f25
|
@ -310,7 +310,9 @@ namespace OmniLinkBridge.Modules
|
|||
{
|
||||
clsArea area = OmniLink.Controller.Areas[i];
|
||||
|
||||
if (area.DefaultProperties == true)
|
||||
// PC Access doesn't let you customize the area name for the Omni LTe or Omni IIe
|
||||
// (configured for 1 area). To workaround ignore default properties for the first area.
|
||||
if (i > 1 && area.DefaultProperties == true)
|
||||
{
|
||||
MqttClient.PublishAsync($"{Global.mqtt_discovery_prefix}/alarm_control_panel/{Global.mqtt_prefix}/area{i.ToString()}/config", null, MqttQualityOfServiceLevel.AtMostOnce, true);
|
||||
MqttClient.PublishAsync($"{Global.mqtt_discovery_prefix}/binary_sensor/{Global.mqtt_prefix}/area{i.ToString()}burglary/config", null, MqttQualityOfServiceLevel.AtMostOnce, true);
|
||||
|
|
|
@ -29,7 +29,9 @@ namespace OmniLinkBridge.WebAPI
|
|||
{
|
||||
clsArea area = WebServiceModule.OmniLink.Controller.Areas[i];
|
||||
|
||||
if (area.DefaultProperties == false)
|
||||
// PC Access doesn't let you customize the area name for the Omni LTe or Omni IIe
|
||||
// (configured for 1 area). To workaround ignore default properties for the first area.
|
||||
if (i == 1 || area.DefaultProperties == false)
|
||||
names.Add(new NameContract() { id = i, name = area.Name });
|
||||
}
|
||||
return names;
|
||||
|
|
|
@ -182,9 +182,10 @@ string ON
|
|||
```
|
||||
|
||||
## Change Log
|
||||
Version 1.1.4 - 2019-10-27
|
||||
Version 1.1.4 - 2019-10-28
|
||||
- Utilize controller temperature format
|
||||
- Ignore invalid temperature for thermostats
|
||||
- Always enable first area to fix Omni LTe and Omni IIe
|
||||
- Fix MQTT id validation and add notice for areas
|
||||
- Fix compatibility with Home Assistant 0.95.4 MQTT extra keys
|
||||
|
||||
|
|
Loading…
Reference in a new issue