2.3.5.13X Progress on Zigbee

The C8 hub by default operates with more power than the earlier hubs. If you have lots of repeaters like I do, you might not need that much power. I changed my Zigbee radio power setting to 12, which is still higher than the older hubs. I might try cutting it back to 8 which is where the C7 operated.

I am an amateur radio operator. We have always been told not to use any more power than required to make the contact. If the front end of the receiver is overloaded, signal quality decreases. I know my LQI reading are lower now than with the C7, but I do not know whether the LQI is calculated differently or if the signal quality is really lower.

2 Likes

I'm going to try to enable CW on my Zigbee devices. That should get through any QRM.

(for non-hams on the thread that was a joke... don't try it at home)

2 Likes

I upgraded from C5 to C8, i have about 10 ‎MCCGQ11LM aqara door sensors, i had to repair all of them when i upgraded to c8 and they only work for like 10 min and then they drop off and does not work again. The type of device are Xiaomi door/window sensor. Everything was working fine on the c5 for almost a year.

Pretty common issue w/those (Aqara and Xioami) sensors on the C8 (and on the C7 as well) for many. I haven't followed C5 use of them as I don't have that hub. They aren't officially supported by hubitat. You might have to keep them on the C5 and share them to the C8 via hub mesh if you decide you want to keep the C8.

I am updated to 113. I have tried power levels 8, 12, 16, and 20. My IRIS v1 buttons and contact sensors seemed to have dropped off after updating to 110, they did not come back after updating to 113. IRIS V1 motion sensors never worked with the C-8 hub so I removed the two I was still using, and replaced with IRIS v2 motion sensors. These seem to work. I have a bunch of the V1 sensors though. It would be great to use them in certain places eventually.

My IRIS V1 smart plugs all seem to be working

I am having trouble with my Yale Zigbee DoorLocks after 110, they also did not come back after 113. The Door Lock events log is tracking the physical locking and unlocking, but no command from the system seem to be making it to the lock from either the device page or from any automation apps.

All of my Sengled bulbs have been pretty much offline since I unboxed my C-8. I can get them to reconnect briefly, but they always stop working again really soon. I have some Sengled LED RGB bulbs I'd like to add to the system, but the standard cool white bulbs still don't work, so I'll wait.

That's about all I have noticed that is still not responding under the 113 update.

QUESTION: Would it be worth the time to recommission my C-7 and shift all my non-working Zigbee devices back to it? I'd want to eventually end up with one hub, so when the C-8 is solid, I'd want to switch them all back. . . Worth it?

V1 devices not pairing w/C8 is a known issue that is being worked on. HE staff has some V1 hardware shared by an HE user and are investigating the issue.

Every release should have a "known issues" post in News and Updates>Release Notes in the forum. You can check that first to ensure you don't try to fix something known not working.

1 Like

Even on my C5 I've never been able to keep this on my mesh. It always falls off, so bad I've just abandoned it as it sits lonely on my floor.

Just lost an ST water leak sensor that had been stable for a while...

Those are like rocks...very surprised to see that fall off.

I've lost my second Hue outdoor motion sensor, so while they lasted longer than before, they are definitely not sticking for me.

Yeah no kidding. I had a bunch of them go south early on that I had to re-pair. This is the first one in a while.

I lost a Hampton Bay fan controller today, that usually only happens on occasion if the power flickers off and on for bit. I did swap out one of my sengled bulbs with a Wifi bulb because I can't have that light not working and I'm just tired of it not working.

The single Sengled light bulb I have on my mesh is holding on, though it sounds like from reports here that they are falling off fairly commonly.

I had started having my Sengled bulbs falling of my mesh some weeks back, and finally gave up and replaced them all w/Hue bulbs that I already had. That was on my C7, so I do wonder if the Sengled issues were already cropping up on the C7, and maybe worsened on the C8.

No idea why, I had been using Sengled bulbs w/out issues for years.

I've seen another report of Hampton Bay fan controllers going off...

There are a lot of mysteries with ZB and the C8. I have a full wave antenna on the ZB radio at 12 and 16 power and all of my aqara and Sengled bulbs have been stable.
The magic of RF.

1 Like

ditto, the person who wired my house thought it would be fun to bring electric to the lights first and then to the switches so I lack neutrals in most of my switches. All of my house is using sengled bulbs. I only have 4 that are giving me problems and only one that was a must work.

I know they have non neutral switches now but up until this hub "upgrade" the sengled bulbs were flawless.

1 Like

Can't find it now, but on HA & Z2M forums there were reported issues with the EFR32MG coordinators, specifically the Sonoff Dongle E

1 Like

I have not jumped on the C8 bandwagon yet. I will, but work is too busy right now to be part of the new and shinny club … and things are sooo stable on my C7 with external antennas.

That said, I have 16 aqara devices (temp/humidity and motions) on a separate C5 with three tradfri repeaters and zero issues. It has to be about a year now since I did it. I really recommend pushing them to their own zigbee mesh and using hubmesh to bring them across. Not only do the aqara drop when they are with other devices, but they can take repeaters offline with them.

2 Likes

Add me to the list. Mine were with Hue Outdoor motion PIR drooping off with them flashing red. I put one within spitting distance to my C7 and got the same results. They work fine with Echo 4 and Hue hubs. I then brought them in through Hue hub via Advanced Philips Hue Bridge. It worked! Patting myself on the back. I then tried it through HE again and found that's working now. So, one of the recent updates must have fixed my problem. Anyone still having Hue sensor problems can try Advanced Philips Hue Bridge if you have a Hue hub. I've left half direct to HE, and the others Hue hub. So far both ways seem steady for me. One thing is the driver with the Advanced bridge is lacking basic features one would expect for "Advanced " in its name. For example, motion retrigger setting. I think it defaults to 10 seconds though I have not actually timed it.

This is interesting; definitely sounds wrong... @kkosev reported seeing this exact behavior on an earlier firmware:

I haven't been able to reproduce any reset/join failures recently, though l had one instance where an Iris V2 contact (which turns its blinking blue light to green on successful join) appeared to have paired and then went back to blinking blue again when I had left Zigbee joining process running. Tried to reproduce and couldn't but definitely saw it once.

this morning I noticed that my HSM didn't arm last night. I tracked the issue down to a Visonic MCT-340 contact sensor that fell off the zigbee network while in an open state. In 4 years of using these I have never had an issue with them other than a few that eat batteries slightly faster than others.

I had one that fell off in open state a couple of times. The first time a battery pull "fix" didn't last, second time I re-paired it and it seems solid again. I've used these since I was first on SmartThings and never had mesh issues w/them, so a first for me as well. I have a lot of these sensors so I do have to say that one going off is a small % problem.