-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug
[Samsung_HVAC]: Project reporting higher indoor temp than SmartThings or AC itself
#225
Comments
Maybe I can help out here. Maybe it could be exchanged to this on on the climate controls..... |
Perfect, I will test this out later today! |
What config did you use? I tried mine like this and it's reporting 412 degrees Fahrenheit
|
Tested also this. I got 200C when indoor unit shows 20C, and the real measured temp is 21C.
|
Doing this seems to work perfectly for me. custom_sensor:
- name: "Indoor Temperature Fixed"
id: sunroomac_temp_fix
message: 0x4204
device_class: temperature
state_class: measurement
unit_of_measurement: "°C"
accuracy_decimals: 2
#Add filter as it reports with an extra zero
filters:
- multiply: 0.1 @dierkgrossfeld Does yours also report with the decimal in the wrong location? I'm going to figure out how to override what is set for the climate entity. |
ah yes, sorry, forgot to mention this. |
The problem
Hello! I noticed recently that the Samsung HVAC component seems to report noticeably higher indoor temperatures than what the AC has on its display or in SmartThings. For instance, my AC is set to 62, says 64, but in Home Assistant it is displayed as 68.
I thought about changing
room_temperature_offset
but if the AC is reporting the correct temp that shouldn't be needed?ESPHome Version
2024.10.2
Samsung HVAC Component Version
latest
Home Assistant Version
2024.11.2
AC Type
NASA
Indoor AC Unit Model
AR12TSFABWKNCV
Outdoor AC Unit Model
AR12TSFACWKX
ESP Device Model
M5STAMP Pico
Connection Points
F1/F2
ESPHome Logs
No response
Samsung AC Logs
No response
YAML Configuration
Additional Details
No response
The text was updated successfully, but these errors were encountered: