Actual temperature unit conversion error reported in climate sensor

[mattsmallman]

System Health details

System Information

version	core-2023.7.3
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.11.4
os_name	Linux
os_version	5.15.0-78-generic
arch	x86_64
timezone	Europe/London
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4812
Installed Version	1.32.1
Stage	running
Available Repositories	1265
Downloaded Repositories	21

Home Assistant Cloud

logged_in	true
subscription_expiration	22 August 2023 at 01:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	false
remote_server	eu-central-1-6.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	8
resources	7
views	7
mode	storage

Recorder

oldest_recorder_run	15 July 2023 at 22:03
current_recorder_run	29 July 2023 at 07:52
estimated_db_size	405.53 MiB
database_engine	mysql
database_version	10.11.4

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of currently previous issues..

Describe the issue

Actual temperature is reported as - C, which is obviously not correct. I suspect this is an issue with unit conversion. My Ooler is set up in Celsius.

I recall a similar issue with a previous MQTT integration and suspect that Ooler may report actual temperature in Farenheight regardless of temperature unit set but am unable to figure out how to see the raw data in order to check.

P.S. Thanks for creating this integration - It would be great to expose some of the other diagnostic data if you get a chance

Reproduction steps

1. Install as per instructions with Ooler set in celsius

...

Debug logs

n/a - Please advise if required

Diagnostics dump

n/a - Can't locate

[plucpel]

Had the exact same issue. I tried to modify the conversion logic on my own, but could not get it to work properly anyway. Happy to help test if anyone comes up with a solution.

[cpayne14]

Having the same issue here too, outside of this works amazing :)
Thanks!

[PostLogical]

Glad to see others are using this! Sorry I've been MIA (two kids being born will really sap your time). I don't use Celsius myself, so unless somebody else comes up with a solution I'll have to find some time when I can switch mine over to test. Hopefully that can happen in the next couple months, but I'll look at the code regardless to see if anything jumps out.

[omega015]

I opened a new case but realised this was a duplicate of this case. Anyway it appears that the temperature error when using celcius is due to a conversion on the celcius value already. So I suspect either a double conversion is being done or there is no need for the conversion due to the correct value being presented already.

e.g. device reporting current temp of 26°C but HA shows Current temperature -3.3 °C

Taking the 26°C and converting that into F ( 26-32 * 5/9) = -3.3°C

could this be the issue ? _attr_temperature_unit = UnitOfTemperature.FAHRENHEIT (climate.py line 63)

[omega015]

In addition to my findings, it seems like some forks of your integration already have some handling for celcius temps.

master...wesjdj:ooler:master