I recently upgraded my Hubitat to C-8. "Most" of my previous attempts at firmware updates on the Inovelli(s) on C-7 had failed, so, I decided to give it another run on the new C-8. I realized that with S2 Authentication, the firmware updates were still a no-go. I excluded/re-included a couple of switches with Auth=None and then the following:
Sequence of events
On a LZW30-SN, update firmware using C-8 | App = Firmware Updater
The process takes 90 minutes and then finishes
Once Done, the device works fine & responds to hubitat interactions
Stops working after a few hours, automation starts to fail
Tried excluding, did not work, had to force remove
Tried inclusion, did not work
Did the 20 sec factory reset
Re-tried inclusion, did not work
Switch works manually, led responds (factory reset/inclusion/exclusion)
Many airgaps included in the above after step 4
As if one failure was not enough, I tried a second switch and landed the same situation - yes, I know, I should not have.
I found a couple of devices in Zwave Details that are in PENDING status. I am not able to remove them. Are these unresolved references to these devices causing my problem with not being able to exclude them?
[sys:1] 2023-03-05 07:10:13.453 PM
[info] Failed node 4F remove status:
0 SDK failure node is no longer in failed node list
[sys:1] 2023-03-05 07:07:03.255 PM
[info] Failed node 56 remove status:
0 SDK failure node is no longer in failed node list
When I run Z-Wave Mesh details, here is what I see
Update: Turns out this is due to "ghost" devices in the zwave details. On one of the switches, I was able to hit "refresh", cause it to surface the "remove", and then remove it. After that inclusion worked on that switch.
Now, I have a situation, where I have two "ghosts", any amount of "refresh", "remove" or even "reboot hub", "refresh", "remove" and even "remove" while air gapped, is not working.
How long does a "ghost" live in PENDING state? Any other ideas?
@rlithgow1@Rxich - Thank you very much! I got a zwave stick, installed parallels, windows 11, simplicity studio, zwave pc controller .... and was able to successfully remove the two ghosts using this document @Rxich shared. Again THANK YOU!
@bcopeland@bravenel - If this is possible with a complex contraption why is this not possible through the hub? While as a geek this was somewhat exciting to do, the barrier to doing this is so high!!
Because you're bypassing the SDK for lack of a better description. If Hubitat were to somehow build this in they would risk losing certification. Post your current z-wave details page lets see how it looks now.
why is this not possible through the hub? While as a geek this was somewhat exciting to do, the barrier to doing this is so high!!
