If you still have the remote and it is IR or RF, i would buy a broadlink and program the codes. That way you have complete functionality without potential damage.
I use this for an 8 speed Big Ass Fan. Just program speed up, speed down, power on, power off, fwd, rev, and whoosh mode.
I actually do have a BroadLink for a couple other things. And I’ve tried to do exactly that with this fan but per my Google search, Harborbreeze runs on 304 MHz and BroadLink range is between 315 and 433.
I’ve tried a million times and I can’t get anything to be recognized
I bought this fan along before I was into Home automation and it’s the only one I have that I want to automate I might end up buying a whole new fan to suit my needs lol
I have a gate opener (non rolling code) that is on 310 and managed to get the Broadlink to pair. It did take many tries and being sure to hold the action button for a long time until the frequency scan completed and then tapped it once to grab it. Certainly at least 10-15 tries before I got it right.
304-310 are normally like the range of those little visor ones in a car.
I took a spare one button remote used to open the gate and a spare Broadlink I had at the house and after many tries, got it to work and could see the light flash. I took the base64 code and copied that into a script at the gate Broadlink which is even on a different Home Assistant instance and voila. I would note that I was not succesful just sending Broad Link + Device + Button name, it did not work even after it was memorized. It does work in the broadlink app though which is confusing … but the b64 code did the trick so maybe there is some frequency stored in that code.
Better, added that to a webhook and can tell my Alexa’s here … which goes … Alexa → Alexa Cloud → Nabu Home Cloud → Home Assistant → Home Asssitant Remote → Open Gate. Works in less than a second,
I drove myself crazy all day trying to do the BroadLink with ten fan . I was gettting the green check mark I. HA finally but nothing happening on the fan . Not sure what that b64 part means
Ok my bad I do know that is. If you look at my screen shot, fireplace and cigar(exhaust fan) hav been working great.
I just was able learn the power and speed one command for ceiling fan. When I close send remote command In developer tools it gives the green check mark. The light flashes on BroadLink. But nothing happens with the ceiling fan. Is the b64 command supposed to start with the letter B?
ITs one power button and 6 separate speed buttons.
I dunno, this might be a failed project. I dunno what IM doign wrong now, but I do the learn remote in developer tools, when broadlink light comes on I hold the button down on remote until ligth goes off. I press the button again when HA prompts me to… The Call service button turns green. But when i go to the storage file, there is nothing new added
SO now I can’t even pull hthe dam codes, to try and use them
And to make matters worse, I’ve just learned that I have a DC motor, which eliminates fanLinc
Note to Self: Don’t buy that type of fan!
Obvioulsly you are saying it is RF remote. I have seen issues reported for IR and not enough power to send the light beam unless perfectly pointed.
Yeah, it’s an older fan before I was into automation. It’s kind of funny because I had three imsteon switches and the eight button touchpad on my wall for several years.
And it took the company going out of business and me breaking out into a full-blown panic to find out what my options were
Couple days later I was like Home Assistant what’s that? It was right they added the whole integration
Never knew it would consume the next three years of my life lol every week configuring something new
On that note, I think I’ll look to see if and what type of ceiling fans are out there that are already smart and integrate directly with Home Assistant. Thanks for the help.
FYI, I am totally willing to trade anyone all my 6 button switches (like 6 or 7 of them) for dimming paddles. With Home Assistant now …
I never use the buttons on those
I rarely use any switch, ever except for a few … I have wall tablets now
My wife NEVER uses a switch, she has everything in scenes and Alexa and Home Assistant … handles her life perfect. “Alexa, turn on couch” … “Alexa, it’s bedtime” … “Alexa, open gate” , “Alexa, turn on dogs”.
Great news everyone! The most recent update of the Insteon Panel has been merged into the core. The features included in this change are:
Delete devices
Configure modem (PLM / Hub)
Configure device overrides (still not a recommended option in most cases)
Manage X10 devices
Move the panel from the side panel and to the standard configuration path
Settings → Devices & Services → Insteon → Configure
Ability to access a specific device configuration from the HA device page. I.e. you can get to the Insteon properties / ALDB via:
Settings → Devices & Services → Devices Tab → Select Device → Visit (in device info box)
All panel actions are moved under the actions (three dots) menu in the upper right corner of the screen for design consistency with other HA screens
The move from the side panel to the Configure section was requested by the HA team to make this consistent with other integrations.
@teharris1 I can’t express enough my gratitude for all you’ve done with the Insteon integration. You are the reason I use HA today, as I was part of the great Insteon-to-HA migration when the Insteon servers went offline from the bankruptcy.
I’ve used a Hub 2 and now a USB PLM to connect to HA. The PLM responds much more quickly, and doesn’t seem to be as affected by situations when a spike in Insteon traffic leads to messages being dropped on the way to/from HA.
But I have a couple of issues with my Insteon devices that I’m hoping you or someone else here can help with.
Status often doesn’t change in HA if a wired device was changed in response to a Mini Remote (2342-2). The remotes are directly linked to the target devices (dimmer outlet, ApplianceLinc, FanLinc). I’ve noticed that sometimes HA will see the button signal from the remote, but inconsistently. It’s never consistent; it’ll work for a while and then stop working for a while.
Also, I have two 2476S relay switches. They do not correctly work with ALDB read/write. They are linked to the PLM, correctly report state, and respond to on/off commands from HA. But when I try to load the ALDB, it shows one entry and stops, reporting that the ALDB is partially loaded. This behavior occurs with both 2476S switches. Ideas on why this may be happening?
I would like to add my voice of deep appreciation and thank you for all the work you do to maintain and innovate the Insteon integration. It is a lifesaver for me.
Question, I think I recall the integration used to auto detect new devices. I added a new plug in module to the hub using the older Insteon app on my phone. Works fine. That was about an hour ago, I have rebooted HA but still has not identified presence of new device. Perhaps I am mistaken. What am I missing?
@rfmcmanus, yes, it should recognize a deviced added using the Hub app or using the set buttons on the Hub and the device. I will test that to see if something broke. In the meantime, there is no harm in re-adding the device using the HA UI.
I just heard from the head of development at Insteon. They are releasing a new firmware version for the Hub and they think they have found some improvements in the Hub connectivity issues.