Tasmota: iFan02 Unable to Pair Remote

[jumblies]

Describe the bug
Also, make sure these boxes are checked [x] before submitting your issue - Thank you!

• [x] Searched the problem in issues and in the wiki
• [x] Hardware used : iFan02 with 2.4 GHz remote
• [x] Searched google groups
• [x] Provide the output of command STATUS0 :

21:32:25 MQT: stat/iFan1/STATUS = {"Status":{"Module":44,"FriendlyName":["iFan1"],"Topic":"iFan1","ButtonTopic":"0","Power":6,"PowerOnState":1,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0}}

To Reproduce
Difficult without dissociating remote from iFan02 Unit. But, pairing functions on iFan02 do not work with Tasmota Firmware.

Expected behavior
Long press on iFan02 Unit should cause remote module (daughterboard) to enter pairing mode. Per user guide itead link

Additional context
To PAIR remote with iFan02 Unit requires use of button, but the button is coupled with Tasmota functions which appears to be interfering with re-pairing the remote with the iFan02 Unit. There is no way to disable the button in Tasmota. It may be that Tasmota FW is intercepting button press for tasmota behavior and remote module not being triggered for pairing. This may be a problem with the daughterboard referenced in #3395.

Tried removal of remote from casing, pressing button on back while holding battery in place and restoring power to iFan02 without success.

Maybe a disable switch state could be used?

