Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daikin Integration - temperature setting is missing when switching mode from "Fan Only" to "Heat/Cool" #126089

Open
chiahsing opened this issue Sep 17, 2024 · 8 comments

Comments

@chiahsing
Copy link

The problem

Temperature setting is missing when switching mode directly from "Fan Only" to "Heat/Cool". Switching from "Fan Only" to "Cool" to "Heat/Cool" is fine as the temperature setting is restored when switching to "Cool".

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

daikin

Link to integration documentation on our website

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

Diagnostics information

When the climate device is in fan only mode, there is no temperature setting (because it only actives the fan). When switching from fan only to cool, the temperature setting should be restored, and is restored. When switching from fan only to heat/cool (auto mode), the temperate setting should have been restored, but is not.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

no error logs

Additional information

No response

@home-assistant
Copy link

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.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


daikin documentation
daikin source
(message by IssueLinks)

@fredrike
Copy link
Contributor

This sounds like a frontend issue. Is the behavior as expected using the set climate action?

@chiahsing
Copy link
Author

Using climate.set_hvac_mode still shows the same behavior.

When I switch from heat/cool to fan_only, the temperature still exists in the attribute and has the previous value (e.g. 25). When I call climate.set_hvac_mode to set it to "Heat/Cool", the temperature attribute becomes "null".

@chiahsing
Copy link
Author

chiahsing commented Sep 17, 2024

And when switching to "heat/cool" without temeperature, it falls back to "fan_only" mode after a few seconds. It seems that the integration fails to set the mode, and the integration picks up the mode from the wifi module and orverrides its own inconsistent state (just my guess. I have no knowledge of how this integration works.)

@fredrike
Copy link
Contributor

Which part of the integration are you running? Do you pass password/API-key?

@chiahsing
Copy link
Author

It's a BRP072C42 that needs an API-key.

@fredrike
Copy link
Contributor

I'll have a look in the underlaying library https://github.com/fredrike/pydaikin. It might be a simple solution.

It would be great if you could open an issue there and provide some more logging.

@chiahsing
Copy link
Author

Thanks! Filed fredrike/pydaikin#31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants