Two Hampton Bay Fan/Light controllers suddenly failed

I have two Zigbee Hampton Bay Fan/Light controllers. These were installed 4+ years ago
on C7 hub, eventually migrated to C8 and up to yesterday worked near perfect
(occasionally dropped from Zigbee mesh but simple power recycling brought them back).
Yesterday both dropped from a Zigbee mesh and now they don't want to stay connected.
Yes, I can re-pair them back, completely delete and reinstall but this does not fix the problem.
Of course, I tried to re-boot and soft reset hub, reset Zigbee Radio Re-buid Zigbee network
but nothing is helping. Initially everything looks good but in within few minutes thinks are
disconnecting. The rest of the Zigbee mesh seems to be functional. All sensors, plugs and
switches are working just fine (I did not test all buttons but few were working).
I personally did not install any new devices and did not not touch anything on WiFi.
But I am in a big apartment complex with gazillion of WiFi networks around. Of course, I have
no idea if any neighbor installed something.
Any ideas what may happened and what else to try?
I am thinking to replace them with something else but so far did not find any good
canopy style replacement. Both Fan/Lights wired only with two wires. So wall switches
are not an option.

I had the same thing happen with 3 of my Hampton Bay controllers a few months ago within days of each other. Zigbee keeps falling off. I gave up and got a Bond hub and never looked back. The Bond hub is solid, works 100% of the time.

Same here. Got tired of the HB controllers falling off of the Zigbee network and then having a hard time getting them to pair again.

I also bought a Bond hub and paired the HB controllers to the Bond and the Bond to the HE. Everything is still local.

By doing this I lost the ability to dim the lights on the fans but it was a very small price to pay to have the fans NEVER fall off the network.

1 Like

This is a widely reported problem with this device. A couple users on this forum replaced the antenna, which was possible with the early models, but I think something changed with later ones that made it more difficult. Personally, this helped with mine (until I just replaced the whole thing with an Inovelli LZW36, but that is discontinued and a similar replacement won't be out for some time, so that won't help your right now, either).

It should also be noted, related to this and your other topic, that there is no reason to delete a Zigbee device from Hubitat before re-pairing. Just reset it, and when you pair it, it will be recognized as the same device and work in all existing apps, etc., without any effort on your part. Deleting it from the hub should have no other effect other than making it more difficult (for you) after re-pairing.

1 Like

Same here. I have 5 of these. Our power went out a few weeks ago for about 8 hours. Lots of devices would not come back until I paired them again. All 12 Zigbee IKEA blinds are now back as are 2 of the Hampton Bay King of Fans controllers. I canโ€™t even get three of them to factory reset which eliminates HE. They work fine from the remotes but HE doesnโ€™t see them. I tried the power on/off for 3 seconds 5 times, all sorts of combinations. I find it hard to believe these 3 all failed within a few days of each other.

I have 4 of these and were on a C-5 until a few months ago when I got a C-8. When I migrated, I did so without their "companion repeater" that seems required. They worked great for a day or two then half fell off.So I added the repeaters back in and they've been rock solid since... I even had a neighborhood wide power fail in that interval and when I got around to testing them, they were fine, still are, as of today. (I have a lot of equipment that has to be brought up in the right order or nothing works, so checking the Hubitat array was far down on the list.)

I have experienced the refusal to reset symptom as well. If I left it alone for 15 mins, the next time I tried the power on/off for 3 seconds 5 times worked.


Yes, I saw many posts regarding problems with this toys. Surprisingly two my
worked near perfectly for 4+ years until yesterday. They quit with no apparent
reason. I can repair them back easily but they are staying connected only for
few minutes. I tried to reset them many times but this eventually resulted in
somewhat corrupted driver. This was a reason why I had to delete them completely.

To bad there is no any good replacement for this devices. I may consider Bond
integration but this will be unidirectional. There are few WiFi canopy controllers
but any cloud-based integration is absolutely no go. Let me see what solution
I may find.

This is not possible, though perhaps I'm not understanding what exactly you mean. If there are concerns about any state of the device itself on Hubitat, the "Device" driver can clear state, current states, scheduled jobs, etc., and a re-pair would re-run "Configure" as part of the pairing and probably fix everything.

I have many repeaters in place. What is a "companion repeater"? Is this something
special and somehow dedicated for the HB controllers?

I am using this trick left and right for cleaning states, etc. The problem with HB
controlers is child devices which will be removed. This will destroy many rules.

Are you sure it will remove the children?
I recently changed a ZEN17 driver that has children to device, basic z-wave, and I think something else, and it didn't wipe out the far as I can remember. which isn't far, lol.

Not if you don't run the command to remove the child devices. :slight_smile:

Keep in mind that child device drivers can also be changed for the above purposes, too -- normally. Some of these were created as "components" with some early drivers, which is generally more plain than it's worth but also prevents you from doing that on them... (but all of the Zigbee fun happens in the parent device, so there shouldn't be much to worry about with the child devices where you would need to do this).

100+% true. But after gazillion times of repairing this things something really bad
happened. And only deleting the device all together fixed this mess. However this
did not fix the original problem.

The first thing I heard about regarding the HBFC is that they had a weak Zigbee. The solution was to put in a pair of repeaters. At the time, many people used the Iris wall-wart outlet. I did too. Their advice was to put in a pair of repeaters, one above (or below) and another in the same room such that the HBFC was 'in the crosshairs' of the two repeaters. I didn't find it necessary to use two, but that's perhaps because when I got mine, they were making them with a Zigbee antenna intended to poke out past the canopy. I was able to get by with a single, in room, repeater. Thus I label them a 'companion' since they were needed 1 for 1 and really had no other use in my Zigbee mesh.

Over time, I would find the wall warts sitting on the floor or in a nearby drawer, because they 'looked ugly" or "don't know what that is for, just trying to clean things up" from the family. I bought Zigbee in-wall switches, dimmers or outlets and replaced specific ZWave in-wall switches, dimmers or outlets, so as to make them tamper proof. :slight_smile:

1 Like

OK. Nothing specific, whatever Zigbee repeaters are needed. There are many on my Zigbee mesh.
My 2 HBs with external Zigbee antennas. What is not clear - why these things are dropping from
the mesh. Weak Zigbee signals definitely will compromise communication making it very
unreliable but this should not be a reason for quitting from the network. Zigbee device could be
powered down for a long time but after powering on they near instantly back on line.
Many Tuya devices are not staying connected due to some Tuya-specifics in protocol. But it
does not make any sense if device can easily join network, stayed connected for some time and
eventually quits. In my case everything was OK for 4+ years and suddenly a problem with no
apparent reason. My good guess, some components decided to retire. Usually bad quality
electrolytic capacitors simply loosing a capacitance over time. (Just thinking loudly.)

IF "the Repeater" (pretending there's just one that they all chose to use) got unplugged, or died, that would do it for these HBFC. It's exactly the reason I swapped the wall wart repeaters out and went with in-wall. WAF went down when a downstairs ceiling fan wouldn't come on. People were here so I couldn't debug easily... but eventually I found the wall wart in a nearby drawer... "because it didn't look nice." It took 6+ hours to come back on its own... back when it was on a C-5.

1 Like

I used Peanut plugs as repeaters. My Hampton Bay controllers still were losing connection after a few years.

Just get the Bond Hub.

1 Like

Peanut?? well that's probably the problem. Those have a well documented problem.


The peanuts worked fine as repeaters for years.

1 Like

I have a peanut (that wasn't being used by the HB fan) and it works as a solid repeater for me too. I have 2 sensors that repeat through it.

In a 1000 sq ft house I have 10 repeaters, multiple in each room, so repeaters weren't a problem with my HB fan controllers.

My living room fan controller would drop at least once a year and it would offen take a month or more to get it to stay connected again. It happened so often I added a dumb wall switch just so I could easily toggle power to reset it.

My bedroom was rock solid, until it wasn't last year. That's when I gave up and bought the Bond. I don't see it as a repeater problem as nothing else is affected.

One of my controllers is about 8yrs old and the other is 5 or 6 and both have the outside antenna which I mounted outside the canopy. I don't use the remotes so unidirectional isn't a problem for us and they haven't gotten out of sync.

The HB controllers are just really flaky for a lot of people.

1 Like