TradeFace
TradeFace
Well, I want to get rid of the mqtt-connection per device, but then noticed (working on another issue) that the will seems to work on a per connection basis. You...
Is the idea that all in the list will follow the `will_birth_topic` status? I think that could work. But how would you determine which is the actual `will_birth_topic`?
~~I don't think I fully understand how this should work.~~ ~~Let's say I have tuyagateway with one tuya devices connected. When the TG can't connect to the device it will...
Wouldn't it be easier to do it this way: - When **any** of the defined availability topics returns false ("offline"), the entity will be set unavailable. - When **all** of...
I understand that. But I think it is conceptually easier to understand with the method I proposed. When I want to implement a gateway without knowing anything about birth/will, I...
I might have incorrectly mapped the light. And assumed some of the values where in there ( and wouldn't trigger an error. In gismocaster you can go to Home Assistant...
@danVnest 'state_off': 'OFF', 'state_on': 'ON', are not in spec. https://www.home-assistant.io/integrations/light.mqtt/
> Is this intended? In what case would they be required? Nope, apparently the HA component definition isn't as consistent as I thought. e.g. https://www.home-assistant.io/integrations/switch.mqtt/ could use `state_on/off` as fallback...
It could be normal. Check the log levels https://github.com/tradeface/tuyagateway/wiki//Commandline-options
Okay, happy to merge your PR