Multiple Z-Wave switches/dimmers now have COMMUNICATION_ERROR

  • I have been using OH for 4+ years. I’ve been using OH 2.4 for a couple of months.
  • I am using the Aeotech Z-stick Gen5. It has not been moved from it’s original location.
  • I am using the GE 12724 dimmers and GE 14294 switches
  • I have OH installed on a Synology storage device
  • I have about 14 dimmers/switches (hard-wired, obviously) and about 5 battery-operated sensors.

Today I noticed some of the devices were taking about 5-10 seconds to respond. I then realized some lights were not turning on at all - not even by toggling the physical switch.

I opened OH PaperUI and saw 4 devices that have COMMUNICATION_ERROR. These devices were not responding to any commands. I tried troubleshooting with one of them, removing, adding the device, with no luck. Below is from the event log:

2020-01-26 13:23:38.379 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2020-01-26 17:30:22.312 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to REMOVING
2020-01-26 17:30:22.350 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from REMOVING to REMOVED
2020-01-26 17:30:22.372 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from REMOVED to UNINITIALIZED
2020-01-26 17:30:22.662 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-01-26 17:30:44.716 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_zstick01_node22_switch_dimmer-zwave:device:zstick01:node22:switch_dimmer' has been added.
2020-01-26 17:30:44.716 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_zstick01_node22_switch_dimmer-zwave:device:zstick01:node22:switch_dimmer' has been added.
2020-01-26 17:30:44.776 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:zstick01:node22' has been removed.
2020-01-26 17:30:44.794 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from UNINITIALIZED to INITIALIZING
2020-01-26 17:30:44.804 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-01-26 17:30:44.807 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2020-01-26 17:30:44.886 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:zstick01:node22' has been updated.
2020-01-26 17:30:44.984 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:zstick01:node22' has been updated.
2020-01-26 17:30:45.047 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:zstick01:node22' has been updated.
2020-01-26 17:30:45.078 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:zstick01:node22' has been updated.
2020-01-26 17:49:24.748 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to UNINITIALIZED
2020-01-26 17:49:24.810 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-01-26 17:49:38.250 [temChannelLinkRemovedEvent] - Link 'LivingRoomLight => zwave:device:zstick01:node22:switch_dimmer' has been removed.
2020-01-26 17:49:38.522 [temChannelLinkRemovedEvent] - Link 'zwave_device_zstick01_node22_switch_dimmer => zwave:device:zstick01:node22:switch_dimmer' has been removed.
2020-01-26 17:52:49.423 [.ItemChannelLinkAddedEvent] - Link 'LivingRoomLight-zwave:device:zstick01:node22:switch_dimmer' has been added.
2020-01-26 17:52:49.658 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_zstick01_node22_switch_dimmer-zwave:device:zstick01:node22:switch_dimmer' has been added.
2020-01-26 17:52:49.658 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_zstick01_node22_switch_dimmer-zwave:device:zstick01:node22:switch_dimmer' has been added.
2020-01-26 17:52:50.643 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2020-01-26 17:52:51.719 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2020-01-26 17:52:51.730 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-01-26 17:53:05.574 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-01-26 17:54:36.536 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2020-01-26 18:01:26.076 [hingStatusInfoChangedEvent] - 'zwave:device:zstick01:node22' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE: Node initialising: REQUEST_NIF

I restarted OpenHAB which didn’t help. I also unplugged the z-stick and plugged it back in; again, no luck.

I came across (SOLVED) After a restart, most Zwave nodes are stuck on REQUEST_NIF. But the OP’s solution was to reset everything and start from scratch. Not exactly something I want to do.

I also came across [SOLVED] openHAB 2.4 Z-Wave Dimmers update issue Add-ons. However, I’ve been using 2.4 for a couple of months with no issues. I still read through the replies. Some of the suggestions include (1) change the “Command Poll Period” from 1500 to 3000 - didn’t help, (2) having to update the channel names due to some undocumented changes - did not apply to me, the channel did not change, (3) unplugging the z-stick and plugging it back in - already tried it, no help.

I’m a little hesitant to delete the Z-wave binding and adding it back in. Will it install a 2.5 version of it? I’d rather hold off on doing this (and hold off on updating to OH 2.5 for now).

If the switches are not working when toggling the physical switch, could it be the switches? Could 4 die on the same day? Finding this hard to believe, I even made sure the light bulbs are in fact working (they are working fine…not burnt out).

One of those posts suggested maybe the z-stick is failing. But would it only affect some devices/nodes and not others?

What can be causing the COMMUNICATION_ERROR? What else can I do to troubleshoot?

Thanks!

If they don’t work at the actual switch then it likely isn’t a software issue. I’ve had about half of my GE switches die on me so far, though 4 at the same time is suspect.

If you are in North America, Zooz may be a good option. Their support is stellar and they have worked with us to get their products supported in OH. Their store is at thesmartesthouse.com .

