You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.
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!
The text was updated successfully, but these errors were encountered:
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'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!
The text was updated successfully, but these errors were encountered: