Climate device turns on instead of off when part of a scene (dakin devices only)

[sddgit]

The problem

I’m using the Daikin integration. As part of a “Good Night” scene, I turn off the climate device. This works fine when the device is already on, but if it is off at the time the scene runs, the device is turned on. Logbook shows changed to Heat triggered by HomeKit send command set_temperature to TargetTemperature to 22°C The scene’s button if the Home app turns solid white at first, then goes off again, presumably because the climate device is not in the required off state.

If the device is off and I ask Siri to turn it off, it properly stays off, but doesn’t when part of a scene. I have another climate device which doesn’t exhibit this behaviour.

What version of Home Assistant Core has the issue?

2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

homekit documentation homekit source _{^{(message by IssueLinks)}}

[exzz]

it may be similar to this issue : https://github.com/home-assistant/core/issues/73309

[home-assistant[bot]]

Hey there @fredrike, mind taking a look at this issue as it has been labeled with an integration (daikin) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `daikin` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign daikin` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

daikin documentation daikin source _{^{(message by IssueLinks)}}

[sddgit]

it may be similar to this issue : #73309

Yes, exactly that. Thanks for pointing that out. The issue doesn’t seem to have had any progress.

[dbart37]

Hi, I have the same issue also but only with the Daikin integration. When I set a scene with climate to cool for example, It work. When I set a scene to turn off climate : it saves the state in config but when I call the scene, it turn off the climate but instantly turn on

Changed to Cool triggered by service scene.turn_on 11:01:31 AM - 3 minutes ago Turned off triggered by service scene.turn_on 11:01:31 AM - 3 minutes ago

[fredrike]

Please share the yaml of the scene.

[sddgit]

I should have made it clearer that I’m talking about a Homekit scene, not an HA one. The linked issue above explains why this seems to be happening - turning off a unit that is already off (in a scene) results in a target temperature change alone, and the Daikin plugin interprets this as a request to turn the unit on. The linked issue is a request to review this behaviour.

[fredrike]

@barshow did have a suggestion for solving this that resulted in #94372.

I think this might have been solved in https://github.com/home-assistant/core/pull/95656 please update and connect back to me and @barshow.

[sddgit]

I’m sticking on 2023.5.4 for now, because another integration had breaking changes in 2923.6 that aren’t yet fixed. I’ll test as soon as I can.

[barshow]

Yeah, 2023.7.2 looks like it should fix it.

[sddgit]

Sure seems to be fixed in latest HA. Thanks all!