This object is in archive!
Mesh Network Rebuild
Need Answer
Does anyone know where the "Mesh Network Rebuild" went in the new firmware? I updated to 1.0.17 and can't find that option anymore.
Found it. They moved it to the settings part of the Zwave network.
The same question
No connection
Real-time notifications may not work
It is located in the device manager tab now, next to the z-wave network name there is a "cog" icon
Sometimes it is good to update your network if you change device locations, or add devices to the network but not in the intended place. It can also help to determine or remove dead spots in the networking.
A remote is not a constantly powered device. Only powered devices form part of the mesh network. the remote works because it sends out a signal on a button push and whatever node is closest will pick this up and transfer the message via the mesh route the node is allocated.
It is located in the device manager tab now, next to the z-wave network name there is a "cog" icon
Sometimes it is good to update your network if you change device locations, or add devices to the network but not in the intended place. It can also help to determine or remove dead spots in the networking.
A remote is not a constantly powered device. Only powered devices form part of the mesh network. the remote works because it sends out a signal on a button push and whatever node is closest will pick this up and transfer the message via the mesh route the node is allocated.
Hi Nathan,
As I am new to Z-wave and Zipa-stuff, could you pls explain why you would need to force a rebuild of the Mesh (I suppose that is what this function does?). -I was under the impression that the devices constantly "rebuild" their mesh list, and that this is why e.g a bracelet emergency pushbutton will work all over the house?
Hi Nathan,
As I am new to Z-wave and Zipa-stuff, could you pls explain why you would need to force a rebuild of the Mesh (I suppose that is what this function does?). -I was under the impression that the devices constantly "rebuild" their mesh list, and that this is why e.g a bracelet emergency pushbutton will work all over the house?
It is located in the device manager tab now, next to the z-wave network name there is a "cog" icon
Sometimes it is good to update your network if you change device locations, or add devices to the network but not in the intended place. It can also help to determine or remove dead spots in the networking.
A remote is not a constantly powered device. Only powered devices form part of the mesh network. the remote works because it sends out a signal on a button push and whatever node is closest will pick this up and transfer the message via the mesh route the node is allocated.
It is located in the device manager tab now, next to the z-wave network name there is a "cog" icon
Sometimes it is good to update your network if you change device locations, or add devices to the network but not in the intended place. It can also help to determine or remove dead spots in the networking.
A remote is not a constantly powered device. Only powered devices form part of the mesh network. the remote works because it sends out a signal on a button push and whatever node is closest will pick this up and transfer the message via the mesh route the node is allocated.
Trying to understand/learn in order to get the most out of this, I have been roaming some other forums etc, looking for more details on this. It appears many other controllers do "Mesh Rebuild" automatically; some every night, others more infrequent. The caveat of an automatic rebuild, if done incorrectly, seems to be that passive nodes (such as many battery-operated nodes which sleep for a long time and only wake up when triggered or at their defined "ping time", may be marked as "dead".) The described positive results may be improved mesh utilization and increased coverage. Some comments describe a need for a Mesh Rebuild after deploying a node which was added close to the controller and then moved. Given that such "moved nodes" seem to act as repeaters after having been moved, even without any manual "rebuild", there's got to be some automatic mesh redesign going on...
Does anyone know if, and if so, how often, Zipabox issues a Rebuild Mesh command?
Trying to understand/learn in order to get the most out of this, I have been roaming some other forums etc, looking for more details on this. It appears many other controllers do "Mesh Rebuild" automatically; some every night, others more infrequent. The caveat of an automatic rebuild, if done incorrectly, seems to be that passive nodes (such as many battery-operated nodes which sleep for a long time and only wake up when triggered or at their defined "ping time", may be marked as "dead".) The described positive results may be improved mesh utilization and increased coverage. Some comments describe a need for a Mesh Rebuild after deploying a node which was added close to the controller and then moved. Given that such "moved nodes" seem to act as repeaters after having been moved, even without any manual "rebuild", there's got to be some automatic mesh redesign going on...
Does anyone know if, and if so, how often, Zipabox issues a Rebuild Mesh command?
@Adrian: I am sorry, but I am not sure whether I understood you right. Whta do you mean by "cog" icon? Ist the NETWORK HEAL function the right function the rebuild the mesh network?
Regards
Marcus
@Adrian: I am sorry, but I am not sure whether I understood you right. Whta do you mean by "cog" icon? Ist the NETWORK HEAL function the right function the rebuild the mesh network?
Regards
Marcus
Replies have been locked on this page!