When I upgraded to 2.2.4.153, it seems to have almost completely broken the zwave capabilities of the device. If I run a zwave repair, it's gone after that and won't recover. I have to shut the device down, then power down the device and reboot it. Then basic commands work if I open the device, but rules and using the dashboards seem to break things pretty quick.
Hoping we can get some stable builds cause I'm starting to regret hitting that update button twice in a row now. I wonder if they had different update tracks for builds so that only stable working builds are released to the bulk of people. I really don't want these builds going out and tarnishing the name. Pretty sure we can get to a place where only stable builds are released but 2.2.4.153 is not it.
Seeing the same thing. Saw a bunch of weird messages about unparseable things in the logs. Rebooted but see z-wave pretty much nonfunctional now.
Thinking I will reboot once more and see if anything improves and if not try to revert to previous platform version — unless that would be ill-advised, @bcopeland?
Grabbed some screenshots from the logs. Note that the warnings are from the zooz motion sensor (ZSE40) built in driver. The errors are admittedly from my own drivers, but they had no issues prior to the update.
Whew! OK, so I reverted to 2.2.4.148, and it seems my Z-Wave mesh is starting to restabilize. At least, now the failed nodes will go "OK" when I click "refresh" and commands seem to be working again.
I think I will keep watching the feedback here. Reliability of my Z-wave Ecolink motion sensors is the backbone of my security system. No issues with them on 2.2.3.
I do have a new c7 hub arriving today, no idea what version it shipped with.
Just to be contrary, 2.2.4.153 is one of the best builds my mesh has seen on my C-7. There has been substantial self-routing improvement going on as I have just let it sit overnight, speeds have gone up dramatically.
I have one USB-powered Zooz ZSE18 motion sensor on a built-in Motion Lighting app, and I haven’t seen any errors from it, or errors from any other devices. The ZSE18 seems to be attracting devices like flies for repeating.
I’m sure i have now cursed it, and everything will blow up.
I had exactly the same issue but did not notice it until 2.2.4.156. I too managed to downgrade and though many zwave devices show up as FAILED and about half of them actually appear offline. I'm doing a zwave repair as we speak. What a total mess.
failed sometimes is normal after a complete power down till the mesh stabilizes and it sees events from all the devices.. Thats not to say that there are not issues with these releases..
I've definitely not seen this behavior with other releases. Right now I'm sitting on what appears to be a very broken zwave mesh. A zwave repair didn't seem to do much. 30% of my automations are not functioning, sensors not responding, stuff not reporting. At this point I'll take any suggestions to restore to something reasonably healthy.
If you are seeing problems after a platform update that don't go away within 20-30 minutes, The first thing I would recommend is to do a shutdown, remove power for a minute or two, and then restart.
My C-7 hubs seem okay so far but I haven't been having as many issues as some people on this thread (and others). My issues are with inclusion and after that only a few devices that seem a little funky - erratic/slow behavior but re-pairing them fixes. Almost like they get locked into a particular route and cannot adjust to the newer stuff around them.
Ironically it also does not seem to be responding to a safe shutdown! After a brute force power down I left it off for a few min and turned it back on. I am going to leave it overnight. Maybe that will give the zwave network a chance to heal. If I stay up working on this any longer it will be ugly. I haven't had this much fun since I was on Smart Things!
