"Error adding entity text.<ZONE>_window_rest_timeout" on HA startup

[AlexHunterCodes]

The integration generates the below errors during Home Assistant's startup. I only started using Tado Local yesterday, so I don't know if this is new behaviour or not.

Component	Version
Home Assistant Core	2026.4.4
Tado Local integration	1.0.3 (latest)
TadoLocal server	1.1.2 (latest)

The window timeout entities on each Zone device appear as unavailable.

The More Info panel says they are "no longer being provided by the tado_local integration", but this is because they failed to initialise, not because they are actually deprecated. Right?

Error log

Logger: homeassistant.components.text
Source: helpers/entity_platform.py:680
integration: Text (documentation, issues)
First occurred: 18:40:17 (10 occurrences)
Last logged: 18:40:18

• Error adding entity text.kitchen_window_rest_timeout for domain text with platform tado_local
• Error adding entity text.bathroom_window_open_timeout for domain text with platform tado_local
• Error adding entity text.bathroom_window_rest_timeout for domain text with platform tado_local
• Error adding entity text.hallway_window_open_timeout for domain text with platform tado_local
• Error adding entity text.hallway_window_rest_timeout for domain text with platform tado_local

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 680, in _async_add_entities
    await self._async_add_entity(
        entity, False, entity_registry, config_subentry_id
    )
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 998, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1431, in add_to_platform_finish
    self.async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1050, in async_write_ha_state
    self._async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1199, in _async_write_ha_state
    ) = self.__async_calculate_state()
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1106, in __async_calculate_state
    state = self._stringify_state(available)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/text/__init__.py", line 157, in state
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Entity text.living_room_window_open_timeout provides state None which is too long (maximum length 3)

Logger: homeassistant
Source: components/text/init.py:157
First occurred: 18:40:48 (145 occurrences)
Last logged: 19:54:45

Error doing job: Task exception was never retrieved (task: None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 296, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 575, in _async_refresh
    self.async_update_listeners()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 202, in async_update_listeners
    update_callback()
    ~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 655, in _handle_coordinator_update
    self.async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1050, in async_write_ha_state
    self._async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1199, in _async_write_ha_state
    ) = self.__async_calculate_state()
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1106, in __async_calculate_state
    state = self._stringify_state(available)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/text/__init__.py", line 157, in state
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Entity text.living_room_window_open_timeout provides state None which is too long (maximum length 3)

[Bekkie]

It feels something is wrong on the server site.
Are you are able to see the TadoLocal Server UI via a regular web browser http://:4407 ?
And what does the http://:4407/zones return?

The TadoLocal Server UI is also reachable via the "Visit" link of the IB (Internet Bridge)

[AlexHunterCodes]

The server's zone API endpoint shows the window timeout values are both null, for all zones. I've included one zone below as an example, but they are all like that.

{
  "zone_id": 2,
  "name": "Bedroom",
  "uuid": "<redacted uuid>",
  "leader_device_id": 2,
  "leader_serial": "VA1234567890",
  "leader_type": "thermostat",
  "zone_type": "HEATING",
  "tado_zone_id": 2,
  "is_circuit_driver": false,
  "order_id": 1,
  "device_count": 1,
  "window_open_time": null,
  "window_rest_time": null,
  "state": {
    "cur_temp_c": 19.2,
    "cur_temp_f": 66.6,
    "hum_perc": 53,
    "target_temp_c": 17,
    "target_temp_f": 62.6,
    "mode": 1,
    "cur_heating": 0,
    "window_open": false
  },
  "home_id": 123456
}

Changing _attr_native_max = 3 in text.py to 4 for both window timeout entities at least lets them initialise as "None", even though they really should be "Unavailable" in HA terms (instead of leaking Python's language internals through).

Another workaround is manually calling the API to set those values to what their defaults should be on the server-side, then reload the integration.

POST /zones/{zone_id}/windowtimeouts Set Zone Window Timeouts
Set the open window timeout for a specific zone. Args: window_open_time: window open timeout in minutes (1-480, or -1 to reset to default: 30) window_rest_time: window rest timeout in minutes (1-480, or -1 to reset to default: 15)

I'm not sure if the "None" value is the integration converting JSON's null to Python's None, or if it's the initial value because the integration never sets native_value.

Why are these entities even Text anyway? They can only be ints so they should be Number platform sensors.

I have noticed while debugging that sometimes zones load with other data as null too, which the LocalTado web UI shows as mode = off, when it probably should be disconnected or unavailable. The zone does work in the official Tado app, so I'm guessing its just another bug. When that happens, the integration disables those entities.

So, error handling is all over the place, both in the integration and the server. Whether this is a server side issue or not, it's clear that neither are setting default values or validating inputs at all. This is not a graceful way to handle errors.

[Bekkie]

Thanks for your valuable feedback.

I found the issue — it originates in the TadoLocal Server part.
Creating the database from scratch did not set the default values (15 and 30), while upgrading from older versions did.

I’ve created pull request #53 in the AmpScm/TadoLocal repo and will merge it later today.

Changing the text fields to numeric fields is a good suggestion; I’ll create a separate pull request for that later this week.