Coming from this issue: rvdbreemen/OTGW-firmware#270. Basically, when I had my presoldered, preconfigured OTGW from nodo shop turned on without being connected to a boiler / thermostat (to make sure I could load it in HA before physically installing it), I got this error when loading it in Home Assistant with the OTGW integration:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/opentherm_gw/__init__.py", line 75, in async_setup_entry
await gateway.connect_and_subscribe()
File "/usr/src/homeassistant/homeassistant/components/opentherm_gw/__init__.py", line 119, in connect_and_subscribe
status = await self.gateway.connect(self.device_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyotgw/pyotgw.py", line 58, in connect
await self.get_status()
File "/usr/local/lib/python3.13/site-packages/pyotgw/pyotgw.py", line 270, in get_status
boiler_status, thermostat_status = process_statusfields_v4(fields)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyotgw/pyotgw.py", line 806, in process_statusfields_v4
v.DATA_SLAVE_MAX_CAPACITY: int(capmodlimits[0]),
~~~^^^^^^^^^^^^^^^^^
ValueError: invalid literal for int() with base 10: '0.00'
It seems it gets some default value from the gateway, which is not an int. Not sure if this should be an issue here or on the firmware of the OTGW.
Coming from this issue: rvdbreemen/OTGW-firmware#270. Basically, when I had my presoldered, preconfigured OTGW from nodo shop turned on without being connected to a boiler / thermostat (to make sure I could load it in HA before physically installing it), I got this error when loading it in Home Assistant with the OTGW integration:
It seems it gets some default value from the gateway, which is not an int. Not sure if this should be an issue here or on the firmware of the OTGW.