Hi all,
I’ve been running my HomeAssistant instance whit no issue for the last year. Last week I changed my home router/modem from KPN to a Ubiquiti Cloud gateway Ultra. Some things changed like the gateway IP and some IP’s from hubs i wanted to change to a different static IP. I’ve set all this up in the Ultra and in the HA add-ons / Network settings but for some reason the HomeAssistant keeps rebooting between the 5 to 10 minutes +/- When i check the logs i dont realy see a critical error which could cause the HA to crash
HA setup:
- Core - 2025.1.4
- Supervisor - 2024.12.3
- Operating System - 14.2
- Frontend - 20250109
- Raspberry Pi 4 8GB with NVME storage (500GB) no SD card (Argon ONE V2 M.2 Expansion Board (NVME))
Logs:
- home-assistant.log.fault > Empty ? 0KB
- Home-assistant.log.1 > 34 entries only warnings.
- Home-assistant.log > 104 enties mostly warning and few error’s from a old automation thats allready deleted but i dont know why its showing? (Sensor.droger was a amp/watt checker to see if the washing machine was done but i deleted this like 3 months ago)
I’m kinda out of options where to go looking / what is causing it… When home assistant is back online is shows all data like nothing happend, all dashboards work and integrations etc… Where should i start beside the logs?
2025-01-27 17:41:30.990 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:30.995 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration plant which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:30.997 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration eufy_security which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.000 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.002 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration buienalarm which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.004 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bambu_lab which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.006 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration quatt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.009 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration openplantbook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.012 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xtend_tuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:31.013 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-27 17:41:36.557 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-01-27 17:41:36.620 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=361 from 2025-01-27 16:36:26.376221)
2025-01-27 17:41:56.405 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.415 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.424 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.434 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.480 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.489 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.540 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_CLEANING was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.CLEANING instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.549 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_DOCKED was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.DOCKED instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.558 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_RETURNING was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.RETURNING instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.567 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_CLEANING was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.CLEANING instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.576 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_DOCKED was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.DOCKED instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:56.585 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_RETURNING was used from xtend_tuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.RETURNING instead, please report it to the author of the 'xtend_tuya' custom integration
2025-01-27 17:41:57.568 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.heatpump_flowmeter_flowrate (<class 'custom_components.quatt.sensor.QuattSensor'>) is using native unit of measurement 'L/h' which is not a valid unit for the device class ('volume_flow_rate') it is using; expected one of ['m³/h', 'gal/min', 'ft³/min', 'mL/s', 'L/min']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/marcoboers/home-assistant-quatt/issues
2025-01-27 17:41:59.750 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for higrow04 @ xxx.xxx.x.86: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='xxx.xxx.x.86', port=6053))]: [Errno 111] Connect call failed ('xxx.xxx.x.86', 6053) (SocketAPIError)
2025-01-27 17:42:02.809 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for higrow01 @ xxx.xxx.x.28: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='xxx.xxx.x.28', port=6053))]: [Errno 113] Connect call failed ('xxx.xxx.x.28', 6053) (SocketAPIError)
2025-01-27 17:42:02.811 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for higrow02 @ xxx.xxx.x.83: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='xxx.xxx.x.83', port=6053))]: [Errno 113] Connect call failed ('xxx.xxx.x.83', 6053) (SocketAPIError)
2025-01-27 17:42:02.876 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for higrow03 @ xxx.xxx.x.41: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='xxx.xxx.x.41', port=6053))]: [Errno 113] Connect call failed ('xxx.xxx.x.41', 6053) (SocketAPIError)
2025-01-27 17:42:02.904 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for 3d-cam @ xxx.xxx.x.42: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='xxx.xxx.x.42', port=6053))]: [Errno 113] Connect call failed ('xxx.xxx.x.42', 6053) (SocketAPIError)
2025-01-27 17:42:27.948 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: conversation, solaredge, buienradar.sensor, philips_js, homewizard.button, philips_js.remote, buienalarm.sensor, history, utility_meter, mqtt.binary_sensor, philips_js.light, system_log, esphome, eufy_security.number, automation, assist_pipeline, bambu_lab, bambu_lab.fan, plant.number, solaredge.sensor, xtend_tuya.vacuum, system_health, network, homeassistant_sky_connect, esphome.button, lock, schedule, eufy_security.button, assist_satellite, analytics, homeassistant, integration.sensor, eufy_security.image, tado, xtend_tuya.select, bambu_lab.light, tradfri.fan, tradfri.sensor, bambu_lab.sensor, file_upload, xtend_tuya, local_todo, wiz.number, trace, switch, picnic, cloud.tts, xtend_tuya.alarm_control_panel, eufy_security.switch, plant, zone, mobile_app.notify, energy.sensor, stt, cover, time, rpi_power, hue.sensor, mqtt, wiz.switch, xtend_tuya.camera, template, hacs.update, tradfri.light, device_automation, bambu_lab.switch, speedtestdotnet, hue, xtend_tuya.sensor, hacs.switch, esphome.climate, hassio, media_player, event, xtend_tuya.cover, quatt.sensor, bluetooth, buienradar.camera, homeassistant_alerts, bambu_lab.number, hue.scene, config, backup, wiz, tts, wiz.light, openplantbook, logbook, input_button, raspberry_pi, rpi_power.binary_sensor, image_upload, device_tracker, my, number, systemmonitor, systemmonitor.sensor, counter, homeassistant.scene, frontend, androidtv_remote, hue.switch, remote, tradfri.cover, xtend_tuya.light, person, philips_js.switch, cloud.stt, eufy_security.select, shopping_list, recorder, api, sensor, homewizard.number, auth, eufy_security.camera, hardware, cast.media_player, google_translate, application_credentials, group.light, tag, button, met.weather, blueprint, weather, openai_conversation, google_translate.tts, esphome.update, sun, xtend_tuya.button, buienradar, xtend_tuya.number, xtend_tuya.binary_sensor, logger, water_heater, camera, onboarding, xtend_tuya.switch, fontawesome, philips_js.media_player, hue.event, input_select, update, mqtt.switch, xtend_tuya.scene, group.notify, default_config, eufy_security.binary_sensor, persistent_notification, lovelace, intent, sun.sensor, webrtc, xtend_tuya.fan, co2signal.sensor, input_text, homewizard, vacuum, openai_conversation.conversation, scene, esphome.light, tado.device_tracker, quatt.binary_sensor, bambu_lab.select, bambu_lab.camera, plant.sensor, hassio.update, esphome.sensor, zeroconf, tado.climate, picnic.sensor, mobile_app.device_tracker, diagnostics, ffmpeg, hassio.sensor, speedtestdotnet.sensor, buienradar.weather, repairs, integration, forecast_solar.sensor, forecast_solar, input_datetime, met, alarm_control_panel, xtend_tuya.lock, eufy_security.alarm_control_panel, humidifier, select, fan, ssdp, ipp, homewizard.sensor, wyoming, shopping_list.todo, androidtv_remote.media_player, bambu_lab.binary_sensor, script, energy, image, stream, template.binary_sensor, co2signal, tado.binary_sensor, todo, google_assistant, quatt, picnic.todo, webhook, wiz.binary_sensor, xtend_tuya.time, ipp.sensor, mobile_app, eufy_security.sensor, mobile_app.binary_sensor, binary_sensor, systemmonitor.binary_sensor, light, xtend_tuya.climate, template.sensor, websocket_api, mqtt.button, radio_browser, wiz.sensor, http, cast, xtend_tuya.siren, local_todo.todo, hue.light, homeassistant_hardware, esphome.switch, siren, tado.sensor, search, bambu_lab.image, utility_meter.sensor, mobile_app.sensor, androidtv_remote.remote, timer, hassio.binary_sensor, dhcp, eufy_security.lock, cloud.binary_sensor, input_boolean, esphome.camera, go2rtc, bambu_lab.button, tradfri.switch, xtend_tuya.humidifier, philips_js.binary_sensor, tado.water_heater, eufy_security, mqtt.sensor, usb, tradfri, notify, climate, cloud, homewizard.switch, hacs, media_source, input_number, hue.binary_sensor, group, wake_word The system is waiting for tasks: {<Task pending name='Task-901' coro=<AbstractConfig.async_initialize.<locals>.sync_google() running at /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2025-01-27 17:44:38.021 ERROR (Thread-113) [pychromecast.socket_client] [Kantoor(xxx.xxx.x.59):8009] Failed to connect to service MDNSServiceInfo(name='Chromecast-0859ad1405c81baa5c58e4b657c49d5c._googlecast._tcp.local.'), retrying in 5.0s
2025-01-27 17:47:33.717 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({% set wasmachine = states('sensor.washmachine_stroom') | float > 0.01 %}
{% set droger = states('sensor.droger_stroom') | float > 0.01 %}
{% if wasmachine and droger %}
Was zowel droger actief
{% elif wasmachine %}
Wasmachine actief
{% elif droger %}
Droger actief
{% else %}
Geen was of droger actief.
{% endif %}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in forgiving_float_filter
return float(value)
ValueError: could not convert string to float: 'unknown'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 643, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2745, in _render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "<template>", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2367, in forgiving_float_filter
raise_no_default("float", value)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1921, in raise_no_default
raise ValueError(
...<2 lines>...
)
ValueError: Template error: float got invalid input 'unknown' when rendering template '{% set wasmachine = states('sensor.washmachine_stroom') | float > 0.01 %}
{% set droger = states('sensor.droger_stroom') | float > 0.01 %}
{% if wasmachine and droger %}
Was zowel droger actief
{% elif wasmachine %}
Wasmachine actief
{% elif droger %}
Droger actief
{% else %}
Geen was of droger actief.
{% endif %}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 760, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% set wasmachine = states('sensor.washmachine_stroom') | float > 0.01 %}
{% set droger = states('sensor.droger_stroom') | float > 0.01 %}
{% if wasmachine and droger %}
Was zowel droger actief
{% elif wasmachine %}
Wasmachine actief
{% elif droger %}
Droger actief
{% else %}
Geen was of droger actief.
{% endif %}' but no default was specified