5
43
Fork
You've already forked ESP32-Faikout
4

Vertical swing inconsistent behaviour in Home assistant #1010

Open
opened 2026年05月14日 11:33:02 +02:00 by craggus2000 · 20 comments

Hi,
Currently using the Faikout in a FTXP25L5V1B, with Home Assistant and MQTT. noswingh is enabled. When turning vertical swing on via HA, it more often than not does not report back to HA that it has been turned on (on occasion it does, although no pattern to this), however the Faikout WebUI does show correctly that it is on. Setting to off seems to report back consistently.
Normally when using comfort mode from the original remote (which changes the swing and fan speed to auto), pressing comfort button after it being turned on reverts to the previous settings. When doing this via Faikout UI or HA it just turns off comfort mode and turns off swing, doesn't revert the fan speed from auto.

Please note I think this is a fantastic solution, and please don't think I'm nit-picking, just noting differences in the hopes it can be made even better!

Hi, Currently using the Faikout in a FTXP25L5V1B, with Home Assistant and MQTT. noswingh is enabled. When turning vertical swing on via HA, it more often than not does not report back to HA that it has been turned on (on occasion it does, although no pattern to this), however the Faikout WebUI does show correctly that it is on. Setting to off seems to report back consistently. Normally when using comfort mode from the original remote (which changes the swing and fan speed to auto), pressing comfort button after it being turned on reverts to the previous settings. When doing this via Faikout UI or HA it just turns off comfort mode and turns off swing, doesn't revert the fan speed from auto. Please note I think this is a fantastic solution, and please don't think I'm nit-picking, just noting differences in the hopes it can be made even better!
Owner
Copy link

There is quite possibly some interaction in the modes of working within the Daikin, but in any case what is reported back to HA should be consistent. HA has a way to see the status update MQTT messages, so maybe you can check those and what it reports.

I.e. so we can see if Faikout is somehow not reporting correctly (very unlikely if web interface is right), or HA is confused.

There is quite possibly some interaction in the modes of working within the Daikin, but in any case what is reported back to HA should be consistent. HA has a way to see the status update MQTT messages, so maybe you can check those and what it reports. I.e. so we can see if Faikout is somehow not reporting correctly (very unlikely if web interface is right), or HA is confused.

