Experiences with Zigbee radio on C-7?

Hi, recently aquired a C-7 to replace my C-5. When booting it for the first time, it reported Zigbee network offline. I tried the things I could find on the forum like performing a soft reset, reset radio and rolling back firmware. When I get back to 2.3.2.141 it seemed to work, I could disable/enable the Zigbee radio and it shows the ID, upgrading again it would just say null(). After a bit of frustration and starting to write this post, I went through the rollback a second time and now it seems to work fine even after upgrading.

I have not tried pairing anything to it yet so just going by what the hub is reporting.

For those of you with C-7 hubs, do you have issues with the Zigbee radio from time to time after upgrading or do you think this was a one off thing? I have no devices connected to it yet, it's just been booted, connected to my account and restored a backup from the C-5. Just looking for some input before I undertake the task of migrating all the devices.

I have been running a C7 for 1.5 years and my Zigbee radio has never failed. Iโ€™ve been a HE customer since Feb 2018 so seen most firmware upgrades and I havenโ€™t had this happen. So hopefully a one time issue though you may want to reach out to support to ensure you donโ€™t have a bad hub.

4 Likes

Ok, thanks that's comforting to know.

1 Like

Same here. I'd say if it stays good for a couple days you should be in the clear. I do find after an upgrade the zwave radio's routing table looks funky and some devices don't work but a quick 5-min power down always fixes it.

I have seen issues with the zigbee radio if I do something to the hub that causes it to overload, but you'll see the excessive load errors from the hub too. And it's invariably either a third party integration or something really dumb I've done that causes it.

2 Likes

You also might want to contact support just in case..

1 Like

You also might want to contact support just in case..

I've seen that post but I bought it second hand locally and would be returning it to them if it turns out to be a hardware issue. Returning it to the US would be $40-50 and if receiving a new one I'd be charged $20 customs fee + 25% of whatever value they declare it as + the cost of shipping (so wouldn't help much if they gave me one for free if it's marked as $80 for insurance purposes).

Anyway, I'm hoping it won't come to that. So far it looks to work fine and based on the other replies it should hopefully stay that way.

1 Like

Same here. I'd say if it stays good for a couple days you should be in the clear. I do find after an upgrade the zwave radio's routing table looks funky and some devices don't work but a quick 5-min power down always fixes it.

I have seen issues with the zigbee radio if I do something to the hub that causes it to overload, but you'll see the excessive load errors from the hub too. And it's invariably either a third party integration or something really dumb I've done that causes it.

Thank you, that's handy info regarding the overload, I'll definitely keep that in mind. Likely wouldn't have managed to piece that together myself if I start having issues.

I'll give it a couple of days and try to pair a device to it. Probably set up an automation to turn the device on/off a couple of times a day and leave it for another few days.

My C-5 is still going strong so I'm luckily in no rush, just want to avoid migrating both back and forth if I can:)

1 Like

Since the Zigbee radios in the C5 and C7 are pretty much the same you could still run your Zigbee devices off the C5 hub and use the C7 for Z-Wave and use HubMesh to share necessary devices for rules etc provided you use Z-Wave devices.

Multi-hub configuration has benefits like reducing overhead and if using by location allows for greater / stronger coverage.

1 Like

That's a good point, I guess I need to do some planning and see what the best option is regarding placement

I've run this configuration for a few years and it works well. I also use Node-RED as a centralized rules controller to reduce hub overhead further and allow for multi-hub integrations (including non-HE hubs). Note: while this works for my use-case, ymmv.

I've dabbled with node-RED a little bit but haven't really found a usecase for it yet. I use home assistant as a front end for hubitat so I do most of the automations there. I just keep a few rules on the hubitat itself that I would want to continue working if the home assistant ever goes down.

The benefit of Node-RED is it makes your rules "agnostic".. HE has one way of handling automations, HA another - By using Node-RED I can create rules that handle both no HADB required and/or allow me to easily convert one to the other. Also I can incorporate different hubs as needed. Very powerful. There is an addon for Node-RED in HA which you can use for both HE & HA.

Again, ymmv - NR is def not for everyone.

I would also make sure you're zigbee isn't overlapping your wifi..

1 Like

Yeah, I've had that on my todo list for a while. The C-7 runs on 20, same as the C-5 and I haven't had any issues with that. But it shouldn't disable the radio even if I pick the worst channel.

I hope you're not running them both. The points are zigbee, the back mountains are wifi.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.