Radiotherm temperature reading bug

[andyat (Andy)]

Hi all, I’ve been playing with Radiotherm CT50 for few weeks now, it is working relatively well, but sometimes it reads current or target temperature as -18.3 C, which is getting quite annoying. I suspect something is wrong with polling, maybe its being polled too often or just random wifi dropouts or something, so that HA cannot get a value for temperature and assumes in is -1 F == -18.3 C.

I looked at the logs and saw error “Human readable value not known for raw value -1”, so I tried fixing this file radiotherm/radiotherm/fields.py at master · mhrivnak/radiotherm · GitHub not to raise that KeyError. It might have helped for a while (or maybe I just got lucky for that time), but then I saw those -18.3 again.

I tried to increase scan interval like this, but it did not help.

climate:
  - platform: radiotherm
    hold_temp: true
    scan_interval: 60
    host:
      - 192.168.1.6

The only relevant thing I get from log after fixing the above things is the following.

16-12-18 21:11:37 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=climate.livingroom, new_state=<state climate.livingroom=idle; mode=NA, operation_mode=idle, unit_of_measurement=°C, fan=Auto, min_temp=7.0, current_temperature=-18.3, friendly_name=livingroom, temperature=22.8, operation_list=[‘auto’, ‘cool’, ‘heat’, ‘off’], max_temp=35.0 @ 2016-12-18T21:11:37.444000-08:00>, old_state=<state climate.livingroom=heat; mode=Heat, operation_mode=heat, unit_of_measurement=°C, fan=Auto, min_temp=7.0, current_temperature=22.5, friendly_name=livingroom, temperature=22.8, operation_list=[‘auto’, ‘cool’, ‘heat’, ‘off’], max_temp=35.0 @ 2016-12-18T20:46:06.846823-08:00>>

Any suggestions on how to proceed with debugging this? I don’t have much experience with linux networking, but I thought if there is a way to get some kind of trace/log of network traffic to thermostat, it should probably be helpful.

[Zen]

Check your fields.py file again. If you recently updated Home Assistant, it is possible your changes got clobbered.

I have a CT50 as well, and can confirm that the radiotherm package reports a value of ‘-1’ anytime it gets a result it doesn’t understand from the thermostat. (I believe this includes a timeout). I’m not sure if it’s the thermostat or the code, but this happens on average a dozen or more times a day here. If your values are all being converted from F to C, that would explain the ‘-18.3’ you keep seeing.

The scan interval doesn’t seem to have any effect.

As a stop gap, you could have your template check for and discard that specific value, although a better fix would be for the radiotherm package to get updated. The package being used by Home Assistant seems abandoned by it’s maintainer. There are PRs over a year old waiting to be pulled in. Maybe switching to a newer fork, or forking a branch just for HASS would be appropriate?