iFan4 - The FanSpeed stat message is not sent when 'Power0 off' is called

[HonzaCZ]

PROBLEM DESCRIPTION

Issuing the command Power0 off turns off the light and stops the fan, but it doesn't send an MQTT status message about the change in FanSpeed.

This issue affects all Power0 commands (off, on, toggle) — no MQTT message is sent regarding changes to the fan state.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Read the Contributing Guide and Policy and the Code of Conduct
• Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• Problem is not scripter related, in this case open a discussion and tag gemu2015
• Device used (e.g., Sonoff Basic): Sonoff iFan04-H
• Tasmota binary firmware version number used: 15.0.1, also 14.1.0.4
  • Pre-compiled
  • Self-compiled
• Flashing tools used: OTA
• Provide the output of command: Backlog Template; Module; GPIO 255:

  Configuration output here:
[23:35:03] stat/tasmota_lvn_ifan/RESULT {"NAME":"Sonoff iFan04-H","GPIO":[32,3200,5735,3232,0,0,256,512,226,320,225,227,0,0],"FLAG":0,"BASE":71}
[23:35:04] stat/tasmota_lvn_ifan/RESULT {"Module":{"0":"Sonoff iFan04-H"}}
[23:35:04] stat/tasmota_lvn_ifan/RESULT {"GPIO0":{"Button1":32},"GPIO1":{"Serial Tx":3200},"GPIO2":{"Option A8":5735},"GPIO3":{"Serial Rx":3232},"GPIO4":{"None":0},"GPIO5":{"None":0},"GPIO9":{"Relay_i1":256},"GPIO10":{"Buzzer_i":512},"GPIO12":{"Relay3":226},"GPIO13":{"Led_i1":320},"GPIO14":{"Relay2":225},"GPIO15":{"Relay4":227},"GPIO16":{"None":0},"GPIO17":{"None":0}}

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

• Provide the output of this command: Status 0:

  STATUS 0 output here:
