I have recently moved all my Z-Wave devices from Fibaro HC2, to Z-Wave JS.
They work great!
But the Home Assistant UI is slow to update it’s gfx.
If I press a light button (dimmer), it turns on instantly (quick enough for me )
But the UI shows the light as off for around 7 seconds.
If i press the same light during these 7 seconds, nothing happens.
But when the light shows as on, I can press the button and it’s off instant both in RL and the UI.
So it’s only on turning ON. And only Dimmers, switches are instant in the UI.
Same thing happens on Scenes, Scenes are actually 10-100x faster than my Fibaro HC2 when it was able to do scenes without overheating back in 2015. They are instant, just like my button presses or UI. But if I use the “All lights off” scene, I have to wait til all lights are on in the UI before it works. Same 7 second delay. And when I run the “All lights off” scene, all lights go off in less than a second (not one after the other like in Fibaro) and the same happens in the UI.
My Home Assistant is running in a VM on a Unraid with 2 cores of a i9 GPU and 8GB ram dedicated.
To add to the mystery, whe using the physical button on the wall, the UI is almost instant (one second).
And I just found out that, setting a level is also instant. So if I set 20% the bulb in the UI is instantly on and same with the light. It’s just a lag when pressing the Bulb in the UI and with Scenes.
Hello,
Same issue here and this has happened since zwaveJS2mqtt was installed (approx 8 months ago). HS, zwave and all devices are operating properly. Response from when the dimmer is switched on from the UI to when the light turns on is fast. But the response from then the dimmer is switched on to when the UI shows it’s on takes about five seconds. This only happens with dimmers, zwave switches show they are turned on instantly. Does anyone know why or how this can be sped up?
As you can see in the screen shot, the light switch is pressed, the indicator momentarily turns on, then off, then a few seconds later the UI shows the light is on.
zwaveJS2mqtt installed in an external (on a different PC) docker container.
zwavejs2mqtt: 5.10.1
zwave-js: 8.6.1
Home Assistant: 2021.10.6
It’s normal, you can find many discussions here about the same subject. The refresh of the light level by the driver doesn’t happen until 5 seconds later. The UI times out after 2 seconds without a state change and returns to the original state. When you turn on a dimmer switch, it doesn’t know what level it turns on at until the fresh.
Additional comment; if you are using this device as dimmer, please check what transition time you have set for dimming. Device reports state change back to HA once the transition is complete, so the longer transition is, the longer it requires to see result in HA.
I observed similar behavior on FGD-212 (one I have) and also Aeotec Nano Dimmer. Fo my Fibaro it is controlled by parameters 5 & 6 (in automatic mode) and 7 & 8 in manual mode. The first parameter defines % of dimming in one step, the second duration of each step (in 10ms). So if you multiply these two you get the total dimming duration.
Thanks, and good point. However, I’ve reduced the transition time between levels to the lowest (10 ms I believe) and the physical light turns on almost instantly, but the UI indicator still takes 5 seconds.
Thank you as well. Yes, I imagine several others have expressed frustration with the current operation as it’s very confusing. My previous home automation system, HomeSeer, would set the UI device state for dimmers to 100% after commanded on, then after five seconds update with the actual dim level. IMO this was much more user friendly.
I’ve created a bug report for zwaveJS2mqtt on this as it seems like a usability issue. Hopefully this gains some traction with them. Turning the device indicator off makes it very confusing for the average user, and they will click the button again thinking the light hasn’t turned on.
Related question, I’ve just moved over my Fibaro dimmers to Zwave JS from a different hub (homey)
In Homey I had the transition time set very low (2s maybe, I don’t quite recall) and I see a noticeable difference in the turn on time in HA, maybe a 10s default?
Might be being blind but is there a way to lower this?
I’ve also noticed that the UI takes a while as mentioned above so dropping this probably (?) would help?
)