Z-Wave Wake-Up 'No More Info' Notification error sending to Node 62

[BobSpen]

Steve,
I get the following error in the log every so often. Happens only on a few devices that have direct connections to Z-Net. How might I go about fixing?

Oct-02 4:57:26 PM

Z-Wave

rgsV1Z-net: Z-Wave Wake-Up 'No More Info' Notification error sending to Node 62(Node 62 Z-Wave (Spare)FibaroFrontDoor-Notification Sensor Root).

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Device (Node 62) woke up and Poll Device for Node 62 Z-Wave (Spare)FibaroFrontDoor-Battery was successfully sent.

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Wake-Up Notification Processing for Node 62 (Node 62 Z-Wave (Spare)FibaroFrontDoor-Notification Sensor Root)

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Z-Wave Wake-Up Notification Received for Node 62

BobSpen

[SteveMSJ]

Steve,
I get the following error in the log every so often. Happens only on a few devices that have direct connections to Z-Net. How might I go about fixing?

Oct-02 4:57:26 PM

Z-Wave

rgsV1Z-net: Z-Wave Wake-Up 'No More Info' Notification error sending to Node 62(Node 62 Z-Wave (Spare)FibaroFrontDoor-Notification Sensor Root).

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Device (Node 62) woke up and Poll Device for Node 62 Z-Wave (Spare)FibaroFrontDoor-Battery was successfully sent.

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Wake-Up Notification Processing for Node 62 (Node 62 Z-Wave (Spare)FibaroFrontDoor-Notification Sensor Root)

Oct-02 4:57:18 PM

Z-Wave

rgsV1Z-net: Z-Wave Wake-Up Notification Received for Node 62

BobSpen

Hi
As you are probably aware that message is from the Z-Wave plug-in and has nothing to do with SDJ-Health. As far as I know it happens if the Z-Wave pi sends a queued poll to the device but doesn't receive a valid response before the device goes back to sleep.

I guess you have the Z-Wave pi set to automatically poll the battery child of the device. You can see that the device announced it had woken up and the z-wave pi immediately sent the poll request for the battery level. The warning was 8 seconds later and probably indicated that the device had gone back to sleep without responding to the request. Your send timeout is probably set to 8 seconds. This may have been due to congestion on your network or other issues affecting communications. If it only happens occasionally I wouldn't worry about it, but if it happens every time the device wakes up I would check that you don't have lots of polling going on or poor routing.

You probably don't need automatic polling of the battery child, although it doesn't normally matter as it's probably only once every 12 hours, or whatever your wake-up period is for the device. Most modern Z-Wave devices send their battery levels when they change without the need for polling, although you would have to check for your specific device.

I hope this helps,

Steve