Refresh Z-Wave network?

[jojo1967 1]

I´m not shure, if "refresh" is the right work for this, but I included all my devices (window sensors etc.) in my living room with a laptop and installed them later in the other rooms. Maybe this was no good idea, because I read that the devices connect to the HC2 and to other devices nearby, to get a stable network.

Now I have some dead nodes in my HC2. I tried to exclude and include these devices again in the correct room, but I still have the dead nodes, although there are other devices with a repeater- / extender-function for Z-Wave nearby (Philio 4in1) which are still not marked as dead nodes.

Is there a function or or script in LUA to refresh the Z-Wave network? To be more exactly: A function, that all Z-Wave devices search for the next devices and the HC2 again without demounting and including each of them again....

[robmac 173]

process to refresh mesh on one device can take max 21m so you should do that timeout because if you gonna send too many request can this block controlling devices so let say you got 1 really dead device, so every 1 minute you will send request action

Thanks Andrew.

Think my script is OK.

The script I run leaves 30 mins per device update and it only retries the wake not the route update.

If it can not wake the device in three tries each three minutes apart it skips the route update as clearly there would be no point as there is no communication. I suppose I could try a full update in this situation.

I don't think this has ever happened or at least I have never seen in the debug that it tried more than twice to wake any node.

But most importantly is my summary of the calls correct? Is there any difference between the result of b) and c)

[ Added: 2014-06-03, 17:57 ]

Wouldn't c) also act as a) if anode=1 ?

Anyone's guess as there is no documentation but I don't think so as the version of the call on the controller node has 1 parameter whereas for all other nodes there is no parameter if you look at the JSON return of the API for the devices.

[ Added: 2014-06-03, 18:01 ]

for node 1

"actions":{"pollingDeadDevice":1,"pollingTimeSec":1,"requestNodeNeighborUpdate":1,"turnOff":0,"turnOn":0}

for one of my other nodes

"actions":{"pollingTimeSec":1,"requestNodeNeighborUpdate":0,"turnOff":0,"turnOn":0}

[A.Socha 133]

Please login or register to see this code.

yes

Please login or register to see this code.

yes

Please login or register to see this code.

do nothing

[robmac 173]

Thanks Andrew,

I will update my sleep to 21 + the max sleep time I have for any modules. I rarely see it running the scene.

BTW

there was a request for new format of scene triggers many months ago so you could set a scene to monitor for a change of a property for a range of ids or all modules rather than just one.

It would be ideal for this rather than having to loop all nodes every so many minutes.

Any update on progress on that?

[Dalle1985 16]

BTW

there was a request for new format of scene triggers many months ago so you could set a scene to monitor for a change of a property for a range of ids or all modules rather than just one.

It would be ideal for this rather than having to loop all nodes every so many minutes.

Any update on progress on that?

That would be a really elegant way of solving it! +1 for that!

[billykwan88 0]

Very nice topic!

I am not a programmer and I want HC2 to find dead node every minute, try to wake it and then update the routing for specific node without sending too many request that blocks other devices.

What code do I need? I have something like this now but it freezes the whole network.

Please login or register to see this code.

[Dalle1985 16]

If you read through the thread, you will see that if you call requestneighbornodeupdate before an earlier instance is timed out (which apparantly takes 21 minutes) it might make the system freeze.

Also, checking every minute might seem a bit exessive. My code only checks every 6 minutes as default and I've actually lowered it to 15 minutes now.