[ANSWERED] Sync with Skip finding neighbor nodes during sync

Hello all,

I was wondering if my configuration is the only one with continuous troubles with Syncing.
My Z-Wave system has 40 different devices (and brands) but since more than 15 devices (almost 1 ½ year),
every new sync with a new Z-Wave device will be only included in Indigo when I switch on the
"Skip finding neighbor nodes during sync".
When I don't switch on this option, the module won't be included in Indigo and I got always the message;
"Timeout waiting for "xxx - xxx" Module might be asleep, or is unreachable".

Anybody an idea what this can be?

Kind regards,

John

[matt (support)]

Hi John,

Can you copy/paste the Event Log for the entire sync operation into a reply?

We have one other report of the same timeout. In large-ish networks where nodes have lots of reachable neighbors the "find neighbor nodes" step can take a very long time. I will look into increasing the timeout value Indigo is using.

Do you have any of the Aeotec repeater modules? I believe the other user that is seeing the problem does, so I'm wondering if that contributes to the problem.

Hi Matt,

Thanks for the fast reply.
For example: yesterday evening I synced the new Aeon Recessed Door Sensor (DSB54).
I don't use a repeater because I think the range of the modules is good enough.
(except some issues with my metal garage door and even a strange low battery issue with this Everspring sensor)
All the modules are working good, even with Skip finding neighbor nodes, some are 55 feet from the Aeon stick, outside of my house.

I just did a re-synced from the DSB54;
Below the log. The sync time was 1 minute and 46 seconds.
See also the strange battery messages.... (the Device info displays 100% battery level)

Thanks and greetings,

John



22 mei 2014 15:18:00
Z-Wave Syncing - started for device ”Door Garden”
Z-Wave Syncing - retrieved module neighbors list: 1, 9, 11, 15, 16, 17, 18, 22, 25, 27, 38, 41, 43, 45, 48, 54
Z-Wave Syncing - requesting neighbor list update of "058 - Door Garden”

22 mei 2014 15:18:23
Z-Wave Syncing - retrieved battery level of 45%
Z-Wave Syncing - assigning return route to "058 - Door Garden”

22 mei 2014 15:19:24
Z-Wave Syncing - retrieved battery level of 72%

Z-Wave Error Timeout waiting for "058 - Door Garden". Module might be asleep, or is unreachable.




22 mei 2014 15:24:39
Z-Wave Indigo Device "Door Garden" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.232
Node ID: 58
Model: Recessed Door Sensor (DSB54)
Model ID: 00020036
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 3.67
Application Version: 1.05
Model Definition Version: 1
Library Type: 3
Class Name: Binary Sensor (routing)
Class Hierarchy: 04 : 20 : 01
Command Class Base: 30
Command Versions: 20v1 80v1 84v2 85v1 86v1 70v1 30v1 72v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 1, 11, 15, 16, 17, 18, 25, 38, 54
Associations: 1:[1] 2:[]
Config Values: - none -

[matt (support)]

In the next version (6.0.13, not yet released) the timeout for that part of the sync operation will be much longer, which I believe will prevent the timeout error you are seeing.

The battery level temporarily dipping is likely because the module is having to send a ton of commands during the process of finding neighbors. After it rests the battery level jumps back up and reports a more normal value. We've noticed that lots of the Z-Wave modules don't report very accurate battery level percentages.

Thanks for the answer Matt.

the timeout for that part of the sync operation will be much longer,

Is it possible to show some details of this process in the Log?
Because more than 2 - 4 minutes waiting when nothing happens is a long time

Greetings,

John

[matt (support)]

Unfortunately, no. The Z-Stick and entire Z-Wave network goes silent from Indigo's perspective during the neighbor finding.

Just to chip in, I get this a lot too. Sometimes I sync or resync a device and it goes through straight away. Other times it hangs like John said and just comes back with 'Module might be asleep' even though it might be a powered device. I then have to choose 'Skip finding neighbour nodes' and it works. I bought the Aeotec repeater module thinking that my range wasn't good enough but it is the same behaviour with or without the module. Will wait for the next version.

Just chiming in to say I have two Aeotec repeater modules and about a dozen other Z-wave modules (all from Norm of course!) and lots of timeouts during "find neighbor nodes",

did you ever physically move a device? I had to exclude a device and then include it again. After that everything worked fine.
same when I had a device that did not sync, and I added another device after that. The not syncing device always timed out. Again after excluding then including everything was fixed.

[jay (support)]

It's been documented, but it's probably worth repeating here: when your Z-Wave network topology changes or you add devices, network routes can get messed up since the Z-Wave network uses static routing. To solve the problem, here's what we suggest: starting with the devices closest to the Z-Stick, redo the define and sync and allow it to locate it's neighbors. Do each device in turn and in order of increasing distance from the Z-Stick. This will allow the routing tables to get updated in each device in order of the number of hops it takes to get to the furthest device.

[matt (support)]

Indigo v6.0.13 is now available for download and includes a longer timeout duration for the sync process.

[matt (support)]

You are getting lots of corrupt packets coming into Indigo. Do you have the Z-Stick plugged directly into your Mac's USB port?

[matt (support)]

I think that is the problem. The Z-Stick is very susceptible to USB hub and extension cable woes, unfortunately.

[matt (support)]

Are you able to have Indigo sync with any of your Z-Wave modules?

Those errors look either like USB communication problems or a malfunctioning Z-Stick, but if that were the case I'd expect you would see errors when syncing most/all of your devices.