Open vvuk opened 3 years ago
Have you set the qos in z2m?
I saw similar behavior in hass with my aeotec dual nanos, they all started behaving a lot better after setting z2m config for mqtt to retain and qos 2.
I would suggest to set the qos to 0 and enable retain flag
QoS is set to 0 and retain is enabled. I saw in the z-wave log that there are some timeouts from this device; will dig into that too.
@vvuk Also keep an eye to: https://github.com/zwave-js/zwavejs2mqtt. It's very close to a first release
I've got a Zooz ZEN15 power switch for a high-wattage device. When I turn the device off via homeassistant, the device's state flicks back to on.. and only some seconds later goes back off. If I look at the zwave2mqtt logs I see this:
I'm guessing what's happening is hass sends the mqtt message to set the device to off. Homeassistant then refreshes the state of the device, and sees that it's still on -- or that the persistent state is still on (I need to go actually look at the physical switch to see how quickly the device responds). Some seconds later, there's a zwave timeout, and then the switch finally responds with the new state. Note that the power draw went to 0 watts within 2 seconds, so I think the switch actually responds fairly quickly; just the state doesn't get communicated.
I'm fairly new to doing zwave through mqtt -- I'm not even quite sure where to begin here. Any suggestions would be appreciated. Thanks!