-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
Update of climate.xxx is taking over 10 seconds #52739
Comments
daikin documentation |
During the integration initialization we need to perform at least one call to know if the energy consumption is supported by the device, but then if the entities are manually disabled by the user we could disable the HTTP calls in pydaikin |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
My log is full of these messages for 3 Daikin BRP072C42 units. According to the logs, each update consists of 10 requests to each unit, mostly for querying power consumption.
Any of these single requests can take a couple of seconds to complete when requested from curl (either on my raspberry pi, or my PC), so the warnings in the log come as no surprise.
Personally, I don't care about the power consumption of the units - I just want to be warm! Ideally, if I disable the power consumption entities, the requests for that information should not be sent and the update of the climate entities would be completed in a reasonable time.
What is version of Home Assistant Core has the issue?
2021.7.0
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
daikin
Link to integration documentation on our website
https://www.home-assistant.io/integrations/daikin
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
The text was updated successfully, but these errors were encountered: