Thank you so much for this integration!
I’m on day two of learning HA but just had a quick question … Changes made via HA are instantly reflected by the thermostat. But changes made via the thermostat take about a minute to be reflected in HA. I was curious if this is a polling limitation by the API?
Is this normal operation, or do I need to setup some additional things? Thank you!
Were you able to confirm if this work with the Touch model?
Is there an HA integration that supports this family of Daikin thermostats? I have a ATST-CWE-BL-A Amana Smart Thermostat. I have not found it yet if so. There is a screen in the thermostat where I can generate an API key so that is a positive sign the device supports integrations like HA. Thanks!
I also have the Touch model and installed the Daikin One with the HACS Daikin One and visually I see all the information… Temp, humidity etc but I cannot change any of the settings. Like changing the temp will revert back to the temp it was set at. I would love to be able to help with getting this working with the Daikin Touch but don’t know what I need to share.
It looks like it runs the same software as the Daikin One. Have you tried this one?
If you can go through the API document on the GitHub and send me the output of the commands, I might be able to figure something out.
I’ve been using the integration with my DaikinOne+ thermostat for several years. For many months, whenever I change the temperature setpoint, it will immediately revert back to the previous value, usually within 3-5 seconds. If I set it again to the new value, it usually (not aways) stays as expected. This seems to happen not just for tempeature, but for any change such as fan or mode. Has anyone found this same problem? If so, hopefully there is a workaround available? Thanks!
The problem I’ve had with the API is that the thermostat doesn’t read and update it very frequently. Likely the command goes through, but when the integration reads from the API after it’s set interval, it still hasn’t been updated by the thermostat, so it reverts back to the previous state until the thermostat updates it after accepting the command. I’ve done some things to try and mitigate this issue, but it’s still not great. If you let it sit for a minute after making your change, does it eventually show what you changed it to? Check the thermostat itself after a few seconds too.
You’re correct. When I change the setpoint, it immediately reverts to the previous value. But if I leave it alone at the wrong setpoint for about 120 seconds, and then refresh the screen, only then will it display the new setpoint as I had intended. If I refresh the page earlier than 120 seconds, it shows the wrong (old) value.
Perhaps whenever the setpoint is changed, the display update could be suppressed for a duration of time? It would only mask the underlying issue, but would be a functional stopgap?