Rebuild Z-Wave network with HCL3

[Rana 0]

Hi we have HCL3 installed on it many devices we want to put the devices on a new site so in this case we want to rebuild the network without changing the devices' IDs 
Will the lua  "fibaro:call(1,'requestNodeNeighborUpdate',1)" solve this issue, or does anyone have better ideas?

[Sankotronic 2,370]

Hi @Rana ,

 

what I would do is:

1. marked all removed devices where they were placed (e.g. motion sensor kitchen) so can go to the same location on new site. Not bad idea to make list with their ID numbers so, for devices that will go to some different location or be used for different purpose then will be easy to just change their name and location within the rooms on CH3L
2. Place HC3L on the best spot depending on the devices location
3. turn on HC3L and do rescan of the devices to rebuild neighbour list. (this will take some time, depending on number of battery operated devices)

 

BTW - if relocation will take some time then it is recommended to remove batteries from all battery operated devices to preserve them. Batteries are more quickly depleted if device can't find the gateway.

Edited November 24, 2024 by Sankotronic
added BTW

[Rana 0]

@Sankotronic
thanks for your answer 
but how can I make the  rescan of the devices can you explain the steps for doing this

[Sankotronic 2,370]

Hi @Rana,

 

Under the Settings and then Z-wave you should be able to find button. Remember that even if you manually start z-wave mesh reconfiguration it will still take some time, depending on number battery operated devices, since they need to wake up to refresh their list of neighbors.

[Barkis 1]

On 11/23/2024 at 1:08 AM, Rana said:

Will the lua  "fibaro:call(1,'requestNodeNeighborUpdate',1)" solve this issue

 

 

On 1/6/2025 at 6:54 AM, Sankotronic said:

Under the Settings and then Z-wave you should be able to find button

 

@Sankotronic, do you know if this button executes the function call in the original post? (I'm running a Z-Box Hub, which I understand to basically be a re-labeled HC3L, and it does not present this button on the 'Settings' tab. Thank you!

Edited April 24 by Barkis

[Brors94 115]

21 minutes ago, Barkis said:

 

 

 

@Sankotronic, do you know if this button executes the function call in the original post? (I'm running a Z-Box Hub, which I understand to basically be a re-labeled HC2L, and it does not present this button on the 'Settings' tab. Thank you!

The z-box hub is running z-wave engine 3 thats why it isnt there anymore (Never been therer for z-box*) 
 

[Barkis 1]

13 minutes ago, Brors94 said:

Never been therer for z-box

Right: never been there. At least since I got mine...

[Sankotronic 2,370]

Hi @Barkis,

 

z-wave engine 3 does not have button to force rebuilding mesh, since it does it automatically. If you still want to play with z-wave you can use Swagger and do it using Z-box API. 

[Barkis 1]

On 4/25/2026 at 3:21 AM, Sankotronic said:

since it does it automatically.

Yeah, that's what Z-Box has always done ever since I got the hub as @Brors94 correctly points out.

 

But something bugs me about the "automatic" action! 🤔 Since a Z-Wave mesh rebuilt typically takes some amount of time--and the caveat on hubs with the ability to trigger it manually usually warns the user of potential delays--how does one know when it actually occurs? What makes the hub think it needs to trigger a re-build? Does it "automatically" occur more often on hubs with a mesh that has some existing fault (even offline devices) versus a hub with a stable, well-built mesh and all devices active & accounted for? Can a mesh rebuild be scheduled to only run at times of little hub activity, such as the middle of the night when everyone is asleep?

 

My experience with occasional, intermittent delays executing, say, a scene that turns on several lights, with extremely long delays--a major annoyance to other family members--has led me to this as a possible cause. So, I am just exploring possibilities...

 

Thank you both for your thoughts...

[Brors94 115]

1 hour ago, Barkis said:

Yeah, that's what Z-Box has always done ever since I got the hub as @Brors94 correctly points out.

 

But something bugs me about the "automatic" action! 🤔 Since a Z-Wave mesh rebuilt typically takes some amount of time--and the caveat on hubs with the ability to trigger it manually usually warns the user of potential delays--how does one know when it actually occurs? What makes the hub think it needs to trigger a re-build? Does it "automatically" occur more often on hubs with a mesh that has some existing fault (even offline devices) versus a hub with a stable, well-built mesh and all devices active & accounted for? Can a mesh rebuild be scheduled to only run at times of little hub activity, such as the middle of the night when everyone is asleep?

 

My experience with occasional, intermittent delays executing, say, a scene that turns on several lights, with extremely long delays--a major annoyance to other family members--has led me to this as a possible cause. So, I am just exploring possibilities...

 

Thank you both for your thoughts...

Have you checked if you have a device that sends alot of massages?
Go to Setting ->diagnostic -> z-wave
 
(had a case where a device sent 9k massages the last hour a few weeks ago) 






 

[Sankotronic 2,370]

Hi @Barkis,

 

It seems that you didn't read my previous post carefully:

On 4/25/2026 at 9:21 AM, Sankotronic said:

If you still want to play with z-wave you can use Swagger and do it using Z-box API.

 

[Barkis 1]

On 4/26/2026 at 4:33 PM, Brors94 said:

Have you checked if you have a device that sends alot of massages?
Go to Setting ->diagnostic -> z-wave
 
(had a case where a device sent 9k massages the last hour a few weeks ago) 

 

Yes, done already. Lux sensors are particularly verbose, followed by motion sensors in our house. I tweaked their settings and reduced Z-Wave traffic by over a factor of ten. That seems to have helped...

 

15 hours ago, Sankotronic said:

It seems that you didn't read my previous post carefully:

 

Sorry I was not clear enough in my response. Yes, I've explored some of the functionality exposed in Swagger, in particular looking at device neighbors, etc.

 

But I've yet to find a way to log when--and how often--the hub thinks it needs to do a Z-Wave mesh re-build in the background without telling the user. It would be helpful to correlate that with scene execution that occurs tens of seconds after one clicks a scene controller button. 🤔