[0.80.0] Zwave issues with HomeSeer Devices

[jwelter1971]

Home Assistant release with the issue: 0.80.0

Last working Home Assistant release (if known): 0.79.3

Operating environment (Hass.io/Docker/Windows/etc.):Ubuntu with HA docker

Component/platform:Zwave

Description of problem: After upgrade to 0.80.0 all HomeSeer Zwave devices are no longer responding. The zwcfg.xml now shows them as an unknown manufacture and unknown device; where prior to the upgrade they were correctly reported.

Manually excluding these devices and adding back works temporarily (they respond and are correctly listed) but they revert to unknown again at the next HA restart cycle and stop responding.

All other Zwave devices seem to work working correctly with good response times and proper operation. The two devices are the WD100+ dimmer and WS100+ switch. About 40 devices show the exact same symptoms.

Zwave interface is a Aeon Zwave Stick G5.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

N/A

Traceback (if applicable):

N/A

Additional information:

[tomuta]

I seem to be having similar zwave issues recently, exactly like this with my devices (none of which are HomeSeer). I'm not sure when exactly it started, either since 0.72 or 0.80.0. It used to work flawlessly, and now it seems to "break" after a day or two. A restart of HASS seems to fix it temporarily for me, although zwave devices seem to be sluggish for a couple of minutes after restarting hass (sometimes taking 30+ seconds to respond, sometimes not responding at all).

[jwelter1971]

Hello,

I presume you are seeing log entries such as:

Z-Wave entity Unknown Node 119 Level (node_id: 119) not ready after 30 seconds, continuing anyway
12:09 AM components/zwave/__init__.py (WARNING)
Z-Wave node 119 not ready after 30 seconds, continuing anyway
12:09 AM components/zwave/__init__.py (WARNING)
Z-Wave entity Unknown Node 118 Level (node_id: 118) not ready after 30 seconds, continuing anyway
12:09 AM components/zwave/__init__.py (WARNING)
Z-Wave node 118 not ready after 30 seconds, continuing anyway
12:09 AM components/zwave/__init__.py (WARNING)

What devices are givingyou trouble as perhaps we can narrow it down?

In my case I have ecolink PIR and door/windows that work fine, some legacy GE switches that work fine, Schlage and kwikset locks working fine, and a couple Leviton switches working fine as well. What has broken is all of my HomeSeer and all my GE fan switches.

[tomuta]

I'll check my logs if I run into it again. Basically Leviton switches, dimmers, as well as one GE switch. It seems to affect everything, not just those, but I have to verify that first. I updated to 0.80.2 yesterday and everything was working fine this morning.

[jwelter1971]

Seems all central scene capable devices are the problem. Can someone with working devices confirm if they also see 0 scenes registered like below?

2018-10-17 18:08:40.122 Info, Node071, CentralScene - Created 0
2018-10-17 18:08:40.122 Info, Node077, CentralScene - Created 0
2018-10-17 18:08:40.122 Info, Node078, CentralScene - Created 0
2018-10-17 18:08:40.122 Info, Node079, CentralScene - Created 0
2018-10-17 18:08:40.122 Info, Node081, CentralScene - Created 0
2018-10-17 18:08:40.123 Info, Node084, CentralScene - Created 0
2018-10-17 18:08:40.123 Info, Node087, CentralScene - Created 0
2018-10-17 18:08:40.123 Info, Node090, CentralScene - Created 0
2018-10-17 18:08:40.123 Info, Node095, CentralScene - Created 0
2018-10-17 18:08:40.123 Info, Node096, CentralScene - Created 0
2018-10-17 18:08:40.124 Info, Node099, CentralScene - Created 0
2018-10-17 18:08:40.125 Info, Node116, CentralScene - Created 0
2018-10-17 18:08:40.125 Info, Node118, CentralScene - Created 0
2018-10-17 18:08:40.125 Info, Node119, CentralScene - Created 0

[tomuta]

I haven't had any issues whatsoever since upgrading to 0.80.0. I don't think there were any zwave related changes in between 0.72.0 and 0.80.0. It seems something unrelated must have caused these issues for me.

[jwelter1971]

I've dug a bit deeper and on device removal I get the following. This is for a Homeseer WD-100+ which is just a dimmer. It had only a single light entity created for it.

What I don't understand is all the ValueRemoved for unknown value with strange ID's.

018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596022456321}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596022456344}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596022456360}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596030844976}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596030844993}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596030861316}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596031713283}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596031762433}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596031762454}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596031762470}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106500}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106513}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106536}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106545}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106564}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106582}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106600}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106616}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106628}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032106646}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032417799}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032417815}) on node 118
2018-10-23 10:23:00 WARNING (Dummy-10) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057596032417831}) on node 118

[jvolkman]

I have a bunch of HomeSeer WS100+ and WD100+ that recently started misbehaving as well. OZW would show unknown nodes, and while some communication worked (remote control sometimes worked after a multi-second delay), OZW was constantly failing to send requests and retrying.

I finally fixed the problem by power cycling all of the switches. The dimmers are easy: just pull the air gap switch at the bottom and push it back in. For the switches I had to power cycle at the breakers. After rebooting all of the switches, the zwave network is normal and fast again. I have no idea what caused them all to get into this bad state.

[jwelter1971]

Thanks; I had tried this on a few devices and it didn't work but interestingly it seems to have but required me to power-cut ALL my HomeSeer devices to be offline together; and then power back up.

Simply power cutting a couple and bringing back online would cause the same issue to return almost instantly.

It becomes very apparent doing a grep of the OZW log for "Err" -- you can see the pattern of them dropping commands.

What is interesting is it was only the HS devices that did this; my other zwave and zwave+ devices all have remained happy; albeit with poor performance due to the network being slow with retries and such.

[tomuta]

Have you tried updating to 0.80.2? Since upgrading to this version, my zwave mesh has been working flawlessly again. I don't recall if 0.80.0 exhibited this problem for me as I only stayed on that version for a very short time.

[jwelter1971]

@tomuta Yes; now on 80.3 and the HomeSeer devices still have issues. As pointed out above to @jvolkman it seems power cutting to all of them and bringing back online solves it for awhile; but then it reverts back and the only way to recover is to power cut again.

On 78.3 I was rock solid; and thing working really nicely. No new devices added to my zwave network prior to going to 80.0.

Looking at the commit log it does seem quite some work on zwave was done in 80.0 where some new functionality added for adding/removing Values; which interestingly I see related log entries above.

The good news is I've replaced few of the offending HS devices with Lutron Caseta to keep the family happy and that has worked out really well; and lightening fast.

Interestingly all my other zwave works fine; locks; pir sensors; door sensors; and older switches -- it's only the HomeSeer; and ALL the HomeSeer that are impacted.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[tomuta]

Just ran into a zwave issue again (manufacturer independent), my zwave devices reflect the correct state, but I am unable to control them (e.g. turn lights on or off). I suspect it's all related to #14956 still not being fixed in 0.86.2. I believe some thread related to chromecast devices is locked up, which prevents some totally unrelated functionality from working properly.

[thomasvs]

I finally fixed the problem by power cycling all of the switches. The dimmers are easy: just pull the air gap switch at the bottom and push it back in.

What is the air gap switch at the bottom? Not finding anything that could match that, could you give me a clue where exactly?

[jvolkman]

You'll only find the air gap switch on dimers, not switches. It looks similar to this, but on the HomeSeer dimmers it's usually centered on the bottom.

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.