Aeratron Fan Control: Inaccurate Button Matching

BOND Setup and Hardware
1

Hello,

Brand new user here.

Just got my bridge today and I am trying to make it work with an Aeratron Fan (6-speed, no light).

First tried to reproduce the toggle button in the app with no luck. The bridge turns green, but the newly created button has no effect. I then replaced it with one button for on and another for off (even though the original remote only has a toggle) and it sort of works, except for the following: when I press the On button with the fan already on, it will keep it on but decrease the speed to the min level.

I also matched the increase and decrease speed buttons on the original remote with a mixed success: when I press the Increase Speed button in the app, it will bring the fan to max speed while the decrease speed will bring it to minimum speed.

Are there any tools to diagnose the issues and fine tune the commands? Are these known problems?

Thanks in advance.

2

Correction: the on button created in the app does turn the fan on, but at the lowest speed, so it is working consistently, but not as expected. With the original remote, turning on the fan brings it back to the previously used speed.

3

One of the best troubleshooting steps the Bond staff usually asks for is the FCC ID of the remote (sometimes on the back, sometimes under a battery door), as well as pictures of the remote itself.

4

Hi,

Apologies if i’m positing in the wrong place, but could you let me know if compatibility issues with Aeratron AE3 fans have been resolved. I have a client with this brand and have had issues getting them to respond or behave as they should. My last attempt to integrate them using bond bridge was about four months ago.

Regards
Andrew

5

I haven’t seen any updates in this thread about it - neither from someone with the fan / remote posting the FCC ID or pictures of the remote, nor from the Bond staff that are able to visit the forums from time to time.

To get a quicker response, you might try the Support Chat in the Bond app during business hours, or send an email to customerservice@olibra.io to create a ticket.
Also, if you would like to provide the FCC ID or pictures here that might help the community help you. :slightly_smiling_face:

6

@merck - has this brand / issue been added to the list of things Support or your team has seen?

Possible match (though this example has a light):
https://fccid.io/M8CRF7091BLN01/User-Manual/User-Manual-2625099
@Andrew / @statman - can either of you confirm if this looks at all similar to your device?
(Also looks similar to user manual here)

Also a random git search found this project.

7

Thanks so much for your help, much appreciated.

8

We show this remote as fully supported on our compatibility check. Possibilities are (1) we got it backwards or (2) Aeratron changed the protocol between batches/models of product (this happens all the time in this industry).

Will check here. Beautiful fan btw.

2 Likes
9

I have an older model (e502), so not sure if this can help, but I was able to manually program the device by using the exact frequency of the remote (433.85) and instructions from the Bond team. It is a bit more tedious at first, but the fan has been responding perfectly since.

2 Likes
10

Thanks for the update, @statman !

11

Hi there mine are and old model aswell and I seem to be having the same issue is the programming all done inside the app?

image
image1920Ă—2560 161 KB

12

Hello!

While I didn’t follow all the details, @statman seemed to indicate success by manually setting the scanning search to RF with a frequency of 433.85 in the Bond app (when first setting up a new device, there is an “Advanced Settings” button at the bottom to allow for that).
I am uncertain if @statman and others manually recorded each of the button presses, or if a template was found and applied after recording only one or two commands.
If no template was found, it is possible unchecking “search remote database” may be required, but try the change from Auto RF frequency to 433.85 first and see if that helps.

13

Hello @Carllarkin,
It looks like the exact same remote I have. I did not try to look for a template as suggested by @residualimages, but if it works, it might prove an easier alternative as it took me a bit of time to record each of the buttons I needed. This being said, once it was done, I never had to change anything and it has been working steadily since.

14

What’s the process for recording the buttons, I’m really struggling to get it to record I’ve tried the frequency you suggested but no luck
:frowning: I’ll speak to support and see what they say.

15

Hi,

TLDD - any tips on getting at AE3 with a light and an RF7091BLN01 remote working.

I have five Aeratron fans that all work with a Bond Bridge, including an Aeratron AE3 with a light.

To get the AE3 to work properly I needed help from the Bond Support crew…back in 2018. The remote model is RF7091BLN01 and the FCC ID is M8CRF7091BLN01. The issue was that while I could get the bridge to learn the commands I could not make the light and fan operate independently. For example if the fan on button is learnt with the light on then the light is turned on when the fan is turned on even if the light was off…which is not great in the middle of the night!

