I’m trying to add 2 First Alert ZCOMBO Smoke/CO alarms (v1)
Hub is a C8 on v 2.4.1.177 (lowest one available for downgrade).
I tried all versions available in between.
Zwave excludes them. So that’s’s working. But when i go to add a device, it doesn't find them.
After the inclusion process, all zwave devices stop working. I have to reboot the hub for those to start working again.
I also noticed i cannot change zwave from LR to classic (doesn’t save).
Ive been trying this for 2 days now.
C7 on 2.4.2.160 excludes them successfully. Does not add them, zwave freezes on that one too.
Correct and if i want the c8 to go back to classic, even though the dropdown has it, it will not set/save that.
Nothing, blank.
2-3 ft
No. I have about 30 z-wave devices paired that stop functioning/responding once i start the pairing process for these (2) devices.
6 of those 30 are identical to these 2.
Paired a long time ago. No issues with those.
These 2, yes.
Yes. Until i try to pair any of these 2. After that, they stop responding. I need to reboot the hub for zwave devices to start responding again. It’s like the radio chokes …
Tried them both, yes.
The exclude process seems to work as it excludes them.
New but did exclude and device factory reset procedure …
There is no "classic" option. It is what it is. The correct option is either US-LR, or other regions. The other US option is for the older hubs, and it will be automatically selected instead of LR for the C7. You cannot change it from LR, it doesn't matter if it is on that setting, the hub still does LR plus (as you are calling it) Classic ZW.
This setting is a red herring, so ignore it.
That is hard to believe. It will at least say "excluding" or "discovery running" or something of the sort (screenshot below). If it isn't logging anything, you have more serious issues than just one device that won't join. Are you in live logs when you are trying this inclusion?
I just pushed the buttons without even having a device to try and I got these messages in logs.
That would be typical if the device you are attempting to pair is jamming the radio for whatever reason. Not ideal that this happens, however it does occasionally happen in my experience. A shutdown, pull the plug, and boot cycle unjams the radio so you can try again.
Ok, do you have a device that isn't one of these? It is possible (not sure how likely) but possible nonetheless there is a bad batch or defect in both being they are the same product. It is especially suspicious that 3 different Z-wave chipsets are choking with these particular devices. I am very astonished the C5 won't pair, it is a completely different and seemingly more tolerant device (in my experience) than the newer hubs.
So you have 30 (various) Z-wave devices on your C8? What about your other hubs?
Not an answer, but wanted to chime in that I've also been having issues adding certain Z-WAVE devices lately on my C8 PRO.
Some devices add fine. Others either don't add at all or always create ghost items. I've tried doing shutdowns of the hub including pulling the power. Factory resetting devices. Excluding devices multiple times before adding. Uninstalling some apps. Ect.. The hub is right next to the devices.
The device I tried adding this past weekend worked fine on Hubitat in the past, but now only creates ghost items.
One thing I'm also curious about is that "Hubitat Z-Wave Mesh Details" tells me the Z-Wave Firmware I have is out of date. I have 7.18 installed. I don't see a newer firmware update being offered by Hubitat, so I'm curious if Hubitat only support up to 7.18, or should the LR Z-WAVE module have been updated to a newer firmware version? (The latest firmware I see at Silicone Labs is 7.24. There have been 5 updates since 7.18.)
That's a glitch unique to that community-developed "Mesh Details" app... When JS first rolled out, an update to ZW 7.22 was made available, but that's since been rescinded (I'm not sure exactly why).
The Mesh Details app still thinks the 7.22 update is available, so it dings about it.
If you're on 7.18, that's as far as you can currently go.
