Side question: what are you using to generate your mesh network map? The default one from Hubitat definitely doesn't look like that.
It's called zigbee-graph you can install it through Hubitat Package Manager
1 Like
This post spawned HE to include this capability:
1 Like
Still hanging in there...no Zigbee reboot since I booted up on June 14, so nearly three weeks.
Have had a couple of devices pause reporting briefly, but a Refresh on their Device page "woke them up" and they started reporting again.
So not perfect but worlds better than before, and my automations that rely on Zigbee devices are running w/out issue. I've also been able to join new Zigbee devices w/out issue, previously joining or re-joining Zigbee devices was an iffy proposition.
3 Likes
Ya every time i join or rejoin a device zigbee reboots. When i get home i am gonna have to request a new hub as well.
1 Like
My improved results have continued, thankfully. Everything continued to work perfectly while my wife's family was visiting last week, to the point where she even bragged to them about a couple of my automations. (Be still, my beating heart.) 
OT: I also added a couple Z-Wave devices (iBlinds) and setup and automations worked w/out issues.
6 Likes
Looks like things are starting to settle, I myself haven’t had any issues at all with the radio restarts or the transition to the C8 overall, but still feeling pretty bad for all the people that have, nothing worse than constantly chasing issues.
Let’s hope thing continue to progress to the point of having a rock solid home automation system like the C7 and prior iterations.
3 Likes
1 Like
My c7 seems to be relatively stable (moved almost two thirds of my zigbee devices back to that) but the c8 still seems to suffer regular reboots several times a day unfortunately. However with most of the crucial zigbee devices back on the c7, the reboots are now not of as great concern.
(Edit) But it does appear that the reboots are not as frequent. Only 6 over the past two days (rather than say, 6 in an hour which is more like what I used to have). Though this might have more to do with the fact that most of my zigbee devices have now been moved off it. Probably a good week or so before I finish moving all zigbee devices over to the c7.
I had the same experience. Started moving devices off. Reboots slowed. Eventually they stopped when I moved just about everything off. Doesn’t really solve the problem but now everything is running on the old C5 without issue.
So am I missing out on anything leaving it there?
1 Like
The main benefit on the C8 should be the external antennas/better Zigbee/Z-Wave range, but since the C8 wasn't working well w/your Zigbee devices on it that's a moot point, obviously. If Z-Wave is working well on the C8 then I'd leave those devices on the C8. For me, anyway, Z-Wave on the C8 is better than on the C7. More direct connects, higher speeds, more reliable. If my Zigbee hadn't settled down, I would have moved all Zigbee to my C7 and kept my C8 for Z-Wave.
C8 is Zigbee 3.0, but again, if it wasn't working for you and the C5 does, then that Zigbee chip upgrade isn't relevant to your needs.
C8 also has Wi-Fi connectivity, but if you don't have to use that and it's best to use Ethernet.
I think C5 won't support Z-Wave Long Range, but you can do that on your C8.
2 Likes
Well, in my experience in these months with the C 8 is that the zigbee radio failure decreases as you remove devices, I have reached the number of 35 devices already stable in the C 8, we still don't know why that happens, now that the zigbee 3.0 version is better than the one that the C7 brings.
Regarding the C8's Wi-Fi connection, I highly recommend not using it, in my experience I have had a failure to the point that the C8 Hub hangs, with an ethernet cable it does not happen.
I know which team is working on it because I have had contact with it, I bought 5 C8 hubs and 3 were giving me a problem, in one they recognized that the hardware had a problem, and in another they uploaded an additional code to my hub to monitor some values.
1 Like
Support sent me a new hub. So far it has been solid. If the shutoffs will start again, net step is downgrading to C7.
4 Likes
I had a similar experience to you at 35 devices . I added zigbee devices to my replacement c8 one at a time / 3 or so a day. Everything was stable with no zigbee reboots. It wasn’t until I hit just on 40 zigbee devices that the radio started having offline/offline events. For a good couple of weeks or so before that it was fine. I’ve since reduced the number of devices on the c8 as I move back to the c7 and have dropped well below 40 devices. But the reboots continued. Not suggesting that the number of devices have any bearing. Just why happened to me.
I've migrated all zigbee devices back to my C7 from the C8 due to the radio reboot issues. So far so good.
To those that received a replacement C8 hub, did the replacement hub suffer from the same reboot issues or did it fix it?
I'm just wondering if its possible that I recevied two "broken" hubs in a row as my replacement hub suffered from the same reboot issue. FYI the replacement hub I recieved may have been a used hub as it was unpackaged and missing the PSU and an attenane. Wondering if it may have been inadvertently returned due to the same issue.
Thanks.
[EDIT: clarified that the replacement hub "may" have been a used one. I only assumed that to be the case given it was missing parts, unpackaged etc.]
I don't think they send out a whole new "kit" in original packaging for warranties. Last I knew, they sent only the hub. Presumably your power supply and antenna and the ethernet cable from the old hub are good, so why send replacements.
Almost zero chance you got two bad hubs in a row. I doubt the first hub was bad either. The second acting just like the first would seem to support this fact.
You quite likely have a bad device, a device is somehow incompatible with the C8 chipset, or some integration or app on your hub is acting badly on the C8.
I had issues with certain cloud integrations killing my C8 when I first migrated. I had to turn off all cloud and LAN based integration for a while to narrow down what was causing the issue. It wasn't easy to track down, but once I found the rogue app, things calmed down and the C8 worked normally.
Thanks. I figured that was the case. It would have to be a zigbee device I guess as the C8 didn't have any apps or integrations. I used it solely to hold zigbee devices which were then used by my other hub with rules, intergrations etc. via hubmesh.
At this stage the C7 is running trouble free with the Zigbee devices so may keep everything on the C7 until whatever is causing the issue is sorted out.
After moving all but one device back to my C5, all things zigbee have returned to normal. The last device is a Sinope Thermostat and moving it involves redoing a number of rules, but I will do that eventually and shutdown the radio.
In my testing, reducing the number of devices down to a handful was the only thing that stopped the errors. And when I have done that I lose the benefit of the mesh and saw a lot more misses.
My only complaint is that I have shades in a room at furthest point from the C5 and I have to send those commands out multiple times to ensure that they work. I didn't have that issue with the C8 with its antennas.
So I will watch this thread to see if this issue is solved and will then dive back in and move devices over to the C8. Meanwhile I have been enjoying flawless Z-wave on the C8.
I got a replacement hub with no charging brick and no antennae, but it's normal for a piece of replacement equipment, and it doesn't mean it's not new or was returned.
So far, the replaced C-8 works properly, but considering the old one started acting out a couple of months in, the jury is still out on whether I had defective hardware or it behaves "as expected" (i.e., bad).
Looks like this thread settled at "There is nothing we can do about it, replacing C-8s won't work, so just go back to C-5/C-7" and we shouldn't be OK with that.
