Roth Touchline - reloaded

Hi’ @pilehave
Sorry to ‘ping’ you like this.
I’ve previously had your HA Roth Touchline integration installed and running.
Tried to reinstall today, but only got a device update error like below for each thermostat attached.

Should the component actually work or has further updates/development been abandoned ?

2023-09-24 17:49:02.446 ERROR (MainThread) [homeassistant.components.climate] touchline: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/", line 573, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/", line 938, in async_device_update
    await hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.11/concurrent/futures/", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/touchline/", line 86, in update
    self._current_temperature = self.unit.get_current_temperature()
  File "/usr/local/lib/python3.11/site-packages/pytouchline/", line 158, in get_current_temperature
    return int(self._parameter["Temperature"]) / self._temp_scale
ValueError: invalid literal for int() with base 10: 'None'

Update: All good now, my bad…

The Roth app configuration apparently wasn’t done correctly, so I redid everything from scratch.

  • Set static ip for my master device in my router. Router rebooted
  • Power cycled both master and slave device
  • Reconfigured one device as master and second device as slave
  • Started new configuration in the Roth Touchline app. Searched for master and all 10 thermostats popped up (5 master and 5 slave)
  • Renamed all thermostats in the app before entering the configuration parameters in HA
  • Entered configuration parameter in HA config and rebooted HA
  • All thermostats popped up nicely with correct naming
  • All devices still match named entity after HA reboot (previous issue with slave entities not named in Roth app)

I actually didn’t rename all thermostats before firing up the HA integration :roll_eyes: This caused duplicate entities when i rebooted HA (or at least I thought it did). Core issue here was that Chrome cached old non existing entities. I flushed the cache for the HA local page and the dublets was permanently gone :tada: :slightly_smiling_face:

Confirmed working on Home Assistant 2023.9.2 with master/slave configuration - 10 thermostats in total

I’m a happy camper now!! :sunglasses: