Teltonika

The problem When adding the Teltonika integration, Home Assistant crashes during DHCP discovery with a ValidationError. Device: * Teltonika RUT950 The issue appears to be caused by older firmware/API responses missing the fields: * `device_model` * `device_identifier` Traceback: [code] The router response contains: [code] but does not include `device_model` or `device_identifier`. The issue happens during: [code] Manual setup may still work. ### What version of Home Assistant Core has the issue? 2026.5.0 ### What was the last working version of Home Assistant Core? 2026.5.0 ### What type of …

Excerpt saved from GitHub on 2026-10-23.

The problem After updating a Teltonika RUTC50 from RutOS RUTC_R_00.07.24.4 to R_00.07.24.5, the Teltonika integration no longer sets up. The config entry stays in setup_retry and all entities become unavailable (restored: true). The router itself is fine, its API responds normally. The response simply no longer contains a field that teltasync's pydantic model declares as required: DeviceStatusData requires static.release.target, but on this firmware static.release only carries version and distribution. Because this happens during get_device_status() in the coordinator's _async_setup, setup …

Excerpt saved from GitHub on 2026-10-23.

Same failure on a Teltonika RUTM11, a third model on this firmware line. - Device: RUTM11, RutOS R_00.07.24.5 (build 2026-09-14) - Home Assistant: core-2026.8.2, HAOS 18.2 (Raspberry Pi 5) - Config entry state: `setup_retry`, added manually, no entities ever created Identical single validation error, same call path (`coordinator._async_setup` → `get_system_info()` → `teltasync/system.py:226`): [code] Since it was noted above that the field selection differs between routers, here is the full, untruncated `data.static.release

Excerpt saved from GitHub on 2026-10-23.

The problem After updating a Teltonika RUTC50 from RutOS RUTC_R_00.07.24.4 to R_00.07.24.5, the Teltonika integration no longer sets up. The config entry stays in setup_retry and all entities become unavailable (restored: true). The router itself is fine, its API responds normally. The response simply no longer contains a field that teltasync's pydantic model declares as required: DeviceStatusData requires static.release.target, but on this firmware static.release only carries version and distribution. Because this happens during get_device_status() in the coordinator's _async_setup, setup …

Excerpt saved from GitHub on 2026-10-23.

The problem After updating a Teltonika RUTC50 from RutOS RUTC_R_00.07.24.4 to R_00.07.24.5, the Teltonika integration no longer sets up. The config entry stays in setup_retry and all entities become unavailable (restored: true). The router itself is fine, its API responds normally. The response simply no longer contains a field that teltasync's pydantic model declares as required: DeviceStatusData requires static.release.target, but on this firmware static.release only carries version and distribution. Because this happens during get_device_status() in the coordinator's _async_setup, setup …

Excerpt saved from GitHub on 2026-10-23.

Additional RUTX50 data point: I reproduced this today after updating the router. Device: Teltonika RUTX50 With RutOS R_00.07.24.5, Home Assistant failed during Teltonika setup with: [code] I then upgraded the router to R_00.07.25.2 and restarted Home Assistant. The integration still fails, but the validation error changes to: ``` pydantic_core._pydantic_core.ValidationError: 1 validation error for ApiResponse[DeviceStatusData] data.static.release Field required [type=missing, input_value={'kernel': '6.6.137', ... 'device_name': '

Excerpt saved from GitHub on 2026-10-23.