-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
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
Unable to save IP address into Host field in Daikin AC integration after upgrade #123918
Comments
Hey there @fredrike, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) daikin documentation |
Will be fixed by #123623 |
Sorry, could you please help me to understand why is this issue marked as 'closed' - I ask this, l am not able to reconnect to the Daikin integration with the same issue reported above due to recent HA core upgrade. |
It has been fixed on the |
The problem
Integration to Daikin BRP072A42 module was previously working well for years.
Stopped working with "Entity not available" message upon upgrade to core-2024.8.1
I can still call the daikin webservice directly via web browser, so I know the api is up at the Daikin end.
Upon removing and reinstalling the Daikin AC Integration, when inputting the IP address (which is the only field required for this module), the field clears itself upon "saving" i.e doesn't retain the IP address.
What version of Home Assistant Core has the issue?
core-2024.8.1
What was the last working version of Home Assistant Core?
previous version to above
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Daikin AC
Link to integration documentation on our website
https://www.home-assistant.io/integrations/daikin
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Daikin BRP072A42 Wifi module. This does not need an API key or password.
The text was updated successfully, but these errors were encountered: