You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 7, 2021. It is now read-only.
climate attributes 'temperature' and 'current_temperature' seem to always send back the same value, the target temperature for both
( FYI : in the current main tuya integration, current_temperature was always null. I switched to ha_tuya_custom in hopes to find a fix for this but... while there now is a reported value, the reported value is wrong )
The text was updated successfully, but these errors were encountered:
When current_temperature information from Tuya API is not available, the integration use the target temperature value, because is the only information available. As alternative the integration also allow to configure an external temperature sensor to use instead (see ReadME for details). This are the only 2 possible option due to Tuya API limitation.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
climate attributes 'temperature' and 'current_temperature' seem to always send back the same value, the target temperature for both
( FYI : in the current main tuya integration, current_temperature was always null. I switched to ha_tuya_custom in hopes to find a fix for this but... while there now is a reported value, the reported value is wrong )
The text was updated successfully, but these errors were encountered: