One is listed as some sort of "generic type window covering" what ever that is. Never had such a device.
I think one is a fibaro FGK-10X fw 3.2 door / window sensor.
I think you may be correct about the duplicates, one is probably duplicate of the Fibaro FGMS-002 that I excluded & then included which is not reporting details fully. May be best to exclude that & re include again.
Exclude the working one, take out the batteries, try to remove its ghost first. Once your ghosts are all cleared up then re-include it. And if you can find that door/windor sensor remove its battery and try getting rid of that one too. It may take a number of clicks of the remove button to get it gone.
brad5 the radio firmware update has sorted most of my problems. Can now control my heating yay.
Thanks for your help. I will do as you suggest with the ghosts.
Well thumbs up for heat! Good luck with the rest.
brad5 thanks & Merry Christmas to you.
Tried updating the firmware (zwave) but it just says "failed to start", then "Z-Wave Updater: ERROR: The device was unable to receive the requested firmware data".
Here is a screenshot of my zwave page:
imgur(dot)com/a/Tw22jhB
Ok just to confirm you tried that zwave update from the zwave details page as shown? Not an update of the firmware of a zwave endpoint...?
Those two devices circled are a problem. If you look at the thread preceding you'll see how to get rid of them. I don't think your screen shot showed 55 devices so if you have more that look like those you'll need to address them too.
If you follow this link Hub owners - Hubitat and join the owners group you'll be able to post screen shots directly.
Yup, I am hitting the "Firmware upgrade" button that you pointed to. I have ten of these devices, how the heck do I isolate them out of all the switches that I have?
Yeah that is a challenge. I would like to get some assistance from support on the zwave firmware update failure though. One thing to try... open the zwave details page, let it sit there for 20 min, and try again. Opening that zwave details page causes a lot of zwave activity and sometimes with a busy mesh it needs to chillax for a bit before the update will work. If you can try again and let us know let's get past that issue first. Besides, if you can't successfully do a zwave firmware update, it may point to an underlying issue with the zwave radio that is the root cause of other problems. In that case we can ask BobbyD to take a deeper look but try my 20 min suggestion first if you would.
1 Like
Thanks for your help, I will stay on the zwave details page to start.
Well that's a tad ugly I have to say.
@bobbyd we've tried to start with a zwave firmware update but it failed even after sitting on the zwave page for 20 min. We can proceed with trying to remove those ghosts but before that I'm wondering if there is an underlying zwave radio issue that might be causing the failure to update the firmware. He also tried a 5 min shutdown.
@cliftonite unless someone else pipes in with an option I think we might want to make sure the zwave radio is working correctly. Usually that involves sending support your MAC address and giving them some time to investigate the engineering logs to confirm it isn't a hardware issue.
1 Like
I just had a similar experience a few days ago. Suddenly, my hub couldn’t talk to most of my devices. Out of the approximately 70 devices on the Z-wave Details, only 2 or 3 showed any routing number information. I tried a Z-wave repair to no avail.
I got my Zniffer out and found I could see messages from my hub and from devices, as the reported status. The devices just weren’t responding to the hubs messages. I decided to hard boot my hub (graceful shutdown and remove power), since it was the greatest common denominator. Once it was back up, all of my devices had routes listed and everything worked like a charm.
1 Like
Yeah that was the first thing we tried... @cliftonite just confirming you did try the power down?
1 Like
I’m was more commiserating than suggesting a solution.
1 Like
I did not do the graceful shutdown/remove power. Once I did that, everything started working.
Aha! Well @wayne.pirtle your commiserating helped. Did you try the zwave firmware update? That will definitely help a lot.
1 Like
I tried, to do the .1 update, but it failed. I am going to do that tonight or tomorrow. I think my problem was not waiting for the page to finish it’s behind the scenes work (5-10 minutes).
Actually that was meant for @cliftonite but you should do it too!
1 Like
I logged in today to see how things looked and the bad/ghost devices are back. However I was able to upgrade the zwave firmware & my devices still work. Is there an easy way to remove them?
