See if the device works.
If yes, stop looking at the zwave details status and just use the device.
If it doesn't, try refresh.
If it returns failed, then you may need to remove and re-pair the device.
1 Like
1 Like
Oops...things got interesting some time last night...looks like overnight maintenance did some serious pruning of my Zwave devices. I guess the good news is that my ghost is gone along with them... 
It is funny that I"m still getting an hourly Z-Wave "Busy" message since 2:30 even though I no longer have any Z-Wave devices. Based on my log (above post) it looks like my Z-Wave devices were pruned around 2:15, which would line up w/the maintenance timing.
OMG...perfect.
1 Like
Do a cold restart. When posters above got this a restart fixed the list.
Yeah, I've already shut it down and am letting it sit unplugged for 30s. I am not too optimistic about my Zwave problems getting fixedd, other than maybe my devices may come back. Other cold restarts in the past few days haven't fixed my ongoing Zwave slow-down/lock up issues.
Yup - all devices back, including my ghost. 
I'm starting to become fond of the little bugger's persistentce...
lol just get ya that stick and delete it.
Yes 0x06 is a ghost node.
Yup, it's arriving tomorrow, assuming the gods of FedEx meet their expected delivery date. I'm going to name it my "particle cannon" and point it directly at my little buddy and blow him into protoplasm smithereens. Unless @bcopeland wants me to test/try some other HE-provided weapon.
If you were truly my friend you would have sent me your UZB several days ago. So selfish...
You should at least have your hub at node 1. Only way I was able to get past this on an out-of-the-box setup was to shutdown, power off for a while, power up, do a Z-Wave Radio Reset, then hub showed up as node 1.
Hub is at node 1, after cold restart. 
And all devices show OK, which they will do for a while (hours or minutes) before they fall into "Unknown" and are unreachable. That's been the pattern for the last several days. Things are working fine now, but like each other day I expect them all to stop working by some time in the afternoon/evening.
Rather than double post....
1 Like
When updating to version 2.2.3.135, it warned me that I should click on firmware update, within z-wave, and that this update would take around 10 minutes. When pressed, it does not take 15 seconds to get a message where it says that it is already updated. Do I have to understand that it is so?
The first 2.2.3 FW update included a Zwave radio FW update, so likely you already applied the Radio update if you installed the previous 2.2.3 release.
2 Likes
Ok, thanks.
01 is the HE hub. That one is there for everyone.
1 Like
The Z-Wave SDK indicates these states.. The hub interface is just reporting them .
2 Likes
If those are battery devices, then that is unfortunately normal display, but they usually work fine in spite of that.
If those are mains powered zwave devices, then you may have a problem.
You could try shutting down your hub, when the LED is red pull power for 30s, then plug back in again and see if it comes up and stays up w/powered zwave devices showing OK.
2 Likes
