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
With the July Home Assistant release my previously unsupported pool heat pump started working, providing a switch, a temperature setting and a temperature sensor entity. However this temperature sensor displays -22, the lowest possible value for the tuya sensor. This is because the device does not actually use this field
Expected behavior
The integration should use the "temp_effluent" sensor (which is the temperature of the pumped water) instead of the "temp_current" which is always the default -22. "temp_set" is correctly read as the desired temperature.
Describe the bug
With the July Home Assistant release my previously unsupported pool heat pump started working, providing a switch, a temperature setting and a temperature sensor entity. However this temperature sensor displays -22, the lowest possible value for the tuya sensor. This is because the device does not actually use this field
Expected behavior
The integration should use the "temp_effluent" sensor (which is the temperature of the pumped water) instead of the "temp_current" which is always the default -22. "temp_set" is correctly read as the desired temperature.
Diagnostics for integrations and devices
tuya-04e2f407698a95f9a43d78459971b4f9-Pool Heat Pump-68b4e7495ba2b7fb8fcc9d5fbd6b52a9.json
Screenshots
Home Assistant Version
2024.7.2
Device info:
Could not get this the described way. Is it still supposed to be custom_components.tuya_v2: debug?
Device specifications:
Could not get this the described way. Is it still supposed to be custom_components.tuya_v2: debug?
Additional context
The sensor "compressor_strength" is correctly filled as a percentage, and "mode" contains the enum value ("heating") in case you want to add it too :)
The text was updated successfully, but these errors were encountered: