How do we go about getting the hub to update neighbor listing for battery devices? I've added a fair number of repeating devices to my mesh since I first joined my battery devices, and all of their neighbor listings just show what was on the mesh, and they could see, when they first joined. So my locks, contact sensors, and motion sensors are all "wrong".
Is there some way to trigger a more thorough zwave repair that will query battery devices? Looking with my secondary stick and 3rd party tools I can see the battery devices talking to a lot more neighbors.
That said, I have no idea if it even matters. I'd still like to be able to get it updated though.
Anybody? Maybe add a second button for "Full Z-wave repair" with a warning that it could take a long time (since it will have to wait for devices to wake up)?
Battery powered devices may have a periodic wake-up schedule but many do not. Neighbors will end up being discovered over time. I recently added a Zwave non Plus contact sensor sitting beside me on the living room sofa. I then installed it outdoors where it is almost the furthest away from my hub. My home has steel siding so it is a faraday cage and could not possibly connect directly. The device registered the open and closed of the rear gate immediately. Using OpenZwave CP I can see that that sensor is 2 hops from the hub.
I understand, but with the z-wave poller app, i would hope those battery powered devices would be more active and hence we would be able to get their zwave neighbors updated.
Indeed. And I can see from other tools my locks know about a lot of neighbors, but Hubitat doesn't reflect that at all. they've been this way for weeks... so either the locks suck at reporting neighbors, or something else is wedged. =/
Looking at contact sensors, I do see they have updated their neighbors. So it's just the locks (maybe?) that aren't. =/
Battery powered devices can't be fired up remotely so they wouldn't be included in the poller app, or any other "app" looking for neighbors to feed to the battery device. That is what the hub does already.
Locks are a special case and because they are battery powered, the Zwave radio is not always powered on. It wakes every few seconds (not really sure how often) and calls home to see if something needs attention. Locks benefit from beaming capable neighbors. A beaming capable neighbor can store and forward a command from the hub that may have been missed while the lock was asleep.
The best thing to do with your Zwave devices, is to make sure you have line powered devices spread through your home. For locks, make sure you have Zwave Plus (beaming should be a part of most line powered Plus devices) opposite the lock. Being 5 feet away but on the same side of the wall doesn't make for a good neighbor.
It is difficult to "see" how things connect. I do wish there was a built in tool to report on neighbor tables and hop counts, but there isn't. There are tools and if you are interested you can add them to your setup.
Understood. And I have several beaming zwave plus devices around my locks now. And the locks show them as neighbors when using ozwcp or zentools, but hubitat does not show them as neighbors.
There are tools to do this, but you have to have a secondary controller to do it. which I have. Hubitat should be able to poll this information from the devices when they wake up. =/ or queue it to a beaming device to have them answer when they wake up...
In Zwave details each device shows “clusters”. While those don’t really map logically to devices listed, you can count how many there are and see how many neighbors hubitat knows about. My locks have had the same 5 since I installed them and before I added several Zwave plus (beaming) devices near them.
Maybe I’m misunderstanding what clusters actually are, but that seems to match up with other devices.