The other option is removal, flashing of factory FW, pair remote, restore Tasmota. :-(

[arendst]

As the button is configured to GPIO0 you might want to try to temporary change the ifan module configuration from iFan02 to Generic. This way the button is not handled by Tasmota and you must be able to pair the remote.

I haven't tried it though ;-)

[jumblies]

Great thought. I tried it and no dice. Can't find my factory firmware either. Poo.

[arendst]

I'm out of options.

I've tried some other things like using the led on GPIO13 to tell the microcontroller wifi is present (see schematics) but both settings do not trigger pairing either.

Anyone with a solution other than using the original firmware is welcome.

NB As the pairing is handled by the microcontroller I see no reason why the original firmware (on the esp8266) would solve the issue.

[jumblies]

No worries. I'm going to ask and see if has the factory firmware and give it a whirl.

[jumblies]

@arendst

Thank you for your patience. It was an ID 10 T error. Apparently if the voltage in the button cell hits 2.9, that's enough to cause it to malfunction.

UPDATE: HOLY CRAP, the oldest trick in the book.

The battery cell went bad. It was 2.9 V on the voltmeter which I figured would be fine. Even tried a couple of different ones. I can't believe I fell for that. FACEPALM

[janneslr]

Hi, I have exactly the same issue, but my battery measures 3.1V. Any suggestion

[janneslr]

Hi, just an update on this. I manage to sort out my issue. The device needs to be connected to AC power for the remote do function.

[Wihanh]

any other ideas to try here? Remote stopped working when i flashed with sonata.exe
I am powering it from 240v cell battery is at 3.2v i can't seem to get anything from it, the several different repairing instructions from power cycling the sonoff while holding the pair button and battery in place, to holding the button on the sonoff, nothing seems to help.

[jumblies]

I found the remote to be very fickle with batteries and got both of mine
working again. I think the remote have a quiescent power draw that causes
problems. On one, I put a switch to cut battery when I'm not using it.

My advice based on my experience is to try several different batteries and
the standard pairing procedure. It's highly unlikely to be an issue with
tasmota or the ESP. The battery caused such confusing behavior, I became
convinced it was something else.

On Thu, Dec 27, 2018, 7:25 AM Wihanh <[email protected] wrote:

any other ideas to try here? Remote stopped working when i flashed with
sonata.exe
I am powering it from 240v cell battery is at 3.2v i can't seem to get
anything from it, the several different repairing instructions from power
cycling the sonoff while holding the pair button and battery in place, to
holding the button on the sonoff, nothing seems to help.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3545#issuecomment-450141492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXFbvy72AmPFw7Tzi5WAxrPmms8R2NiLks5u9LwfgaJpZM4WGlCf
.

[Wihanh]

I found the remote to be very fickle with batteries and got both of mine working again. I think the remote have a quiescent power draw that causes problems. On one, I put a switch to cut battery when I'm not using it. My advice based on my experience is to try several different batteries and the standard pairing procedure. It's highly unlikely to be an issue with tasmota or the ESP. The battery caused such confusing behavior, I became convinced it was something else.
…
On Thu, Dec 27, 2018, 7:25 AM Wihanh @.* wrote: any other ideas to try here? Remote stopped working when i flashed with sonata.exe I am powering it from 240v cell battery is at 3.2v i can't seem to get anything from it, the several different repairing instructions from power cycling the sonoff while holding the pair button and battery in place, to holding the button on the sonoff, nothing seems to help. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#3545 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AXFbvy72AmPFw7Tzi5WAxrPmms8R2NiLks5u9LwfgaJpZM4WGlCf .

Thx, can you clarify the exact procedure you used to re-pair? and can i confirm you did it with Tasmota loaded?

[jumblies]

I did it with Tasmota. I even flashed the original firmware but it didn't change anything. As others have noted, the remote is completely separate subsystem that just feeds info to the ESP.

I left my Tasmota configured functionally and confirmed all activity over MQTT before fiddling with anything else. I recommend that so it removes a variable.

Reflowed the daughter board pins as others suggested. No difference.

Replaced the battery holder with one from Ali in case that was the issue. No difference

Replaced the battery with a brand new battery and pressed the button on the front of the remote until the fan unit beeped. That's it. Just it is supposed to work. I was surprised and felt stupid but these remotes are really flaky. Erratic behavior if the cell isn't full.

think I measured mA draw at one point but can't remember what it was. I think that if there is any undue internal resistance in the battery, the remote misbehaves.

[Wihanh]

So you didnt power cycle or press anything on the fan controller only on the remote?

Which button did you press the hidden silver disc inside or just one of the remote buttons?

On 27 Dec 2018, at 11:43 pm, jumblies [e-mail] wrote:

I did it with Tasmota. I even flashed the original firmware but it didn't change anything. As others have noted, the remote is completely separate subsystem that just feeds info to the ESP.

I left my Tasmota configured functionally and confirmed all activity over MQTT before fiddling with anything else. I recommend that so it removes a variable.

Reflowed the daughter board pins as others suggested. No difference.

Replaced the battery holder with one from Ali in case that was the issue. No difference

Replaced the battery with a brand new battery and pressed the button on the front of the remote until the fan unit beeped. That's it. Just it is supposed to work. I was surprised and felt stupid but these remotes are really flaky. Erratic behavior if the cell isn't full.

think I measured mA draw at one point but can't remember what it was. I think that if there is any undue internal resistance in the battery, the remote misbehaves.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[jumblies]

I tried the power cycle holding the hidden button on the back of the opened
remote but there wasn't any indication that it did anything.

I used the standard pairing method power instructions using the front
button.

I feel your pain. It's frustrating.

On Thu, Dec 27, 2018, 10:26 PM Wihanh <[email protected] wrote:

So you didnt power cycle or press anything on the fan controller only on
the remote?

Which button did you press the hidden silver disc inside or just one of
the remote buttons?

On 27 Dec 2018, at 11:43 pm, jumblies [e-mail] wrote:

I did it with Tasmota. I even flashed the original firmware but it
didn't change anything. As others have noted, the remote is completely
separate subsystem that just feeds info to the ESP.

I left my Tasmota configured functionally and confirmed all activity
over MQTT before fiddling with anything else. I recommend that so it
removes a variable.

Reflowed the daughter board pins as others suggested. No difference.

Replaced the battery holder with one from Ali in case that was the
issue. No difference

Replaced the battery with a brand new battery and pressed the button on
the front of the remote until the fan unit beeped. That's it. Just it is
supposed to work. I was surprised and felt stupid but these remotes are
really flaky. Erratic behavior if the cell isn't full.

think I measured mA draw at one point but can't remember what it was. I
think that if there is any undue internal resistance in the battery, the
remote misbehaves.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3545#issuecomment-450281661,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXFbv6OldDvwR4B9Hf2CtHI2KgMEKqIbks5u9Y9RgaJpZM4WGlCf
.

[slavekjurkowski]

Can confirm, experienced same pairing issue as described. I replaced the battery with a fresh cr2032 which is .7mm thicker. slightly more battery capacity and paired right away.

[Wihanh]

Still not clear on the exact pairing procedure

What button do you press?

On 30 Dec 2018, at 4:37 pm, slavekjurkowski [e-mail] wrote:

Can confirm, experienced same pairing issue as described. I replaced the battery with a fresh cr2032 which is .7mm thicker. slightly more battery capacity and paired right away.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[jumblies]

bottom button front of remote. In another longer ifan thread I posted a picture of the instructions.

[lanefu]

TAKE OFF THE BACK COVER OF THE REMOTE. THERE IS A SECRET BUTTON THERE.

sorry to shout... I'd been pulling my hair out until I saw this video. I was able to pair my unused remote with my iFan02 running Tasmota

https://www.youtube.com/watch?v=TLiVOAi2Cn4

[Wihanh]

Yeah, not sure if I am just a idiot or my remote or unit is faulty, but i can't get anything out of it.
I tried with the thicker CR2032 battery.
I tried pushing the hidden disk as lanefu mentioned, i tried pressing it and power cycling, just pressing it, pressing it and then pressing other buttons while it is flashing.
I tried pushing the bottom button on remote while unit is powered, i tried holding it while power cycling.
I tried just pressing it a bunch of time with the unit powered on.
The unit is powered with 240v from the mains. It works fine from mqtt, but nothing from the remote.
I haven't reflowed the daughter board, but i think i might just order another unit and see it is just this one that is having a problem.
BTW, the guy in the video mentioned above seems like it is not working, because you can't here the relays click afterward, so i am guessed this is a video he made to show itead how it doesn't work.
I commented on it anyway 3 weeks ago asking him if it worked, but there was no response.

[Wihanh]

BTW when i first put my battery in, my remote led comes on and stays on until i press button 2, then it goes out and behaves normally. is this normal?

[Wihanh]

i see itead website now says retired for this unit.

[iJuiceman]

I also had problems with the remote not working on my Tasmota iFan02, but the new 2032 battery fixed the problem.

[fquinto]

After a long time trying for me the procedure has been:

• Using the original firmware (from Itead Sonoff).
• Check battery: not less 2.85v and not 3.3v. Only runs very near 3v.
• Put the new battery: press the hide button (open remote controller for that)
• The LED is like "searching"
• Connect the ifan02 to the AC current or if connected, reboot.

I think the join during the reboot of the main unit.

Hope this helps.

[HadiHassaoui]

I have two iFan02 modules, one in living room, and one in Bedroom.

The one in the living room was installed first, and was paired with the remote for one week until I installed the Bedroom fan. I manage to pair the new remote with the Bedroom fan.

But then the LivingRoom remote won't connect to the fan. Based ont fquinto's solution I did the following steps:

• Using Tasmota 6.5.0
• Change battery for CR2032
• Turn of the power (breaker)
• Press the Hidden button (made a hole in the plastic to use it with a pin)
• Turn on the power (breaker)
• The flashing stopped immediately
• Press the Pair button (the one the kind of WIFI icon)
• Pairing successfull.

Then, Surprise the remote in the Bedroom won't pair anymore. Did the exact same procedure for the bedroom (without changing battery), and BINGO both remote are paired.

For me the problem came from having two iFan02 module.

[Sineos]

For future reference: Restarting Tasmota did not work for pairing. Mine needed a complete power cycle:

1. AC mains off
2. Press hidden button on the remote
3. AC mains on