Any update on this? I also bought this fan from home depot, and the way they advertised the fan it seemed like this would work.
Is there any update on this? I just installed 3 Ashby Park 52" fans in our bedrooms and a large Kensgrove 72" in our den. The Kensgrove works fine, although it has more fan speeds than the Bond app recognizes, but the Ashby Park still doesnât work. Any ETA on when the next software release will begin to pair these devices?
Any update on this?
I installed the same fan as Thomas.
Ashby Park 52"
This fan is readily available through Home Depot.
Is there an update on when the software will accommodate this remote, or is there some sort of workaround that I can employ to get Bond working with my fan?
Specs:
Model: TX028C-S
FCC ID: A25-TX028
IC ID 10924a-TX028
Iâm pleased to share that this remote will be available in v2.17.3 firmware, due out next week. Currently in internal Q/A. Note that the Color button will only work via the app, not integrations.
4 Likes
Awesome! Thank you!
I donât care about the color changing stuff, I didnât even realize the fan could do it until I unboxed it. 
All I care about is being able to turn it on and off via Alexa.
1 Like
v2.17.4 firmware has been released for Bond Bridge serial numbers starting with Z. (if youâve got an A or B unit, hold tight⌠weâre still working on that update.)
This new FW should support this remote. Sorry it took so long. Thereâs so many remote protocols out there. (Why do they need to change it every time???)
2 Likes
Yay! âŚDownloaded the firmware today and added the AX-TX028 remote, it took a couple of attempts but eventually the remote code was found and Iâve successfully tested with the Bond IOS App and Alexa.
2 Likes
Iâve got a Z bridge and have the Bond app successfully paired with the remote.
Thank you!
I wanted to share my experience to hopefully save you all more support tickets - and my experience sort of lines up with Dhuas:
- I went through the setup steps in the Bond app for the A25-TX028 and the app right away recognized my remote, woohoo!
- When I was on that screen after the remote is recognized where the app has you test out the different functions, the functions were working mostly randomly or not at all
- I tried to re-pair the remote several times and always ended up in the same situation where the buttons appeared to just randomly work whenever they felt like it, but not on command
- I opened up the spec for the remote protocol that I found somewhere on Google, canât remember where, but I saw the remote works at 304 Mhz
- When I went back into the app, I saw that when it auto-registered my remote, it registered it at 303.8Mhz
- Somewhere in the app, I think in Advanced settings during setup, it lets you specify a frequency range, I did RFID and 304Mhz
- Tried it out again and everything works perfectly in the app now
Just now trying to configure this device on my new Bond Bridge. I have the latest firmware (v2.17.4). It recognizes my remote, and gives me three choices. None of the choices actually work when trying out the commands.
Not sure what to try now.
It took me several times for me before the bridge recognized the remote as AX25-TX028, when it did, there were a couple of remotes to choose from but the one that worked did have âAX25-TX028â imbedded in the name â if you donât see that keep trying until you do.
1 Like
Hi Paul, welcome!
Do you have the A25-TX028 remote control? Or some other remote?
The best way to get support is to contact our Customer Support (https://olibra.zendesk.com/hc/en-us). They will ask for photos of front/back of your remote control + the FCC ID if it has one. We can then assist in figuring out how to make it work.
Interesting⌠Actually most of the transmitters that we casually refer to as â304 MHzâ are actually â303.8 MHzâ. The Bond Bridge scans over many different frequencies and tries to lock onto the strongest frequency. Sometimes it might miss however, picking up on a neighboring frequency where the signal is not perfectly represented, and yes adjusting the scan frequency manually would help workaround the problem!
It is the A25-TX028. After a little over a half dozen attempts, it recognized the correct remote. It sort of works now.
@pjwysocki - do those last steps which @cronos mentioned work for your fans?
It was recognizing it as 304Mhz, so didnât have to specify a different frequency range (although, if I had to not seeing how I would).
My process involved attempting to add a new remote. If the A25-TX028 wasnât an option, I would cancel and try again. Once the A25-TX028 was given as an option, I would attempt to validate the commands. If they didnât work, I would cancel and try to add a remote again.
I finally managed to get the remote recognized and the commands working. Finished adding the remote. Worked fine through the Bond Home App. Once I added the device to Smartthings, the first command worked but subsequent commands stopped working through both Smartthings and the Bond Home App.
Will try again tomorrow, by removing the remote and adding again as I have time throughout the day.
Thanks for the detailed write up.
Fingers crossed for some better success tomorrow.
When the Bond app and SmartThings both stopped working, the original physical remote continues working without issue, correct?
As a matter of fact, the physical remote also stopped working. I had to physically cycle the power through the light switch before the physical remote would work again.
Very odd. This seems to point to a bug in the receiverâs firmware where it is getting stuck. These receivers all use different hand-written (often assembler-based) algorithms for decoding the remote controls, and they vary in quality and robustness, though this would be the first time Iâve heard of one going unresponsive.
Well, if it is odd, chances are that I will experience it.
I had to go into the office the last few days, so havenât had a chance to work on this further. Will attempt to do so tomorrow.
@merck Seems the BB (snowbird) also has the hang up issue as well on 2.15.8.1. Every night when I try and call commands via Home Assistant to set my sleep settings via scripts it seems the queue gets hung and I have to use the OEM remote to turn off the fan light. The only other thing I changed was going to the Home Assistant bond integration after they changed the template fan standards. I feel like now Iâd two commands come in quick succession it breaks the hub. Not sure if buying a new (zz?) model would fix it or even the pro hub. Either way my wife hates it.