One of your devices may have developed a fault, or something else may have been introduced in your neighborhood, partially jamming your zwave radio network.
No amount of fiddling with configs or reloading bindings will fix this. (only introduce new opportunities to add mistakes)

2 Likes

Shutdown the hardware running OH. Unplug/plug in the controller. Pop the air gaps or unplug/plug in all mains powered devices, then power them back up. Then start OH up. Once settled, perform a network heal. This is standard maintenance for the network.

Cause could be a bad device, or just one that’s fallen over. You could also throw the breakers, which should also be done periodically, rather than cycling the power on all the devices.

Bruce_Osborne, yes, I am in the US. I’ll definitely check it out. Thanks!

feens and rossko57, I hope that’s not the case :frowning:

5iver, I turned off the hardware running OH and unplugged the controller. I’m not sure what “pop the air gaps” means so I just switched the breakers off and on. I started up OH again, waited several minutes, then performed a network heal. Unfortunately, these 4 switches are still not doing anything.

The odd thing is, I’m trying Aeotec’s IMATools.exe and Zenzy Tool’s ZWaveController.exe and they both see these nodes, but if I try to send the on/off command, I get a failed response.

IMATools:

20200127-19.30.41.410 Starting Z-Wave Network Health for Node 022
20200127-19.30.48.722 Route quality - Stable (0), uniq LWR TRUE
20200127-19.30.48.770 Node 022 test 000 Failed... Latency 6740 ms
20200127-19.30.48.802 Node 022 LWR - NONE [0x00, 0x00, 0x00, 0x00 at Auto]

Zenzy Tools:

07:32:56.425: SecurityManager.Init 60 24 38 46 16 50 74 C4 80 D9 10 A8 30 5B 90 08 
07:33:12.026: Request failed: 07:33:12.025: BASIC_SET failed. CompleteNoAcknowledge received

Is there anything else I can try before I throw in the towel and consider these dimmers dead?

Look at page 14 in the manual… https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/43.

The air gap is a way to quickly and easily physically disconnect the wiring of the switch. For most switches/dimmers, you push in at the top and the bottom pops out. Sometimes it is a separate little button.

Before tossing them, I’d exclude and reinclude, although I think you may have tried this (maybe you only deleted the Things?). The odds of them all dying at the same time is very small, unless there was some kind of power fluctuation that they couldn’t handle.

Also, I would update to OH 2.5.

Wait a minute… I just saw this…

If the switches do not work when physically toggled, then there is an issue with the switches or the wiring. Do the LEDs on the switch light up (assuming they have them)?

Nope, they’re not working when physically toggled. Yes they have LEDs but are not lit. I checked with a voltage tester and they are all live. Even so, four suddenly having wiring issues?

Node22 that I’ve been referencing here in the log entries is in a 3 gang box. Node22 is a dimmer for lights in a. Another dimmer in the 3 gang box is for the fan itself (actual fan specific dimmer) and that one works fine. The 3rd is for a 3-way switch and that one is working fine too.

Ha!!! I thought this little tab was just to swap out the paddle switch cover (since they come in white and almond).

I pulled the tab out then checked with the voltage tester…no beeps at all. I pushed the air gap tab back in and the voltage tester beeped when I put it up to the dimmer. Still nothing, no LED, lights won’t turn on when physically toggled.

Tomorrow I will turn off breaker again, check wiring, and if still not having any luck, swap it with a dumb switch just to conclusively confirm nothing is wrong with the wiring.

I did try to exclude and reinclude, but I have to toggle the switch to do so, and, well, it’s not responding.

:+1:

Sounds like there was an electrical problem with these devices or the wiring. Be safe… and if you don’t know how to be safe, call an electrician!

1 Like

A set of four going loopy, that is curious.

It is possible these particular devices have a design weakness about a power line spike or somesuch.

That might have corrupted internal settings rather than actually destroyed anything. Or some piece of software may have sent bad settings, or perhaps a failed update.
Is there a means to invoke a “factory defaults reset” on these devices?

If the devices are not switching load from physical toggling, there’s more wrong that software.

1 Like

My very first Zooz switch physically would not turn off within 24 hours of installation. Support rushed out a tested replacement that has worked well for months.
I also like supporting a company that helps us support their products in OH. There was an old unsupported version 1 of a product in our database missing information. Even though unsupported they provided the missing information.

Checking out the Zooz Zen22 dimmer light switch. At $20.95/ea., it’s definitely a better deal than the $35 GE/Jasco…x4.

How are their motion sensors?

I have a ZSE18 that can be USB or battery powered. Be sure you are using your final power selection when including into the network. My only major complaint when using ir battery powered is that the included manual is incorrect. Instead of one button press to wake up, it takes 3 presses. After that the light blinks and I usually press 3 more times to cancel that.

Quick update…

I replaced the 4 switches and they are all working. Not sure what caused them all to die pretty much at the same time.

Another thing I learned: all these 4 are from the same breaker, however, other z-wave switches are as well and those are fine.

Very strange!

1 Like