home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.6k stars 30.76k forks source link

Can not get the actual configured temperature #126454

Closed apographon closed 4 weeks ago

apographon commented 1 month ago

The problem

I want to use external window sensors to push the tado into "off" mode and to restore the previous configured temperature after closing the temperature. My automation always put the current temperature (e.g. 22.4°) as new temperature after closing the windows instead the defined temperature (e.g. 10°)

alias: tado-wohnzimmer description: >- Speichert den aktuellen Status des Tado Thermostats und stellt ihn nach dem Schließen des Fensters wieder her. trigger:

Trace trace automation.tado_wohnzimmer 2024-09-22T20_41_24.157654+00_00.json trace automation.tado_wohnzimmer 2024-09-22T20_40_39.910909+00_00.json

What version of Home Assistant Core has the issue?

2024.9.2

What was the last working version of Home Assistant Core?

2024.9.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

tado

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

joostlek commented 1 month ago

I am missing the question here, what is not working? What have you tried? What do you expect it to return?

apographon commented 1 month ago

Maybe I'm in the wrong GitHub area to ask support. I need to get the actual configured temperature of my tado thermostat.

joostlek commented 1 month ago

This sounds like a support question indeed. Please refer to discord or the forums

issue-triage-workflows[bot] commented 1 month ago

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.