Lost Z wave control

C7 hub
Coming back from vacation on June 25, all my automations were working properly. Updated the hub. Lost ability to control z wave devices. all my devices, except three are without security.
Hub receives info from the z wave devices. However, none of the automations work (actually, sometimes, something happens, much delayed). It is not possible to actuate a device digitally from the device page.
Updated the hub again (new firmware, twice in a few days) Currently at 2.3.2.134
Tried the following:

  • Repair. Unable to repair any device, except occasionally one device might be repaired.
  • Downgraded to firmware that used to work - no difference. Went back to latest
  • Soft reset - no result
  • shutdown, wait a few minutes, reboot - no result.
  • Safe Mode - This is the weird part. The hub is then able to control the devices WHILE in safe mode, at least for a while (lost the ability over night). Trying again, the devices can be controlled, for a short while, again, WHILE in safe mode. Normal reboot after safe mode does not fix anything.
    I am at a loss...

Thanks

@user327 When you shut down the hub, did you physically unplug the power? If not- do so for 5 mins and power back up.

2 Likes

I physically unplugged teh power. I actually left it without power for an hour or so as I had other things to do.

1 Like

Have you updated to the latest z-wave firmware? (this is different than the platform)

Yes I have -

And to complete the info, I have two ghost devices, one without authentication, the other S2. I am not able to get rid of them. However, the system was working with those devices prior to the updates (or whatever else happened...)

How about power cycling the devices themselves?

I had some switches acting up in a group that improved after I opened the breaker for a min and then powered back on. I don't know why but it was the last thing I tried.

Those ghost devices could still be interfering with your mesh. If you know the devices that made them, power down those devices and then reboot the hub and attempt the removal of the ghosts again otherwise you will need a z-wave stick paired as a secondary controller to remove them. Even those 2 ghosts can wreak havoc

I do not know what devices made them. I also resent having to buy a new device just to fix a problem that Hubitat should provide tools to fix. However, I seem to have solved the problem ... at least it has been "solved" for more than 12 hours... I disabled Rule Machine and re-enabled it. Just that. Everything works now, so far.
There are a few weird things though that I notice:

  • Hubitat says that Safe Mode disable the apps and drivers ... well, this was not the case. The apps worked (don't know about the drivers).
  • It would seem that the hub retains some memory of the status of Rule Machine even through a soft reset + data base restore, or a shutdown and reboot. Probably only Hubitat could confirm that.

Thank you for the help. I will post an update if things stop working again.

This is NOT a hubitat issue. This is caused by the SiLabs SDK. SiLabs need to correct it. As long as you have those ghosts though there will be problems or eventual problems with your mesh.. Also have you updated the z-wave firmware on the hub? This is separate from the platform update.

2 Likes

Just to expand on this in case you're new to some of this stuff, @user327, HE (like every other vendor using 700 Series Z-Wave) has to use the Z-Wave SDK provided by SilLabs. The behavior of Z-Wave devices and pretty much all rules of engagement are dictated by that SDK and accompaning T&Cs that HE and other vendors have to abide by. So while HE can (and has been) doing their best to work around limitations and issues caused by SilLabs SDK, there is only so much they can do.

There have been a couple SDK updates released by SilLabs in the last few months that HE has tested and released that have helped w/some ongoing problems. There is a another new SDK update being released "soon" by SilLabs that fixes some additional issues, HE will have to test and confirm it solves more problems than it causes, and then hopefully we'll get another Z-Wave SDK update that will further improve things for all of us.

5 Likes

Sooo... Things got bad again. the way I can get something working is by going in "Safe Mode". In these conditions, I can control the devices from the C7 interface and the Apps "kind of work". "Kind of" because Delays and Wait statements do not work. Other automations work. On motion, lights will turn on, but they will never turn off...
I purchased a Zooz stick and removed the two ghost devices. The problem STILL persists. No change whatsoever. This issue appeared when I upgraded from 2.3.1.142, though it does not mean it is because of this. I am now on 2.3.2.135. Going back to it did not solve anything.
More detail on the issue: it would seem the hub is very unresponsive. An "On" command may never go through, or may go through 20 or so seconds later, or more. I have tried to disabled ALL the applications in the Apps section, but the problem is still present. At this time the only configuration when the hub responds is in Safe Mode (with the limitations highlighted above).

Thanks

I know it sounds like a mantra around here, but can you share pics of your Z-Wave Details page?

1 Like

Yes, as @danabw please post your z-wave details page.

Please find the screenshots attached Part 1





And this is part 2


You have several really low speed devices.. That could be contributing to things. That said have you done a soft reset to clean up your database?

What apps do you have installed?

Under logs what do your device stats and app stats say? Anything really busy?

1 Like

Everything used to work fine ... and yes I did soft reset, shutdown, etc. I have a few apps installed: Action Tiles, Advanced Thermostat, Amazon Echo Skill, Button Controller, Denon HEOS Integration, Device Firmware Update, Goodnight, Groups and Scenes, Hub Link, Hubitat Dashboard, IFTT (disabled), Let's Get Started, Lutron Integration (disabled), Maker API, Notifications, Preference manager, Rule Machine, Webcore (disabled), Z-Wave Poller (disabled), Zone Motion controller, Zooz Garage door Opener (disabled).

Anything forcing your app or device stats to go through the roof? If not I'm gonna put it down to those several low speed devices

1 Like


Where is device 0x31? This device reported it as its route at one point, and has a seriously low transfer rate. I would do a repair on this device to force it to rebuild its routing neighbors.

4 Likes