I just installed the z-wave js add-on/integration (fresh install, i did not migrate from other z-wave intergrations). I am using a zwave.me uzb1 dongle.
I managed to add my z-wave devices: two Fibaro “dimmer-2” and two (battery operated) Sensative door/window sensors.
I have problems with the Sensative strips. If I keep them close enough to the z-wave USB dongle (say, one floor down), then close/open status is recorded correctly. But if I move the strips to where I want them to be (two floors down), then they don’t seem to reach/communicate with the z-wave USB dongle anymore.
However, one of the Fibaro dimmer-2 is very close to the Sensative strips (3 meters away, no walls). And this dimmer works / reaches the USB dongle: shouldn’t then the dimmer act as a repeater, and the Sensative “connect” through it? (I have waited 24 hours, in case it takes some time for the mesh network to build…)
Is there a map/topography tool that could help to understand what is the issue? Or any other ideas?
Hi diodorus,
How did you fix your problem. I have exactly same problem - 2 battery operated devices are very close to mains powered switches yet they insist on connecting (or trying to connect) to the controller.
Thanks
I’ve not seen a way of getting a network map out of Z-Wave JS, which is a shame as otherwise it works at least as well as openHAB which did “heal” the network and generate a visual topography map overnight.
A Fibaro FGD-212 dimmer is mains powered and does indeed act as a router (or it did under openHAB when a network map was last generated).
The Zigbee HASS integration has “Visualisation” tab with mesh map, so a Z-Wave JS network map may be added in the future. For now, all you have is the log which might help by showing timeouts.
You seem to understand the mesh radio distance issue well enough to know the difference between a mains device (“routing slave”) and battery (“slave”, non-routing unless a FLIRS - which is unlikely here), so my suggestion is the obvious one - buy additional mains powered devices to improve the mesh RF coverage.
Basically, Z-Wave and Zigbee all have the same issue - with only a few mains-powered devices, there’s not much of a mesh. More devices = better RF coverage.
The HASS integration does include a “Heal” control, so you might be able to force the “routing controller” to check the network coverage and generate a new route map to change the topography - the issue is this can take several hours! The controller has to “ping” every device and test mesh connectivity.
This process is automatic - you are no substitute for automated RF testing.
Another suggestion would be to update the zwave.me controller firmware - my previous RaZberry had issues for years with dead devices being unreachable (causes delay timeouts), until I created a RPi4 install of the manufacturer OS, updated firmware (~4x incremental releases), and removed the dead nodes.
This is likely to be lot easier with the USB controller as options like a PC are possible.