Somehow Bond Support solved the issue and the AE3 works fine.

Some months ago I integrated the Bond Bridge into Home Assistant. All the devices were imported correctly except the AE3. When I went looking I noticed the AE3 does not have a local token and has a couple of toggles to access device settings as opposed to three dots. So I tried to setup the AE3 again and I have struck the same problem where the light and fan will not operate independently.

I have had a case open with support for months but unlike is 2018 I have had no assistance.

So in summary there is a way to get the AE3 with a light and RF7091BLN01 working however it is a mystery how…and I think only Bond support can help.

Could be wrong.

16

Hi.

Based on this thread I have been able to get 4 of my 5 fans set-up. I ended up having to manually map as the mapping returned from N1 wasn’t quite correct it didn’t return an on command.

With that said for the 5th fan I have only been able to map on and off functions. This seems to be a later iteration of the fan with a different FCCID - https://fccid.io/2AAZPDC9

Any support would be great

17

Just an update, for those with a AE3\AE3+ with the DC9 remote it is currently not supported by bond.

I have only been able to get On \ Off working. Will post updates if things change.

1 Like
18

Any updates? I would reallylove to know if Bond Bridge works with the new DC9 remotes (2022+ Aeratron fans). I purchased 4 for them for my home.

19

I have just added a bridge for 5 DC9 (FCC 2AAZPDC9) controlled AE3+ fans, a Martec fan, and 12 ACMEDA roller blinds. No problems with the blinds or the Martec, but I have the same sort of AE3+ problems as @SJJ and others. I am starting on my journey to solve this :slight_smile:

20

I’ve hacked it. :slight_smile:

Well, partially. I have an Aeratron AE+3 and I now have full functionality for the following:

  • Power Off
  • Speed 1
  • Speed 2
  • Speed 3
  • Speed 4
  • Speed 5
  • Speed 6

These don’t work:

  • Power On
  • Direction Toggle

BTW, none of the buttons above match the buttons on the remote. Here are the buttons on the remote:

  • On/Off (toggle)
  • Fwd/Rev (toggle)
  • Speed Up
  • Speed Down

So, how did I hack it? And why could I not hack Power On and Direction Toggle?

I figured out that the remote remembers state. Not the state of the fan, but the state it remembers putting the fan into. It has a display and it shows this state. If I change the actual state of the fan by changing a speed setting via the BOND Bridge, the remote does not reflect this change.

Taking that into consideration with the fan speed commands indicated here: aeratron/src/webremote.ino at master · mgkoenig/aeratron · GitHub , I was able to deduce that when you hit “Speed Up” that the remote checks it’s current remembered speed, then sends an explicit command to the fan to jump to the next speed.

I was able to do the same with Power Off, by putting the remote into the Power On state, then training by hitting the toggle, which sends the “Power Off” signal.

However, I couldn’t do the same with Power On, because the remote remembers the last speed while on, then sends that speed explicitly to turn on the fan. The best I can do (without implementing some code logic), is to train the Power On function to send a single speed signal. For now, I’ve opted to just send a speed signal directly, and do without a Power On button.

Direction toggle doesn’t work – not really. I can train it to go forward with the “Summer” button and backwards with the “Winter” button, but once it has changed to “Winter” mode, if I hit a speed button, it changes to that speed in the “Summer” direction, because I trained the speed buttons while it was in forward mode. Therefore, the speed settings also explicitly send the direction too.

I’ve contacted BOND Support and have offered to create a profile that will work for these fans if they give me access to the underlying code logic. But I thought I’d post this info here too, in case it helps anyone in the community right away.

One more tip for the community – after programming each button as I did above, just lie to the BOND Bridge app and say, “yes, it worked”. Because if you send your fan a command that is the same as the one you last sent, it won’t beep, and it won’t change anything. Once you’ve finished the training, go back and try each of the commands again and you’ll hear the beeps and see the actions happen.

BTW, here’s the FCC ID for my remote:

FCC-ID for Aeratron AE+3 Remote
FCC-ID for Aeratron AE+3 Remote1920Ă—2550 152 KB

Cheers,

-Brian

1 Like