Optimizing nodon crc-3-1

I have a nodon crc 3-1-0x remote switch.

nodon.png (14.56 KiB) Viewed 912 times

It is included in my network and synched to Indigo. It seems to work fairly well, but occasionally requires multiple button presses to do something. There are 2 nearby well connected Z-Wave devices, so connectivity from the nodon should be good. I figured it just needed optimization, and therein lies the problem...

Code: Select all

 Z-Wave                          Optimizing - started network optimization for nodes: 8
   Z-Wave                          Optimizing - starting "008 - Remote Switch"
   Z-Wave                          Optimizing - ping completed in 167 ms
   Z-Wave                          Optimizing - finding neighbors
   Z-Wave                          Optimizing - failed "008 - Remote Switch"
   Z-Wave                          Optimizing - complete
   Z-Wave                          Optimizing - update queued for next awake message: "008 - Remote Switch"


I can't get past this point. I try restarting inclusion mode on the nodon, I try sending ons and off, nothing seems to work. So, I have the following question(s):

1. Can you actually optimize wireless devices?
2. If so, how?
3. If not, how do wireless devices actually choose their route, or do they only communicate with the controller?

TIA

Matt... Jay... Any comments?

[matt (support)]

In berkinet's case the module responded to the ping command, which means it was awake, so Indigo send the command for it to find its neighbors but that failed. Indigo always pre-flights a "find your neighbors" command with a ping first to make sure the module is awake and reachable.

In lanbrown's case the ping failed (module probably asleep), so Indigo first tells all the neighbors to update their lists first, then it gets back around to telling the module itself to update and apparently Indigo never got response (which is odd – I'd expect either a success or a failure response). If the module was asleep I'd expect that to fail, then Indigo would add the module to its queue to try the processing again the next time it wakes. But it doesn't look like it gets that far from Indigo's perspective.

Basically, I'm not sure exactly what is going wrong with these.

Thanks to a 2+ year old post from howartp I was able to awaken the noon remote. But, that was all, it then quickly failed. Here's the log

Z-Wave Optimizing - started network optimization for nodes: 8
Z-Wave Optimizing - starting "008 - Remote Switch"
Z-Wave Debug SENT sendPingZwaveCommand: 01 09 00 13 08 02 00 00 25 3E F4
Z-Wave Debug RCVD sendPingZwaveCommand: 01 07 00 13 3E 01 01 9F 4A (node NAK)
Z-Wave Optimizing - ping failed (could be asleep)
Z-Wave Optimizing - finding neighbors
Z-Wave Optimizing - failed "008 - Remote Switch"
Z-Wave Optimizing - complete
Z-Wave Optimizing - update queued for next awake message: "008 - Remote Switch"
[This is as far as I was previously able to get]
Z-Wave Debug RCVD nodeInfoFrame: 01 1D 00 49 84 08 17 01 01 01 5E 85 59 80 5B 70 5A 72 73 86 84 EF 5E 5B 2B 27 22 20 26 84 07
Z-Wave Debug RCVD nodeAwake: 01 08 00 04 00 08 02 84 07 7A
Z-Wave Debug . . nodeAwake: node 008
Z-Wave Optimizing - starting for awake device "008 - Remote Switch"
Z-Wave Debug . . nodeAwake: inhibit count++ to 1
Z-Wave Debug . . nodeAwake: inhibit count-- to 0
Z-Wave Debug . . nodeAwake: stopping inhibit sleep timer
Z-Wave Error Optimizing - update failed: "008 - Remote Switch"
Z-Wave Debug SENT goToSleep: 01 09 00 13 08 02 84 08 24 3F 78
Z-Wave Debug SENT goToSleep: 01 09 00 13 08 02 84 08 24 40 07
Z-Wave Debug RCVD goToSleep: 01 07 00 13 3F 00 00 01 D5 (unsolicited while waiting for interface ACK -- requeuing)
Z-Wave Debug RCVD goToSleep: 18 (RETRANSMIT REQUEST)
Z-Wave Debug SENT goToSleep: 01 09 00 13 08 02 84 08 24 40 07 (re-sent because retransmit request)
Z-Wave Debug . . goToSleep: requeuing 1 unsolicited packets
Z-Wave Debug RCVD packet: 01 07 00 13 3F 00 00 01 D5 (hex)
Z-Wave Debug RCVD packet: 01 07 00 13 40 00 00 01 AA (hex)