I thought it would be a good idea to run a heal with stress test, as I do not run the nightly heals and I wanted to see the signal quality to help me decide if I need to upgrade the antenna on my Vera 3
Big mistake. The heal finished about 5 hours ago, took 12 hours to finish, but I still had a lot of my battery devices with red banners, Unable to get information on node. That has now cleared on my StellaZ rad valves, but my garage door sensor and a few of my Fibaro window sensors still show the same. (They all have worked fine before the heal). That is the first problem, I thought over time that would sort itself out, but doesn’t look that way… I guess when I come back from work tonight I will have to try waking them all up manually and hope that’ll sort the problem.
The second problem is a plug in module which has the same error message. Again, it was working fine before the heal. It sits in a double socket, with another plugin module, which has 5 starts in the heal report… so no idea why that one does not want to communicate, nor of how to correct it as I cannot wake up a appliance module as far as I am aware
Restore from previous night’s backup.
It sounds like you do have some communication problems, as a heal should not cause this. A 12 hour heal process sounds like a huge network or a lot of battery operated devices.
On the other hand, if everything was working and starts working again after restore, perhaps no action is the best action.
It took another few hours, by the time I was back home everything was working normally again, with the one exception of my plugin module. Over the weekend I will exclude and include again, that should fix that problem. Luckily it is in only 1 scene so not too much aggro. I did not want to use the backup, as I must have had some problems, with devices being very slow to react on commands, which is now a lot better
I’m new to ZWave with a pretty small network (4 devices) and every time I’ve run a heal process it breaks most of my system. I haven’t figured out why yet, I just don’t run it anymore… :
I had problems with the nightly heals, so I turned that off. But after a while I had long delays on some of my devices, so I thought it might be time for a heal…
The problems you encounter are likely due to Vera choosing a routed communication path that is broken over the direct communication path. This is not uncommon when there is not a reliable mesh or devices that support routing e.g. not battery operated. The fix is to improve the mesh by adding more powered devices to fill “holes” in the mesh.
The problems you encounter are likely due to Vera choosing a routed communication path that is broken over the direct communication path. This is not uncommon when there is not a reliable mesh or devices that support routing e.g. not battery operated. The fix is to improve the mesh by adding more powered devices to fill “holes” in the mesh.[/quote]
So add more powered items and that will help? Is there anything I should look for in the specs for powered equipment to make certain it will help develop the mesh?
Thanks
Yes, more nodes result in a more reliable mesh and a more responsive network.
The feature you are looking for is routing. Most powered Z-Wave devices including switches, receptacles and plugin modules support routing and don;t advertise it on the box.
[quote=“Z-Waver, post:8, topic:181650”]Yes, more nodes result in a more reliable mesh and a more responsive network.
The feature you are looking for is routing. Most powered Z-Wave devices including switches, receptacles and plugin modules support routing and don;t advertise it on the box.[/quote]
When I pair a powered device to the network, where can I look to see if it indeed has routing?
If you look in the advanced tab of the device settings, in Autoroute you can see the routing to the device. Altid gives you the node number of the device. If there is a number your device is routing, and will show up in nearby devices as a node in autoroute (if the signals are routed through it)
Hope that makes sense
[quote=“mikee123, post:10, topic:181650”]If you look in the advanced tab of the device settings, in Autoroute you can see the routing to the device. Altid gives you the node number of the device. If there is a number your device is routing, and will show up in nearby devices as a node in autoroute (if the signals are routed through it)
Hope that makes sense[/quote]
Thanks, I think I understand.
If you wish to know if the device is capable of being a Z-Wave routing node, then look at the Capabilities field on the devices Settings tab. An R means it is a router, an RS means it is a routing slave. A B means it also supports Beaming which is important for routing to locks.