[23:45:28] stat/tasmota_lvn_ifan/STATUS {"Status":{"Module":0,"DeviceName":"Living Room Ceiling Fan","FriendlyName":["Living Room Ceiling Fan"],"Topic":"tasmota_lvn_ifan","ButtonTopic":"0","Power":"0010","PowerLock":"0000","PowerOnState":0,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS1 {"StatusPRM":{"Baudrate":9600,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"##REDACTED##","RestartReason":"Software/System restart","Uptime":"0T07:21:31","StartupUTC":"2025-06-21T14:23:57","Sleep":50,"CfgHolder":4617,"BootCount":34,"BCResetTime":"2024-06-25T22:04:12","SaveCount":866,"SaveAddress":"FA000"}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS2 {"StatusFWR":{"Version":"15.0.1(solctech-ifan)","BuildDateTime":"2025-06-21T14:59:20","Boot":31,"Core":"2_7_8","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8285N08","CR":"429/699"}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS3 {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["##REDACTED##",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS4 {"StatusMEM":{"ProgramSize":536,"Free":468,"Heap":22,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"14325E","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","0F804586","04208001","000000C3","00000000","40000801","00000080","00000000","04000000","00000000","00000000"],"Drivers":"1,2,!4,!8,9,10,12,!16,22,24,26,29,38,62,!68","Sensors":"1,2,5,6","I2CDriver":""}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS5 {"StatusNET":{"Hostname":"tasmota-lvn-ifan-6977","IPAddress":"##REDACTED##","Gateway":"##REDACTED##","Subnetmask":"255.255.255.0","DNSServer1":"##REDACTED##","DNSServer2":"0.0.0.0","Mac":"##REDACTED##","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS6 {"StatusMQT":{"MqttHost":"##REDACTED##","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_8D9B41","MqttUser":"##REDACTED##","MqttCount":1,"MqttTLS":0,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS7 {"StatusTIM":{"UTC":"2025-06-21T21:45:28Z","Local":"2025-06-21T23:45:28","StartDST":"2025-03-30T02:00:00","EndDST":"2025-10-26T03:00:00","Timezone":99,"Sunrise":"05:46","Sunset":"21:57"}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS10 {"StatusSNS":{"Time":"2025-06-21T23:45:28"}}
[23:45:28] stat/tasmota_lvn_ifan/STATUS11 {"StatusSTS":{"Time":"2025-06-21T23:45:28","Uptime":"0T07:21:31","UptimeSec":26491,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","FanSpeed":1,"Wifi":{"AP":1,"SSId":"##REDACTED##","BSSId":"##REDACTED##","Channel":1,"Mode":"11n","RSSI":88,"Signal":-56,"LinkCount":1,"Downtime":"0T00:00:04"}}}

• Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:
23:47:02.540 SRC: MQTT
23:47:02.542 CMD: Grp 0, Cmd 'POWER', Idx 0, Len 3, Pld 0, Data 'off'
23:47:02.546 MQT: stat/tasmota_lvn_ifan/RESULT = {"POWER1":"OFF"}
23:47:02.548 MQT: stat/tasmota_lvn_ifan/POWER1 = OFF
23:47:02.951 CFG: Saved to flash at F8, Count 868, Bytes 4096

TO REPRODUCE

Send Power0 off command.

EXPECTED BEHAVIOUR

When Power0 off turns off fan, it should send stat message about it.

Expected messages would be either:

stat/tasmota_lvn_ifan/RESULT = {"POWER1":"OFF","FanSpeed":0}
stat/tasmota_lvn_ifan/POWER1 = 0
stat/tasmota_lvn_ifan/FanSpeed = 0

or

stat/tasmota_lvn_ifan/RESULT = {"POWER1":"OFF"}
stat/tasmota_lvn_ifan/RESULT = {"FanSpeed":0}
stat/tasmota_lvn_ifan/POWER1 = 0
stat/tasmota_lvn_ifan/FanSpeed = 0

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[sfromis]

Your first rule trigger cannot work, as there is no Power0#State trigger, only for specific power channels, like Power1#State indicated by the payload you posted: {"POWER1":"OFF"}

[HonzaCZ]

Thanks for the confirmation. It was just an workaround attempt — a try to solve the main issue.

[sfromis]

Don't waste the time of all by posting random failed workaround attempts, but instead what you expected to work.

And you are not at all clear about what you even try doing with those rules. You are publishing to a specific topic, and your words could be read to suggest that you expected the published data to have effect on the same device.

If this is the case, do not use Publish, but simply have the command. And to have rules pick up the result of a command executed from a rule, you need to "wrap" it in Backlog.

[HonzaCZ]

I apologize, but I think you’re mostly wasting your own time by misreading or misinterpreting what I wrote. The sections “PROBLEM DESCRIPTION,” “TO REPRODUCE,” and “EXPECTED BEHAVIOUR” are, in my opinion, absolutely clear and understandable. Everything else is just filled in as part of the template. Please, stop focusing on the rules and concentrate on the described problem if you actually want to help.

And no, I don’t want to evaluate it on the same device—I want to evaluate it elsewhere and get the info via MQTT. That’s exactly why I wrote that it doesn’t send info over MQTT, and in the “EXPECTED BEHAVIOUR” section, I explained how I’d expect it to work. That’s also why I used Publish in those rules.

[HonzaCZ]

@Jason2866 Could you please explain why this was converted into a discussion? The issue I described genuinely seems like a bug to me. Or do you really think that calling a command performing 2 actions but confirming only 1 of them is okay?

[Jason2866]

Because you are unclear in your description. By posting a rule which is wrong i thought that's the reason why it fails.

[HonzaCZ]

Sorry, I thought that providing info about the rules and how they behave might help with debugging the issue. It didn’t occur to me that it would spark a whole discussion just about the rules, when the core of the problem is something different. The problem clearly isn’t with the rules themselves. My bad.

I’ve edited the report to remove any mention of the rules. Is the actual problem clearer now? Could you please turn it back into an issue?