I'm hoping to confirm whether I've missed anything before requesting an RMA.
I received a replacement C-7 a little while ago, but I'm unable to pair any Zigbee devices.
Here's what I've tested:
Zigbee radio is enabled.
The hub enters Zigbee pairing mode normally.
Z-Wave is working correctly.
My original C-7 paired my GLEDOPTO Mini controller without any issues.
The replacement C-7 will not pair the same GLEDOPTO Mini and pro+.
The replacement C-7 also won't pair another known-working Zigbee device.
All Zigbee devices were factory reset before pairing.
Pairing was attempted very close to the hub.
Since multiple known-working Zigbee devices fail to pair while Z-Wave functions normally, I'm starting to suspect the Zigbee radio or hardware on this replacement C-7 may be faulty.
I've also contacted Hubitat Support by email but haven't received a response yet.
Is there anything else I should check before requesting an RMA?
Yes, it's the same Zigbee channel. This is a completely new Zigbee network and I'm pairing everything from scratch, not restoring a Zigbee backup or migrating the mesh.
When did you receive the replacement? The most recent order I can see was shipped in 2024.
Could you please send me your hub's MAC address in a private message? I'd be happy to review the engineering logs and see if I can determine why your Mini Controller isn't pairing.
Thanks. This is the replacement hub that I purchased in 2024. It has never been able to pair any Zigbee devices except one.
I've reset the Zigbee radio multiple times, performed factory resets on the devices, and tried pairing close to the hub on the same Zigbee channel as my previous hub, but no Zigbee devices are discovered.
I'll send you the hub's MAC address in a private message so you can review the engineering logs.
If you were able to pair at least one device, that indicates the hub and its radio are functioning properly. In this case, the engineering logs are unlikely to reveal the cause of the pairing issue. However, we'll still review the logs to see if they contain any other clues that could help identify a problem.
During the investigation, I identified that the Rollease Acmeda integration was responsible for the repeated Telnet errors. Engineering logs showed the Telnet service being repeatedly closed, so I disabled the Rollease integration completely to rule it out as the cause of the Zigbee pairing issue.
After disabling it, I tested pairing with both a Gledopto Zigbee controller and an IKEA TRÅDFRI device. Neither would pair with the replacement hub.
I then paired the exact same devices with my original C-7 hub, in the same location, and they paired immediately.
I also wanted to clarify an earlier point. Although I mentioned that one Zigbee device had paired with the replacement hub, it was not a normal pairing. It only paired after numerous attempts and a significant amount of trial and error. Since then, I have been unable to pair any other Zigbee devices despite repeated attempts.
Based on this testing, it appears the Rollease Telnet issue is a separate problem and not the cause of the Zigbee pairing failure. The same Zigbee devices continue to pair normally with my original hub but not with the replacement hub.
Given these additional test results, is there anything else I can check on the replacement hub, or are there any further diagnostics that engineering would like me to run?
The issue with my original C-7 was unrelated to Zigbee. After running reliably for several years, it started developing intermittent issues where some Rule Machine automations would randomly stop running while others continued to work normally.
I spent a lot of time trying to troubleshoot it, including posting here on the community forum and working with Hubitat Support. As part of the troubleshooting, I also performed a Soft Reset and restored the database because it was suggested the issue could have been caused by database corruption.
Unfortunately, the issue couldn't be resolved, so I decided to purchase this replacement C-7.
The Zigbee pairing issue with this replacement hub has been present from the beginning and is a completely separate issue from the one I experienced with the original hub.