My little bug bear with my setup is that sometimes I have lights turn off slower than normal such as the bedroom lights at night I turn them off over 30 seconds to give light to get into bed.
My problem with this is that HASS updates the state as off as I turned it off but then checks status a couple of seconds later realises it is still on and updates the state as on which if there is an automation when the light comes on this is now triggered.
Ideally turning a switch off shouldn’t update status until the device is actually off.
I have this issue with certain ZWave lights. Some are older and require polling, and in polling during a transition to off state they will turn back on, but eventually they will show off when they are polled again.
These are older devices that do not support hail, for those who will attempt to point out this shouldn’t happen.
I have this with the Qubino Flush 2 relais since I migrated to the openzwave beta. Unfortunately these switches always required polling which was easy in the old openzwave integration.
Does anyone know if or when it is possible to poll nodes (or better specific entities) again as it was before?
The full detail of my problem nodes are Qubino ZMNHBD1 H1S5P1.
I’m afraid I need to look into replacing them all as they never seemed to have liked HA in the first place.
I have the same issue using milight bulbs that are a bit slower to repond.
While the messages are still being send to mqtt and received by the hub, the switch flips right back to it’s original state, only to move again to the prefered state when all mqtt messages are send.
Hit the off switch in the gui and home assistant instantly reports off but 2 seconds later comes back on if the light is still dimming out until it reaches full off then goes back to off state. Nothing to do with automations.
Annoyingly if I do have an automation to action something when the light turns on it gets triggered even know the light is going off not on.
This has been bugging me as well.
On the old Z-Wave integration you could simply set a device_config with refresh_value and a delay which would easily solve this issue, however I don’t see any way to do that on the new OpenZWave