Right now when adding this fan manually, there is no way to control brightness nor to change color. Ideally there would also be a way to turn the fan and light on/off without the toggle, and possibly set direction without toggle as well. But I realize this may not be possible.
If not specifically supporting this fan, any chance of adding support for the buttons that are not currently supported in the app (for example the light colors and dimming)?
I havenât seen the Bond staff jump in this thread, but I can give a suggestion or two.
If you wanted to ADD a new device (so you donât mess up what is working so far) and manually record the buttons that are missing, choosing âclosest nameâ or writing down what you recorded them âasâ, then you can go in through the API and rename the buttons.
I have Color / Light Temp Change recorded as âSummerâ or âWinterâ or âLow Flameâ, then renamed.
Brightness Up I have recorded as âFlame Upâ / Brightness Down I have recorded as âFlame Downâ, then both renamed.
Experiment with manually recording those commands as a (new) Fan or Fireplace and see if that works as a stopgap until the Bond staff are able to lend more insight?
Thanks @residualimages ! This is a good idea, Iâll check it out this weekend.
Right now I have 4 of these fans in one room. The problem is that I didnât realize as I was installing them that I was programming them with the same remote (well, I did realize this, but, I didnât think it through). This would be great, except that they get out of sync because the circulation/lights/light color are toggles - so some of them are going clockwise, and the others are counter clockwise, and some lights are on, some are off, and different colors
I need to go in and disconnect power from each one and program them one at a time for different remotesâŚ
Awesome, glad theyâre all on separate channels now.
As far as the fan and light powerâŚ
Originally it seemed like Fan Power Toggle and Light Power Toggle were working?
If the original remote doesnât have separate Light Power On and Light Power Off buttons (which indeed seems to be the case based on the pictures you shared originally), Bond cannot add those commands to the fansâ receivers.
What Bond Bridges can do, if youâre willing to put your original remotes in a drawer (to not use them and get out of sync with what Bond did last) and leave any wall power switches on, is to enable an option to track and trust itâs own Bond-tracked power state of the Light. Then you can use voice assistants or Bond API commands to say âTurn On Lightâ and it only sends the Light Power Toggle command if the last state Bond knew the light to be in was âOffâ; if it believes the light is already âOnâ, it sends no signal.
Unfortunately thatâs not available for Fan Power state.
But if you were to get creative with that Light state tracking ability, you might be able to manually record a second Ceiling Fan device in each room which has itâs âlight kit power toggleâ recorded as actually the fan power toggle button from the original remote.
Then again, if you have your own third party smart home controller (Hubitat, SmartThings, Home Assistant, ISY, HomeBridge, etc), you could track your own state for fan power and only send the Fan Power Toggle command via API whenever the last tracked fan power state was the opposite of what it was desired to be acted on to change to at a given moment.
I donât recall now to be honest. I had tested it out last July (wow, I thought it was just a few months ago), but just got back to it yesterday. There are 4 fans in the room and when I set them up I didnât take heed of the remote programming, so they were messed up and I knew it was a bit of a project to fix it so I kept putting it off.
Itâs almost like the Bond is sending the toggle command twice. I think I saw the light flicker a few times when trying to use the Bond toggle. I tried programming the buttons a few different ways, in case it made a difference:
Holding the toggle button on the remote.
Pressing it once.
Pressing it repeatedly.
None of these made a difference (which I sort of expected).
Yeah, my plan would be to use this in Home Assistant - so I can track state that way. But right now unfortunately I canât turn the lights/fan on/off.
Not that itâs very easy, and Iâm not certain this would lead to success, but you COULD go into the command line and edit (PATCH) the signal to be a shorter version of any pattern you can find in the signal the Bridge âheardâ for a single tap.
Or mess with the Reps bit (unlike most of that thread, youâd likely want fewer rather than more, if yours is not already at 1).
Thanks again! We are doing a bit of decoding over there. Well, Davideos is, Iâm just along for the ride so far haha. I also went in last night and did some more thorough testing and re-programming and I was able to get the Fan and Light Toggles working
I didnât have much luck yet with some things like the light dimming/brightness and fan reverse, but Iâm a bit more hopeful now that the other toggles are working.
Going to keep at it when I have some time.
Do you have any advice for an absolute beginner to Bond? Iâm trying to set up Home Decorators Makenna Fans. FCC ID : A25-TX045
I tried to manually add them and got pretty lost.
Hey Jeff!
Not that going by looks alone works all the time, but it does look like one of my fans which was automatically detected (after a try or two during initial âadd deviceâ steps), and assigned a Template of RCF217 â unlike the remote in the original post which looked significantly different.
That automatic detection meant I didnât have to manually record each button press.
Only going on looks (as unsatisfactory as that is) since Iâm not currently home right now, and therefore canât verify if my FCC ID is the same as yours.
If you continue having trouble with either getting a template auto-recognized OR manually recording buttons, will you open a new topic with the FCC ID in the subject line? Iâll jump in and help more if needed there.
Also, Bond has official support thatâs pretty handy to reach out to in the app itself ( under Help Center from the main screenâs Settings ).
Hi Matt,
Thank you so much for your help. I attempted to add it a few times and the remote is not recognized in the database. I did contact support and they verified that this ID is not registered.
Is there a way to enter a request to have Bond add my remote? There are so many variables on it (such as light temperature, dimming, fan speed is controlled by the same button, etc).
Thank you again for your assistance,
Jeff
Unfortunately not yet. I have not tried for a few months⌠maybe theyâve been added to the database.
Please let me know if you find out anything and Iâll do the same.
OK letâs try to get the A25-TX045 added to the database. I need a volunteer⌠What is needed is to create a device on your Bridge called âA25-TX045â with a sampling of every possible state field value,
and then let us know the mapping from the buttons in the app to the state.
Something like this:
power off = fan off, light off
power on = fan off, light on 100%, cool color
speed 1 = fan off, light on 50%, cool color
speed 2 = fan off, light on 100%, warm color
speed 3 = fan off, light on 100%, natural color
speed 4 = fan on forward speed 1, light off
âŚ
speed 9 = fan on reverse speed 5, light off
We just need to see every value of every function (and just 50% and 100% for light). We donât need every combination of every functionâthat would be a big number.
We can then read out the device remotely using our customer service dashboard and (hopefully) create a database template based on it.
Same goes for the 2ABUP-FT1212R, just name it appropriately and let us know. This can save a bunch of time in procuring a whole fan that would otherwise go straight to the dumpster.
Unfortunately, unless youâre reprogramming how the Bond bridge keeps track of what you want this fan is a particularly weird beast from what I have seenâŚ
I have two of these fans in the same room, and they wonât even always sync up to the same OEM remote properly, so one ends up at a wayoff dimmer position compared to the other if youâre not careful. But thatâs just the beginning.
The main issue with these fans is that they send what seems to be a âstate machineâ value for the fan. I.e. whatever it sends, always on approximately the same signal, describes EVERYTHING (except the exact dimmer position which really sucks) about what the fan is doing; this includes overall power status, fan speed, lights on/off status, and fan direction of all things. I switched my fans to winter mode prior to deciding whether to use the Bond Bridge with them, and then later back, and realized one of the regular remotes would just randomly send a completely different remembered overall state. Like I went to turn the fan down, and it actually turned the lights off, sped the fan up to full speed, and reversed its rotation.
Thereâs a fair amount of work to make it work, needless to say. It wasnât a âknown workingâ fan and I tried the bridge, but without a shim of some sort in place itâs not worth it. Otherwise youâd need 48 different custom buttons based on the different states: 2 (on/off) * 2 (lights on/off) * 6 (fan speeds) * 2 (reverse/normal direction)! It wouldnât be hard to program for the bridge itself if thereâs a good enough API, state conservation/memory, and you NEVER used the regular remote to interfere with it; but otherwise itâs not worth the hassle and thatâs why itâs not been done yet.
And this doesnât include trying to alter the dimmer settings, which WOULD require state conservation/memory in the hardware in order to ensure it doesnât randomly change every other setting on the fan if more than one user has access to the bridge app. Because as near as I could tell it just pushes a âchange the dimmer settingâ sort of flag. I probably need a Flipper Zero or something like that to capture the data to confirm. Based on âblack boxâ testing of how the remotes work in my own setting at home I can definitely confirm that even just two remotes absolutely remember their own full states separately of everything else, and thatâs how the dimmer button works, and sometimes it takes multiple remote interactions to get both fans to sync up on the same signal.
