I have 6 Daikin units and all are detected and work fine, but there is one “feature” that prevents me from using HA daily over native Daikin app.
When I turn off a unit through HA it changes/resets the AC mode to “auto” no matter what mode was previously selected with the unit.
Is there a way to keep the previous working mode when turning off?
That is really a problem in everyday use, since if some units remain on “hot” (if for example I turn them off by native app, or remote) and some are on “auto” (after I turn them off with HA) I can get mode conflicts.
Please let me know if there is any way around this (even if I can setup “hot” as default mode manually and change it to “cold” in summer, that would be an improvement.).
I’m glad I’m not the only one 
Can’t get no input from component authors unfortunately…tried in a few places.
Did you find out some sort of workaround in the meantime? I don’t know where else to ask 
Sorry to revive such an old thread.
I have opened an issue on GitHub for the problem.
I found I can actually create the scene and while setting to ‘off’ while building, it would turn the AC off, but as soon as I save and go back to scenes and then into the scene, the device doesn’t save the ‘off’ state as per this video https://youtu.be/O_C5ZDeDKp0
So I know the call works to turn off the AC as it did it, just wont save the scene / command.
I tried manually editing scenes.yaml and trying different states and hvac_modes with “off” and “Off” and all sorts.
Did anyone ever find a fix to this?
I’m just trying out scenes now with my Daikin as well. I get a similar thing here. In the scene I can set a mode and during editing of the scene the AC unit responds to a setting, but the mode is not really saved.
It’s like the scene setting control panel is actually the live control panel, not a setting storage/mode dialog at all…
Did you try to create scene on the fly, before the action on “climate”? It worked for me, I could resume the last state of my Daikin unit. An automation for example:
alias: Windows sensor camera genitori (heating)
description: ''
trigger:
- platform: state
entity_id: sensor.camera_genitori_change_per_hour
condition:
- condition: state
entity_id: climate.camera_genitori
state: heat
attribute: hvac_modes
for:
hours: 0
minutes: 5
seconds: 0
milliseconds: 0
- condition: template
value_template: '{{ states(''sensor.camera_genitori_change_per_hour'')|float<-4 }}'
action:
- service: scene.create
data:
snapshot_entities: climate.camera_genitori
scene_id: climate_camera_genitori_before_windows
- service: climate.set_hvac_mode
target:
entity_id:
- climate.camera_genitori
data:
hvac_mode: fan_only
- service: notify.mobile_app_pixel_2_xl
data:
message: >-
Climatizzatore impostato su fan only. Ripristinare l'impostazione
originale
title: Possibile finestra della camera genitori aperta con riscaldamento acceso
mode: single
Using service scene.create to create scene id “climate_camera_genitori_before_windows”
Hi, sorry I’m not quite sure what on the fly means here, but I’ll add some more info from tinkering last night.
It seems although I can use the Daikin AC Integration control panel GUI just fine to set all modes and temperature, it seems that some hvac_mode don’t always work from the actual automation service calls sometimes, I think it might depend on what hvac_mode the AC was in before the automation is triggered.
I’ve stopped trying out scenes now until I understand why it’s not sometimes working in automations.
I think possibly my hvac_modes are not quite all the same as seen on the Daikin integration list.
Leave it with me for now…
I have a question if somebody knows though. What is the function of parameters for settings
New target high temperature for HVAC.
and
New target low temperature for HVAC.
in the automation GUI for climate service calls.
i.e. When would you want to set that and why (independent of the actual target temperature) ?
Thanks guys.
Hi, creating scenes “on the fly” in automation is described here: Scenes - Home Assistant
Bye