Zwave: Node Not Communicating With Controller - Help to Fix

Add-ons Bindings
1

I have two issues:

Primary issue is that my HS WD100 dimmer switch is not “Node is not communicating with controller”(Habmin and PaperUI)

I’ve tried multiple remedies other than trying new physical switch. It physically works fine. I’m running OH2.5 Snapshot and updated recently. I’ve tried following somes instruction on removing the device(exclusion) from controller but it doesn’t seem to work. Everytime I remove the device, it keeps showing back up when I try to add it without pressing any button on the switch.

I’m stuck. Here’s a log excerpt: (I forget how to format the log to get it work with with Chris’s log viewer)

2019-03-10 19:57:53.712 [me.event.ThingUpdatedEvent] - Thing ‘zwave:serial_zstick:15da5b25003’ has been updated.

2019-03-10 19:58:02.065 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:15da5b25003:node4’ has been updated.

2019-03-10 19:58:09.891 [hingStatusInfoChangedEvent] - ‘zwave:device:15da5b25003:node4’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to UNINITIALIZED

2019-03-10 19:58:10.056 [hingStatusInfoChangedEvent] - ‘zwave:device:15da5b25003:node4’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

2019-03-10 19:58:19.221 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node12’ has been removed.

2019-03-10 19:58:19.232 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node10’ has been removed.

2019-03-10 19:58:19.243 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node13’ has been removed.

2019-03-10 19:58:19.248 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node11’ has been removed.

2019-03-10 19:58:29.185 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node4’ has been added.

2019-03-10 19:58:29.185 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15da5b25003:node4’ to inbox.

2019-03-10 19:58:29.210 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15da5b25003:node10’ to inbox.

2019-03-10 19:58:29.210 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node10’ has been added.

2019-03-10 19:58:29.277 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15da5b25003:node11’ to inbox.

2019-03-10 19:58:29.281 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node11’ has been added.

2019-03-10 19:58:29.293 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-03-10 19:58:29.299 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15da5b25003:node12’ to inbox.

2019-03-10 19:58:29.305 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node12’ has been added.

2019-03-10 19:58:29.306 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-03-10 19:58:29.311 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15da5b25003:node13’ to inbox.

2019-03-10 19:58:29.314 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node13’ has been added.

2019-03-10 19:58:45.687 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:15da5b25003:node4’ has been removed.

2019-03-10 19:58:45.722 [hingStatusInfoChangedEvent] - ‘zwave:device:15da5b25003:node4’ changed from UNINITIALIZED to INITIALIZING

2019-03-10 19:58:45.728 [hingStatusInfoChangedEvent] - ‘zwave:device:15da5b25003:node4’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2019-03-10 19:58:45.734 [hingStatusInfoChangedEvent] - ‘zwave:device:15da5b25003:node4’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

2019-03-10 19:58:45.737 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:15da5b25003:node4’ has been updated.

2019-03-10 19:58:45.751 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:15da5b25003:node4’ has been updated.

2019-03-10 19:58:45.753 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:15da5b25003:node4’ has been updated.

2019-03-10 19:58:45.824 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:15da5b25003:node4’ has been updated.

(Edit: I did a hardware reset on my Aeotec Z Stick and that resolved my problem, but a somewhat drastic solution)

2

Yes, that does seem a bit drastic.

The directions on how to do that are here. If the problem still exists, you can post the debug log and we’ll help you find out what’s going on.

3

I think I have the same issue. It started after upgrade to OH 2.5 stable. I’m using aeotec zstick as controller. I reset it and readded all nodes. The reset was before the first node went bad. So after first node went bad I reincluded it in the network and it works for now. But today two other nodes went bad. Habmin says they are not comunicating with the controller.

This is the log when I try to send ON command:
node_not_comunicating.log (11.8 KB)

4

I realized that before last two nodes went bad I disconnected power to them. For the first node that went bad I don’t remember but it is possible that it was the same case. So maybe it is related … It is like the node reseted itself, all nodes are philio pan06 (https://www.zwavetaiwan.com.tw/pan06)

5

I also checked if something Will show UP in logs when i turn on/off the node with button but nothing showed UP. Also the node was not exclueded nor reseted because it would flash its Led - the Led was not flashing. I had to exlude it and include it again. After that it is working. Next Time i Will check with external tools if the node is Talking to the controller.

6

I’ve had similar issues ever since upgrading to 2.5 release. Randomly 90% of my devices are “not communicating with the controller” and I need to restart the zwave binding to get anything working again. I’m honestly to the point where I want to see if I can somehow roll back the upgrade or install the older working version.

7

Have you been moving mains powered devices around, or do you have any that are not plugged in?

Try disabling your daily heal (found in the controller Thing settings) and restarting OH. When adding devices, you may need to manually heal your mains powered devices, possibly some battery too, to sort out your mesh. There are a couple known and possibly related issues that have been reported…

8

I moved a zwave lightbulb from one room to the next, and added two new switches yesterday but that’s it. I’ve disabled the daily heal, I’ll see if that helps. Come to think of it, the devices showing not communicating seems to be in the morning so maybe the daily heal is indeed a culprit.

9

I have disabled network heal after first of my nodes went offline. The next to went offline when automatic healing wast turned off.