I have noticed a ~1.5s delay between turning a z-wave switch on with openhab 3 z-wave binding and actually turning the light on. My network is currently a single light switch connected to a zw090-c aeotec z-stick gen 5 controlled by a rbpi 3 1gb. I am also using a proprietary gw by Keemple (Polish brand for OBLO) and their delay is so small that I cant even measure it. The switch reacts in an instant.
I also have a zigbee usb dongle cc2531 connected (~5 devices network). Is it possible that it slows down the serial connection to z-wave devices?
Now the main question: would zwavejs2mqtt over generic mqtt binding work faster than openhab’s z-wave binding?
Well I guess that zombie nodes are not possible in my case, because the network consists of a dongle and a single light switch. I also imagine that the signal is as strong as it may get, as the dongle is ~2.5m away from the light switch.
To get things sorted out, my z-wave network in openhab is kind of experimental, but I have paired my switch in a single attempt. I haven’t tried to remove any node yet, therefore I don’t think I have any dead ones.
Actually, upon further research, what confused me is that the zwavejs2mqtt Docker container also has their ws-server for websokets. MQTT is a publish-subscribe model and websockets are designed for bidirectional communication.
Their documentation is geared heavily toward home Assistant. Apparently their main developer works for an Italian IoT company.
I am starting to look at zwavejs2mqtt using their Docker container.
I traced the problem to the way the mobile application works. When I use the Models in web browser, the Things react instantly. When I use the mobile application, the delay is present. Seems like the mobile application is reconnecting to the server with every command.