Clima - limited usage, how it really works?

[lubosramo]

Hello,
I’m having trouble understanding how the Clima function works — or maybe it works correctly, but its usability seems limited.

1. I’m not able to set only the temperature. This was possible in the We Connect ID integration.

2. I’m not able to start/stop the climatization (using the previously set temperature). This was also possible in the We Connect ID integration.

3. When using your native clima card, it seems to ignore the set temperature. It actually starts the climatization successfully, but the temperature set in the clima card is ignored. The behavior is also somewhat strange — I set a temperature and switch to Auto mode, but after 1–2 seconds it switches back to Off. Despite that, the climatization does start in the background. However, I don’t see the updated climatization state in HA for several (quite long) minutes.

4. There are long delays between start/stop (clima, charging) and seeing the changes in Home Assistant. I know the polling interval is 600 seconds, but is it possible to force a refresh sooner after start/stop?

Is this the final state of the integration, or can we expect further improvements?

Thanks.

[tillsteinbach]

I believe all of your problems are related to the slow responsiveness of the car when updating values and the long update interval.
The solution is to more aggressively poll after setting something, this is on my list to implement, but I don’t have time right now. If a developer reads this and wants to contribute, please contact me. I can explain what to do.