Hello, I'm suddenly getting these busy messages in the log, and nothing is working. It's pretty much brought the hub to its knees. How can I fix this?
I've just tried reverting to 2.3.9.136 and the busy messages still keep coming.
I've shutdown, unplugged for 30s and rebooted. Still under assault.
The power down normally should fix it.
What does your Z-Wave details look like? A pile of new ghost nodes at the end maybe?
Were you attempting to add a new device via Smart Start (long range maybe?)
If yes to adding a device, remove its entry from SmartStart.
I haven't done anything to the hub in a couple months at least except update the platform. No new devices or removing or anything.
There is only 1 unlabeled device in Z-Wave Settings. I am admittedly less familiar with the new Z-Wave settings page since C7. I see "Discover", which doesn't work. Repair doesn't work either.
You might be able to click refresh, then remove once the refresh is done. It may remove it but probably not while the busy errors are spewing out. One ghost should not cause that much trouble.
2.3.9 had some major back end Z-wave changes to accommodate Long Range support.
I would take a backup and then roll back to 2.3.8.140
If you have created any of the new EZ Dashboards they will be deleted when you roll back, otherwise it should not hurt anything else.
If 2.3.8 does not work, then I am leaning towards some sort of hardware failure.
How is the hub being powered? Supplied power block or something else? PoE?
Powered via wall.
I eventually got the Remove option, but it failed as well.
Trying 2.3.8 now.
I just pulled this puppy out just in case. I've completely forgotten how to use it though.
1 Like
Is it using the supplied power brick and cable, or a different brick and/or cable?
Hopefully the rollback to 2.3.8 works!
Hrm. No dice with 2.3.8. Yes, using the supplied power brick and cable.
1 Like
Hub Protect?
Could do a radio reset and then restore from cloud backup (requires hub protect).
Next step would be to file a warranty claim if you have hub protect.
Bummer.
No hub protect.
RIP
Could be recoverable but I have never seen that happen before so no idea what it could be besides hardware failure.
There is a chance a radio reset would bring it back, but you would need to pair all your devices again (and rename the DNI of all the old ones first). There is also a chance someone from staff might have another idea that does not involve resetting the radio.
Maybe try a different power supply? The Z-wave radio is very sensitive to power issues.
I've been meaning to transfer everything to the new C-8 anyway. Just not... now...
Here are the instructions for a manual Z-wave migration if you need them. 
You can also now use Swap Apps (new since those instructions) instead of the later part of switching the DNIs around. I probably wrote some instructions on how to do it with Swap Apps somewhere but its almost the same procedure with maybe a few less steps.
1 Like
not so fast
Noticed a Zooz XS tilt sensor acting up:
I removed it and the busy signal has stopped... Let's see what happens if I add it back.
1 Like
That thing must have been pounding on the radio. Never seen one device jam it up so quick.
What diver are you using for it?
a brush with death
How odd... Never expected this little sensor to be the culprit. I don't think I was using any special driver. Looks like there's a newer firmware though, I might do that.
