Wanted to post this here since I know it’s affecting at least @denis and it’s hard to track in the other thread.
Since the update, I’ve lost all control of all my z-wave devices. Cloud integrations still work fine.
Most ominously, we both see some variables set to false that we’d rather not see:
zwaveHomeID: C58D3EEF zwaveNodeID: 01 zwavePowerLevel: full zwaveRadioDetected: false zwaveRadioEnabled: true zwaveRadioFunctional: false zwaveRegion: US zwaveSerialVersion: 4 zwaveSucID: 01 zwaveVersion: 3.83
I’ve rebooted, power cycled, disabled+enabled the z-wave module, all to no effect. We both have tickets open with support. I’ll update the thread with any news. Feel free to chime in if you have the same problem and make any progress.
Mine been out for days now and support is aware of the problem. Make sure you file a ticket with support and maybe it get to a higher level and get fix. It’s bad I move some of my Z Wave to another controller. I hope that they fix it soon. It’s hard to keep a positive outlook but I’m trying and keep waiting.
I had some of these issues before the upgrade, but are much worse now. I have a ticket opened on it. I get this in the logs now.
2016-04-22 6:41:42.865 AM MST
moments ago HUB zwdebug zw rsp 0x60: 01
2016-04-22 6:41:39.489 AM MST
moments ago HUB zwdebug zw rsp 0x60: 01
2016-04-22 6:41:32.116 AM MST
moments ago HUB zwdebug zw rsp 0x05: 14
2016-04-22 6:41:31.628 AM MST
moments ago HUB zwdebug zw rsp 0x15: 5A 2D 57 61 76 65 20 33 2E 38 33 00 01
2016-04-22 6:41:31.488 AM MST
moments ago HUB zwdebug zw rsp 0x17: 00
2016-04-22 6:41:31.382 AM MST
moments ago HUB zwdebug zw rsp 0x02: 05 08 1D A5 38 F1 F2 F3 FF 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00
2016-04-22 6:41:30.363 AM MST
moments ago HUB zwStatus starting up Z-Wave starting up
2016-04-22 6:41:29.453 AM MST
moments ago HUB zwStatus power cycle Z-Wave power cycle started
2016-04-22 6:41:29.359 AM MST
moments ago HUB Err 101: ZW module not respon… Err 101: ZW module not responding
You beat me to it! I was fishing for examples (links) for an identical post, while you clicked save on your post. Good idea!!!
@justintime can we generalize this thread to cover all z-wave issues post yesterday’s update. I am having issues with some devices but not all. And there are other folks in the same boat as me… (maybe changing the title to Z-wave issues post update 114.38?)
Same issue. I found it bizarre that Apps stopped working after the update. I had multiple devices dropped, and a few devices like a minimote not work anymore. I have the same variables set to off now which is likely what is causing the issues. Opened a ticket as well. I thought I was the only one last night. Frustrating!!
Support was able to fix me up – I had some orphaned devices that they removed, and then rebooted. I think there’s a few different problems in this thread, and mine one just one type. Specifically, I didn’t have the Err 101 problem.
Make sure you open a ticket with support if you’re having problems, they’re good about figuring out exactly which root cause you’re being impacted by.
I find it surprising just how many orphaned devices get created in my experience this has been maybe 10% of device removals get orphaned. It’s very annoying. This needs to be looked into
I am starting to think that’s my issue. I have a couple that are not orphaned, I think, but are a long distance, so they drop in and out. When I try to turn one on and off, zwave restarts and gets unstable for a while. That and repair fails 100% time now.
I seem to be having the same issues…unfortunately I am traveling out of the country. I had my wife reboot twice and I tried repairing z wave - still not right.
The app devices statuses are incorrect and change depending on screen with no change of actual device…
Did you do anything? Was the fix pushed out to your hub by support? Trying to figure out what I should expect. Came home to no lights today because none of my routines ran last night