This is everything I can see in the MQTT logs for the Faikout (I've just replaced IP address and MAC address). I am not an expert in understanding it. But basically there should be something corresponding to me turning on the aircon to cool mode at fan speed 1, turning on swing, turning off swing, and turning the unit off again, all from HA. During this time, the unit responded correctly, and the Faikout Web UI showed swing going on and off, but HA didn't show swing going on.

Edit: Attached log file, as pasting didn't work properly.

Incidentally, just to confirm, when I control swing from the Faikout WebUI. Home assistant updates correctly, i.e. that swing is on.

Does this help?

This is everything I can see in the MQTT logs for the Faikout (I've just replaced IP address and MAC address). I am not an expert in understanding it. But basically there should be something corresponding to me turning on the aircon to cool mode at fan speed 1, turning on swing, turning off swing, and turning the unit off again, all from HA. During this time, the unit responded correctly, and the Faikout Web UI showed swing going on and off, but HA didn't show swing going on. Edit: Attached log file, as pasting didn't work properly. Incidentally, just to confirm, when I control swing from the Faikout WebUI. Home assistant updates correctly, i.e. that swing is on. Does this help?
Owner
Copy link

That is not showing the stuff HA is receiving...

That is not showing the stuff HA is receiving...

Hmm ok, not sure where that is then. That me selecting 'All' log types in mosquitto MQTT broker settings.
I'll take another look.

Hmm ok, not sure where that is then. That me selecting 'All' log types in mosquitto MQTT broker settings. I'll take another look.
Owner
Copy link

I am not an HA expert - maybe someone that is can help?

I am not an HA expert - maybe someone that is can help?

Ok, I've installed MQTT explorer. Still becoming acquainted with it but have had a quick look. Bearing in mind I have noswingh enabled - When I turn swing on from HA, MQTT shows this error: failed-set = {"swingh":true}. Could this be related? Is there some logic to look at both swing modes and its not reporting on because both h and v are not on?

Also when subsequently turning off swing, the following shows: failed-set = {"swingh":false}

Ok, I've installed MQTT explorer. Still becoming acquainted with it but have had a quick look. Bearing in mind I have noswingh enabled - When I turn swing on from HA, MQTT shows this error: failed-set = {"swingh":true}. Could this be related? Is there some logic to look at both swing modes and its not reporting on because both h and v are not on? Also when subsequently turning off swing, the following shows: failed-set = {"swingh":false}
Owner
Copy link

OK not sure, I can adjust swing status more (new bet).

OK not sure, I can adjust swing status more (new bet).

Thanks, just installed the new beta. Initial test seems to show swing now reporting correctly. I'll see what I can find in MQTT explorer for the Comfort mode issue next.

Thanks, just installed the new beta. Initial test seems to show swing now reporting correctly. I'll see what I can find in MQTT explorer for the Comfort mode issue next.

Re comfort mode, viewing the status from MQTT explorer:

Using the original remote to turn on Comfort - "fan": "A", "anglev": a number, "comfort": true
Using the original remote to turn off Comfort - "fan": "reverts to previous setting", "anglev": another number, "comfort": false
I say 'a number' and 'another number' because both seem to change depending on where the flap started.

Using the faikout webui or HA to turn on Comfort - "fan": "A", "anglev": a number, "comfort": true
Using the faikout webui or HA to turn off Comfort - "fan": "A", "anglev": another number, "comfort": false

Does this help?

Re comfort mode, viewing the status from MQTT explorer: Using the original remote to turn on Comfort - "fan": "A", "anglev": a number, "comfort": true Using the original remote to turn off Comfort - "fan": "reverts to previous setting", "anglev": another number, "comfort": false I say 'a number' and 'another number' because both seem to change depending on where the flap started. Using the faikout webui or HA to turn on Comfort - "fan": "A", "anglev": a number, "comfort": true Using the faikout webui or HA to turn off Comfort - "fan": "A", "anglev": another number, "comfort": false Does this help?
Owner
Copy link

No, someone else versed with HA may need to look.

No, someone else versed with HA may need to look.

But even taking HA out of the equation the behaviour is the same if using the WebUI (basically via the faikout it doesn't revert the fan to previous setting), so I'm not sure HA is causing the issue. Or do you mean more to do with MQTT explorer?

But even taking HA out of the equation the behaviour is the same if using the WebUI (basically via the faikout it doesn't revert the fan to previous setting), so I'm not sure HA is causing the issue. Or do you mean more to do with MQTT explorer?
Owner
Copy link

It may be how Daikin handles it?

It may be how Daikin handles it?
Owner
Copy link

Closed, someone using #AI

Closed, someone using #AI

Please re open this? I haven't used AI apart from understanding something another issue, and also apologised on there too. This issue is still something I'd like to carry on helping to investigate, if that is acceptable?

Please re open this? I haven't used AI apart from understanding something another issue, and also apologised on there too. This issue is still something I'd like to carry on helping to investigate, if that is acceptable?

I have discovered the reason that the fan speed is reverted when comfort mode is disabled is because the previous setting is stored in the remote (found by the really scientific method of covering the end of the remote and changing settings to prove out). On that basis, could the prevous fan speed be stored in the Faikout to then resend the fan speed command when comfort is turned off, thereby mimicking the original remote behaviour?

I have discovered the reason that the fan speed is reverted when comfort mode is disabled is because the previous setting is stored in the remote (found by the really scientific method of covering the end of the remote and changing settings to prove out). On that basis, could the prevous fan speed be stored in the Faikout to then resend the fan speed command when comfort is turned off, thereby mimicking the original remote behaviour?
Owner
Copy link

"the remote" being what? IR remote?

"the remote" being what? IR remote?

Sorry yes, IR battery remote. ARC480A11 to be exact.

Sorry yes, IR battery remote. ARC480A11 to be exact.

Also just found that when turning on econo mode while comfort mode is already on, reverts the fan speed via Faikout webui.

If using Faikout, econo is turned on first, and then comfort is turned on the fan speed goes to auto. Then turning off econo while comfort is on does not revert the fan speed. So seemingly currently a different behaviour depending on which is turned on first in Faikout.

Behaviour should be that whenever comfort mode is on (even if econo mode is on as well) the fan speed should be auto.

Whenever comfort mode is turned off the fan speed should be reverted. But if both econo and comfort are on together, turning off econo should keep the fan speed to auto as comfort is still on.

Also just found that when turning on econo mode while comfort mode is already on, reverts the fan speed via Faikout webui. If using Faikout, econo is turned on first, and then comfort is turned on the fan speed goes to auto. Then turning off econo while comfort is on does not revert the fan speed. So seemingly currently a different behaviour depending on which is turned on first in Faikout. Behaviour should be that whenever comfort mode is on (even if econo mode is on as well) the fan speed should be auto. Whenever comfort mode is turned off the fan speed should be reverted. But if both econo and comfort are on together, turning off econo should keep the fan speed to auto as comfort is still on.
Owner
Copy link

Well we send the setting, and if that has some knock on effect we get what the Daikin sends, generally.

Well we send the setting, and if that has some knock on effect we get what the Daikin sends, generally.
Contributor
Copy link

Maybe some cross ref with #843 too...

Maybe some cross ref with https://codeberg.org/RevK/ESP32-Faikout/issues/843 too...
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
RevK/ESP32-Faikout#1010
Reference in a new issue
RevK/ESP32-Faikout
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?