Jump to content


Photo
- - - - -

OmniLinkBridge to integrate Home Assistant, SmartThings, Node-RED


  • Please log in to reply
124 replies to this topic

#121 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 2124 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 08 February 2019 - 03:08 PM

grantlewis, on 07 Feb 2019 - 13:58, said:

Looks like 0.87.0 only makes matters worse. In addition to the loss of thermostat control, 16 OmniPro flags, which were previously operating as switches in 0.84.6, are unrecognized.

...
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/mqtt/switch.py", line 66, in async_discover
...
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['brightness_state_topic']

Hmm. What's that all about? MQTT Switch does not even support brightness_state_topic. It's MQTT Light that supports it.
https://www.home-ass...ess_state_topic


I wonder if it has anything to do with this breaking change in 0.87:

Quote
MQTT platforms will now flag mistyped configs from configuration.yaml correctly as invalid, instead of just ignoring them. (@emontnemery - #20562) (mqtt docs) (breaking change)


In other words, in previous releases, if you included an invalid MQTT parameter (like specifying a brightness_state_topic for a switch component), it would simply be ignored. As of 0.87, it no longer ignores them.

Edited by 123, 08 February 2019 - 03:54 PM.


#122 rsw686

rsw686

    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 462 posts
  • Experience:guru
  • Software:Open Source Automation
  • Hardware:HAI OmniPro II
  • Tech:UPB, Z-Wave, ZigBee, 1-Wire, RadioRA2
  • Phone:Asterisk, FreePBX

Posted 10 February 2019 - 05:22 PM

Hmm. What's that all about? MQTT Switch does not even support brightness_state_topic. It's MQTT Light that supports it.
https://www.home-ass...ess_state_topic


I wonder if it has anything to do with this breaking change in 0.87:

In other words, in previous releases, if you included an invalid MQTT parameter (like specifying a brightness_state_topic for a switch component), it would simply be ignored. As of 0.87, it no longer ignores them.

 

I'm working on fixing this right now. Yes it has to do with the breaking change you noted. I was mapping units < 385 to light and units >= 385 (outputs) to switches. However I used the same config generator, which Home Assistant just ignored the extra values until now.



#123 rsw686

rsw686

    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 462 posts
  • Experience:guru
  • Software:Open Source Automation
  • Hardware:HAI OmniPro II
  • Tech:UPB, Z-Wave, ZigBee, 1-Wire, RadioRA2
  • Phone:Asterisk, FreePBX

Posted 10 February 2019 - 06:32 PM

I just released version 1.1.3 of OmniLinkBridge on GitHub, which fixes the above issue. Additionally I've updated my branches for the Home Assistant custom_components. Please note that Home Assistant moved them from climate and alarm_control_panel directories to mqtt. If you have the previous versions you will need to delete the old ones from your custom_components directory.

 

https://raw.githubus...mqtt/climate.py

https://raw.githubus...ontrol_panel.py

 

I'm going to try again to get the custom_component changes merged into Home Assistant's code base.



#124 grantlewis

grantlewis

    Cocooner

  • Registered
  • PipPip
  • 16 posts

Posted 10 February 2019 - 07:34 PM

Great work! Thank you.

Edited by grantlewis, 10 February 2019 - 08:58 PM.


#125 pete_c

pete_c

    Cocoonut

  • -=Gold Supporter=-
  • 8978 posts
  • Location:House
  • Experience:average
  • Software:Main Lobby, Open Source Automation
  • Hardware:HAI OmniPro II, Mi Casa Verde Vera, Ocelot
  • Tech:X10-PLC, X10-RF, UPB, INSTEON, Z-Wave, ZigBee, 1-Wire, xAP, xPL, ALC
  • Audio:Russound
  • Video:MythTV
  • CCTV:analog, ip, dvr
  • Phone:Asterisk, FreePBX, Ooma, POTS, VoIP via ISP

Posted Yesterday, 05:05 PM

Updated today to HA 87.1.  Running fine.  I am impressed with the changes I see.

 

Updated OmniLinkBridge to version 1.1.3.

 

Thank you Ryan!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users