Yeah, concur... I've given up on trying to bring stuff back online when it drops - they either mysteriously come back up on their own (while inevitably something else drops off), or I just end up rebooting every few days and that seems to help sometimes for a while anyway.
But trying to chase things around and coax them back into behaving well is just too exhausting - it's like playing a never-ending game of whack-a-mole.
Fortunately, my problematic devices aren't show-stoppers, so I can get away with letting them pout.
Yup...I've moved power down to 4 most recently (mostly since I hadn't tried it yet), and re-joined most of my zigbee plugs/repeaters after the change. Still had a number of devices drop over the past day. I've either gotten them back online or replaced them (in some cases w/Iris v2 motion and Visonic MCT-340 contacts reset/re-join just doesn't work).
Devices that have gone south and needed to be replaced or re-joined since I completed re-joining my Zigbee plugs/repeaters (Centralite old and new, Innr, & Sengled, and Tuya repeater) yesterday morning:
Iris v2 motion
--5/18 evening| Stopped reporting, would not rejoin after reset (stuck on initializing), so replaced it w/another Iris v2 motion
Visonic contact
-- 5/18 evening| Stopped reporting, reset/re-join worked
Innr plug
-- 5/18 Stopped responding, reset/rejoined and OK since then
Visonic contact
-- 5/19 AM Door open/close, battery pull|worked
Visonic contact
-- 5/19 Battery pull & open/close, not reporting updated temps initially, but then later (hours) started updating temps too|
Visonic contact
-- 5/19 Battery pull no effect, couldn't get it to reset/re-join (stuck on initializing, and after one failed pariing on C8 device would no longer complete a normal reset, an issue I've been seeing on the Visonics on the C8), so replaced with Aqara contact sensor
Yale lock
-- 5/19 lock/unlock after Device Activity Check listed it as not responding - slow to respond initially to commands from Device page, but after a minute or so started responding normally - need to keep an eye on it|
The C8 particularly doesn't seem to be fond of the Visonic MCT 340s that I've been using for years on ST and then on the C7, I've been having consistent problems w/keeping the Visonic connected in different areas of my house. In the end I may have to move all my Visonic contact sensors back to one of my C7's and hub-mesh them onto the C8. Will need to move some repeaters to the C7 at the same time to support the Visonics.
Wife has been surprisingly relaxed about all the "service interruptions," which I have mostly blamed on FW updates (I'm ducking for cover!).
I've been following this for quite a while and trying everything mentioned in the various threads. A few days ago I threw in the towel and ordered a used C-7 off ebay and took today to re-pair all my devices.
The C-8 is now in the "maybe later" bin in case they work out all the kinks.
Good luck to everyone trying to tough it out! You're doing important work!
Some of us are just breezing through with the most reliable Zigbee experience ever on the C-8. Although I can appreciate the frustration being felt by those that haven’t been as fortunate. I wish there was an answer to why there is such a disparity.
Yeah, that disparity has got to be a headbanger for them. I feel for them. I really do. I just can't spend as much time as I have been re-pairing devices and having WAF fall...
There is a huge variety of devices being used by the Hubitat community. Some folks have been doing home automation since the very early days and still have older devices in use. Others attempt to use devices like Aqara that are not on the officially supported list. Some folks are trying to get all their Zigbee devices to connect directly with the hub by using max power. Others have Zigbee repeaters scattered all around the house and run low power on the radio.
Most of my Zigbee devices are Zigbee 3.0 certified. However, I do still have several older Smartthings devices running HA 1.2. I even have some older Centralite devices. I have removed ALL of my older repeating devices from the network and replaced them with Zigbee 3,0 devices. have experienced a couple of glitches, but for the most part, things have been running smoothly for well over a month now. The Zigbee radio still goes offline occasionally, but comes back in about 7-8 seconds and the devices still work, so I am just ignoring the logs.
@gopher.ny It has been a few months since you said you were working on fixing the pairing problem on the Centralite 4257050-RZHAC and I'm am wondering if you have made progress on getting this to work. I have many of these and I need to pair another one.
Ok, so it's been a couple days since I "reverted" back to a C-7 (the reality is that I went from a C-4 >>> C-8 >>> C-7), and everything has been smooth as silk. It's glorious.
That said, I wanted to add some more (anecdotal) data to the pile:
DISCLAIMER - I am NOT saying definitively that any of this is related, but I am simply putting it out there.
Prior to reverting, I was having layers upon layers of odd activity occuring in my home. On top of the Zigbee woes we keep seeing, my UDMP router would need to be restarted at least once a day because all internet would cease (very rare previously). MQTT seemed to be missing beats at inopportune moments and automations in Node-Red would not run. MQTT was super odd because that's not linked to Hubitat in any way.
This, on top of the Zigbee issues, was really really getting on my nerves... Since migrating to a C-7... nothing. Node-Red automations running like a dream, nothing odd with MQTT, no internet drop outs.
Like I said, see the disclaimer above. I'm not pointing any fingers. Alls I know is that I have my Hubitat home back and I'm McLovin' it.
We have implemented various fixes for Zigbee devices not paring properly. Please be sure to update to the most recent release, and if the problem persists, please send us a private message so we can further assist.
Still no difference, Zigbee devices being dropped by Hubitat and randomly ‘re-found’ only to be dropped again later.
Some comfort to know others are seeing Zigbee behavioral issues and I think important to note that all this worked with the C7, the only thing changed in my setup is the upgrade to C8. Unfortunately I no longer have my C7, not that I would relish having to step back to it (is there a migration path back or would I have to find an old C7 backup file and re-load that?). Hopefully the team can figure out what broke/changed between C7 and C8.
Not sure why I am having a problem. I am on 2.3.5.140 and just tried to pair it and it just times out. I have factory reset the device by holding the power button while plugging it in and waiting for the blue light to flash. Am I missing something? I have a bunch of these that converted over from the C5 to C8 and all work.
We have seen some issues in systems mixing certain Zigbee 3.0 devices with non Zigbee 3.0 devices. Could you please share a list of devices you have paired? Also, you could send us a private message along with your hub's MAC address or hub ID and we would be glad to take a look to make sure you are not dealing with a hardware malfunction. The symptoms you're reporting are not common.
Any chance the device is attempting to join via a router that is more than a couple of hops from the hub?
You'd expect a join to work from anywhere in the network (within range of a repeater), but after a number of reported issues with joins failing when the joining device happened to be more than two hops from the coordinator/trust center, SiLabs came up with several workarounds (changes to the way the hub's firmware is configured) to mitigate the issue...
If the joins succeed closer to the hub, it's possible that issue might be in play here: Why aren't nodes sometimes able to join (no TrustCenterJoinHandler callback) -- caused by an address resolution issue (if the node sending the Update Device command is a non-neighbor of the TC and not tracked in any of its neighbor/child/binding/address tables for address resolution)
The situation has not changed from all my posts to date. The main 2 devices used throughout this thread are the
JASCO light switch:
endpointId: 01
application: 16
firmwareMT: 1124-0054-00000003
manufacturer: Jasco Products
model: 43084
softwareBuild: 00000003
And
Sengled color light:
endpointId: 01
application: 26
firmwareMT: 1160-80CC-00000026
manufacturer: sengled
model: E21-N1EA
softwareBuild: 00000026
The general behavior is that I can pair the devices and see via the sniffer that they initially connect usually through 1 sometimes 2 repeaters. After a day or so Hubitat starts failing to send commands to 6 or more of the around 28 devices. If I wait another day some of those disconnected ones will start working again and others, that were working, will have stopped. If I use the sniffer to check I see habitat never sends a command to the devices that stop responding and (so far) for each of those that remain operational I usually see a direct link from Hubitat to the device (no repeaters being used even though the initial pairing often used one).
In general the initial pairings tend to use other JASCO switches as the repeaters of choice however I do have dedicated repeaters (about 6) throughout the house:
endpointId: 01
application: 03
manufacturer: eWeLink
model: SA-003-Zigbee
powerCluster: none
Occasionally I see them being used at pairing time.
@mike.maxwell@Tony
Boy do I feel like a dummy. I fired up a spare C5 hub and tried to pair and it wouldn't... Humm
The problem turns out to be operator error. I was plugging the outlet in while holding the button until the light flashes. As I just discovered I was supposed to plug it in while holding the button but releasing it as soon as the light came on. Jeez louise all this time screwing around with this thing. I guess I should write it down next time? Sorry folks
You're not the first to fall down this path, so don't worry too much about it. So many devices, so many different reset/pairing steps. It would have been nice if the the Zigbee and Z-Wave manuf had seen the shared benefit to making it easy by having consistent steps. Oh well...
