Bonjour.
j ai besoin d aide.
mon ha plante regulierement (presque tous les jours.)
Je suis obligé de debrnacher rebrancher le rpi.
Comment savoir l origine du plantage ? le fichier de log n indique pas grand chose.
Ma config : rpi5 avec shield x1001 et ssd nmve.
Je vous sur certain site qu il faut actiber le port pci5 pour pouvoir botter sur le ssd, moi je n ai rien fait, juste mettre haos dessus depuisbmon oc, branché le ssd sur le rpi, et ha s est lancé directement.
Voilà.
Salut. Tu peux en dire plus sur ton installe ? Tu tourne avec des composants ZigBee, une clef zigbee, beaucoup d’appareils, des intégrations ?
Et quand tu dit plantage c’est à dire, ça se fige ou ça répond plus ? C’est quoi qui plant exactement ?
alors, j ai une cle zigbee avec 2 boutons integres dessus.
Une cle zwave avec 4 periph dessus.
Quelques donnees qui remontent en mqtt. 3 sondes xiaomi en ble.
Pas de trucs fou.
Avant sous jeedom, pas un seul plantage.
je voulais essayer ha, mais franchement je me tate a revenir sous jeedom si je ne peux pas compter dessus.
Plantage : interface qui n est plus accessible.
au redemarrage pas de massage d erreur, dans les logs je ne vois rien de special. ca me dit juste qu il n est pas certain que ma base de donnees ai ete fermée correctement.
Salut
Peux-tu partager les infos de ton installation en suivant le template de message du forum qui est là pour ça
il faut regarder le fichier log.1 (celui d’avant le redémarrage), sinon tu ne verras rien
Si ça boote, c’est suffisant et c’est probablement sans rapport avec un plantage.
Par ailleurs, tu parles de stabilité jeedom/ha… Avais-tu le même pi sous jeedom ? Avec une debian 12 ?
Voici la configuration : (HA a planté deux fois aujourd’hui, l’interface n’affiche plus rien; elle était ouverte sous mon windows) Et depuis mon smartphone l’ip n’est plus joignable.
| version | core-2024.3.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.12.2 |
| os_name | Linux |
| os_version | 6.1.73-haos-raspi |
| arch | aarch64 |
| timezone | Europe/Paris |
| config_dir | /config |
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.34.0 |
| Stage | running |
| Available Repositories | 1403 |
| Downloaded Repositories | 9 |
| HACS Data | ok |
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
| host_os | Home Assistant OS 12.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2024.03.1 |
| agent_version | 1.6.0 |
| docker_version | 24.0.7 |
| disk_total | 219.3 GB |
| disk_used | 9.9 GB |
| healthy | true |
| supported | true |
| board | rpi5-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Terminal & SSH (9.10.0), Studio Code Server (5.15.0), Mosquitto broker (6.4.0), Zigbee2MQTT (1.36.0-1), Z-Wave JS (0.4.5), Network UPS Tools (0.13.0), Node-RED (17.0.10) |
| dashboards | 2 |
|---|---|
| resources | 1 |
| views | 3 |
| mode | storage |
| oldest_recorder_run | March 28, 2024 at 5:23 AM |
|---|---|
| current_recorder_run | April 3, 2024 at 8:19 PM |
| estimated_db_size | 1452.77 MiB |
| database_engine | sqlite |
| database_version | 3.44.2 |
Le RPI5 est neuf le ssd aussi.
Jeedom tourne toujours sur l’ancien pi4
et voici le contenu de ha.log1
2024-04-03 11:35:30.967 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration multiscrape 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
2024-04-03 11:35:30.968 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration ble_monitor 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
2024-04-03 11:35:30.969 WARNING (SyncWorker_5) [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
2024-04-03 11:35:30.969 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration nodered 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
2024-04-03 11:35:30.970 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration meross_lan 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
2024-04-03 11:35:30.970 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration apsystems_ecur 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
2024-04-03 11:35:30.971 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration meross_cloud 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
2024-04-03 11:35:30.971 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration rtetempo 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
2024-04-03 11:35:32.062 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-04-03 11:35:32.073 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=45 from 2024-04-02 18:39:20.848906)
2024-04-03 11:35:37.362 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-03 11:35:37.364 WARNING (zeroconf-ServiceBrowser-_googlecast._tcp-114) [pychromecast.dial] Failed to determine cast type for host <unknown> (HTTP Error 403: Forbidden) (services:{MDNSServiceInfo(name='MIBOX3-92067379e11b727f13642e96dda1e341._googlecast._tcp.local.')})
2024-04-03 11:35:37.644 ERROR (Thread-8) [pychromecast.socket_client] [MIBOX3(92067379-e11b-727f-1364-2e96dda1e341.local.):8009] Failed to connect to service MDNSServiceInfo(name='MIBOX3-92067379e11b727f13642e96dda1e341._googlecast._tcp.local.'), retrying in 5.0s
2024-04-03 11:35:38.102 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-251C/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-251C', 'state_topic': 'homeassistant/sensor/PvRouter-251C/state', 'availability_topic': 'homeassistant/sensor/PvRouter-251C/status', 'unique_id': '251C-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-251C/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-251C', 'name': 'PvRouter-251C', 'sw_version': 'PvRouter Version 20240306', 'model': 'ESP32 TTGO 192.168.1.124', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.124'}, 'platform': 'mqtt'}'
2024-04-03 11:35:38.103 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-CDC4/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-CDC4', 'state_topic': 'homeassistant/sensor/PvRouter-CDC4/state', 'availability_topic': 'homeassistant/sensor/PvRouter-CDC4/status', 'unique_id': 'CDC4-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-CDC4/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-CDC4', 'name': 'PvRouter-CDC4', 'sw_version': 'PvRouter Version 20240306', 'model': 'ESP32 TTGO 192.168.1.49', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.49'}, 'platform': 'mqtt'}'
2024-04-03 11:35:38.104 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-C88C/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-C88C', 'state_topic': 'homeassistant/sensor/PvRouter-C88C/state', 'availability_topic': 'homeassistant/sensor/PvRouter-C88C/status', 'unique_id': 'C88C-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-C88C/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-C88C', 'name': 'PvRouter-C88C', 'sw_version': 'PvRouter Version 20240316', 'model': 'ESP32 TTGO 192.168.1.116', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.116'}, 'platform': 'mqtt'}'
2024-04-03 11:35:39.261 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'value_json' is undefined when rendering '{{ value_json.power }}'
2024-04-03 11:36:04.886 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f78127240>>(<Event homeassistant_start[L]>)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state
numerical_value = float(value) # type:ignore[arg-type]
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/core.py", line 1196, in __call__
self.hass.async_run_job(self.listener, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 775, in async_run_job
return self.async_run_hass_job(HassJob(target), *args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 40, in _matched_event
hass.async_run_hass_job(at_start_job, hass)
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 486, in _async_template_startup
result_info.async_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1076, in async_refresh
self._refresh(None)
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1262, in _refresh
self.hass.async_run_hass_job(self._job, event, updates)
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 434, in _handle_results
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1113, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1050, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state
raise ValueError(
ValueError: Sensor sensor.prod_onduleur_piko_mp has device class 'energy', state class 'total_increasing' unit 'Wh' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>)
2024-04-03 11:38:56.001 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'value_json' is undefined when rendering '{{ value_json.Routed }}'
2024-04-03 11:55:33.134 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 11:55:35.712 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=6>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 11:56:17.724 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=10>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 11:56:20.294 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=14>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 12:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 12:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 13:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 13:00:00.334 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 14:00:00.332 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 14:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 14:14:11.903 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=18>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 14:24:10.601 WARNING (Thread-11) [pychromecast.socket_client] [SHIELD(192.168.1.195):8009] Heartbeat timeout, resetting connection
2024-04-03 14:24:40.632 ERROR (Thread-11) [pychromecast.socket_client] [SHIELD(192.168.1.195):8009] Failed to connect to service HostServiceInfo(host='192.168.1.195', port=8009), retrying in 5.0s
2024-04-03 15:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 15:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 15:27:15.585 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=22>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 15:47:34.845 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.shellyem_a4e57cbacf57_channel_2_energy_returned (<class 'homeassistant.components.shelly.sensor.BlockSensor'>) took 0.543 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+shelly%22
2024-04-03 16:00:00.332 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 16:00:00.332 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 16:58:45.134 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}) renders=26>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2037, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 573, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2364, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, 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 2040, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1668, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' 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 699, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{(states('sensor.kostal_ac_power')|float)+(states('sensor.ecu_current_power')|float)}}' but no default was specified
2024-04-03 17:00:00.333 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
2024-04-03 17:00:00.334 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'numeric_state':
In 'numeric_state' condition: unknown entity sensor.ma_piscine_mon_spa_oxydo_reduction_potential
et le .log
2024-04-03 20:19:17.988 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration multiscrape 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
2024-04-03 20:19:17.990 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration ble_monitor 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
2024-04-03 20:19:17.990 WARNING (SyncWorker_4) [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
2024-04-03 20:19:17.991 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration nodered 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
2024-04-03 20:19:17.991 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration meross_lan 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
2024-04-03 20:19:17.992 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration apsystems_ecur 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
2024-04-03 20:19:17.993 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration meross_cloud 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
2024-04-03 20:19:17.993 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration rtetempo 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
2024-04-03 20:19:19.085 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-04-03 20:19:19.107 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=46 from 2024-04-03 09:35:32.055908)
2024-04-03 20:19:24.363 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-03 20:19:25.646 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-251C/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-251C', 'state_topic': 'homeassistant/sensor/PvRouter-251C/state', 'availability_topic': 'homeassistant/sensor/PvRouter-251C/status', 'unique_id': '251C-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-251C/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-251C', 'name': 'PvRouter-251C', 'sw_version': 'PvRouter Version 20240306', 'model': 'ESP32 TTGO 192.168.1.124', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.124'}, 'platform': 'mqtt'}'
2024-04-03 20:19:25.651 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-CDC4/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-CDC4', 'state_topic': 'homeassistant/sensor/PvRouter-CDC4/state', 'availability_topic': 'homeassistant/sensor/PvRouter-CDC4/status', 'unique_id': 'CDC4-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-CDC4/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-CDC4', 'name': 'PvRouter-CDC4', 'sw_version': 'PvRouter Version 20240306', 'model': 'ESP32 TTGO 192.168.1.49', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.49'}, 'platform': 'mqtt'}'
2024-04-03 20:19:25.652 ERROR (MainThread) [homeassistant.components.mqtt.mixins] Error 'expected SensorDeviceClass or one of 'date', 'enum', 'timestamp', 'apparent_power', 'aqi', 'atmospheric_pressure', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'data_rate', 'data_size', 'distance', 'duration', 'energy', 'energy_storage', 'frequency', 'gas', 'humidity', 'illuminance', 'irradiance', 'moisture', 'monetary', 'nitrogen_dioxide', 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'ph', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'precipitation', 'precipitation_intensity', 'pressure', 'reactive_power', 'signal_strength', 'sound_pressure', 'speed', 'sulphur_dioxide', 'temperature', 'volatile_organic_compounds', 'volatile_organic_compounds_parts', 'voltage', 'volume', 'volume_storage', 'volume_flow_rate', 'water', 'weight', 'wind_speed' for dictionary value @ data['device_class']' when processing MQTT discovery message topic: 'homeassistant/sensor/PvRouter-C88C/config', message: '{'device_class': '', 'unit_of_measurement': '', 'state_class': '', 'name': '-C88C', 'state_topic': 'homeassistant/sensor/PvRouter-C88C/state', 'availability_topic': 'homeassistant/sensor/PvRouter-C88C/status', 'unique_id': 'C88C-', 'value_template': '{{ value_json. }}', 'command_topic': 'homeassistant/sensor/PvRouter-C88C/command', 'command_template': '{{ value_json. }}', 'expire_after': '60', 'device': {'identifiers': 'PvRouter-C88C', 'name': 'PvRouter-C88C', 'sw_version': 'PvRouter Version 20240316', 'model': 'ESP32 TTGO 192.168.1.116', 'manufacturer': 'Cyril Poissonnier', 'configuration_url': 'http://192.168.1.116'}, 'platform': 'mqtt'}'
2024-04-03 20:19:25.694 WARNING (zeroconf-ServiceBrowser-_googlecast._tcp-114) [pychromecast.dial] Failed to determine cast type for host <unknown> (HTTP Error 403: Forbidden) (services:{MDNSServiceInfo(name='MIBOX3-92067379e11b727f13642e96dda1e341._googlecast._tcp.local.')})
2024-04-03 20:19:25.727 ERROR (Thread-10) [pychromecast.socket_client] [MIBOX3(92067379-e11b-727f-1364-2e96dda1e341.local.):8009] Failed to connect to service MDNSServiceInfo(name='MIBOX3-92067379e11b727f13642e96dda1e341._googlecast._tcp.local.'), retrying in 5.0s
2024-04-03 20:19:26.761 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'value_json' is undefined when rendering '{{ value_json.power }}'
2024-04-03 20:19:52.164 WARNING (MainThread) [custom_components.meross_lan.profile_@0] MerossMQTTConnection(###################2:@1): Exception(Unable to identify abilities) in async_try_discovery (uuid:###############################1)
2024-04-03 20:19:52.680 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f6b576e80>>(<Event homeassistant_start[L]>)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state
numerical_value = float(value) # type:ignore[arg-type]
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/core.py", line 1196, in __call__
self.hass.async_run_job(self.listener, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 775, in async_run_job
return self.async_run_hass_job(HassJob(target), *args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 40, in _matched_event
hass.async_run_hass_job(at_start_job, hass)
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 486, in _async_template_startup
result_info.async_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1076, in async_refresh
self._refresh(None)
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1262, in _refresh
self.hass.async_run_hass_job(self._job, event, updates)
File "/usr/src/homeassistant/homeassistant/core.py", line 727, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 434, in _handle_results
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1113, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1050, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state
raise ValueError(
ValueError: Sensor sensor.prod_onduleur_piko_mp has device class 'energy', state class 'total_increasing' unit 'Wh' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>)
Mais bon, là c’est plus possible de continuer comme cela avec HA, je ne peux absolument pas compter dessus !!!
Tu as déjà un souci de base corrompue. Le plus facile, l’effacer et repartir de 0
Et un souci de communication avec l’onduleur ? Du coup n’a-t-il pas des microcoupures ? Quel age et les batteries datent de quand ?
Des templates pas correctement ecrits (il manque les valeurs par défaut)
Et des erreurs dans les automatisations.
ça fait beaucoup d’un coup
A priori ça semble plus un souci de config que de matos mais pas certain que jeedom fasse aussi bien avec un pi5 ultra récent
Pour les erreurs dans l’automation : oui, ondilo a changé l’api. Pour l’instant on ne peut plus lire les valeurs.
Pour le template, comment changer les valeurs par defaut ?
Pour la base de données : que faire ? Car cela indique juste qu’elle n’a pas été fermée correctement. Mais c’'est certain puisque ça plante !!! et que HA est en rade.
Pour l’onduleur, la nuit, le fichier renvoyé n’est pas le même que quand il y a production, du coup la nuit plein d’erreurs. Mais même en coupant cela dans HA, j’ai tjs un plantage …
desactive le tout en attendant, ça va pourrir les logs et rendre le truc plus compliqué pour l’instant
ça donne :
'{{(states('sensor.kostal_ac_power')|float(default=0))+(states('sensor.ecu_current_power')|float(default=0))}}'
Oui mais une base pourrie, ça aide aussi à faire planter HA quand il souhaite écrire dedans… C’est le cercle infernal, d’ou l’idée de la supprimer et de relancer HA pour partir propre
Pas simple
Bon alors commençons simple : comment supprimer la BD et repartir sur quelque chose de propre ?
On est d’accord que la BD va juste effacer l’historique des données et pas les automations, helpers, devices … ?
Tu effaces le fichier (avec vstudio par exemple) et tu redemarres (la recréation est automatique)
Et oui, ça ne fait disparaitre que les données, pas la config
Par défaut c’est masqué …
Tu peux temporairement l’afficher en virant le filtre pour les *.db dans Vstudio
ok, entre tmps j’ai installé file editor. J’ai renommer le fichier, et j’ai redemarré ha.
On verra …
Hello
La version HAOS que tu as installé est bien celle dédiée RPI5 et non celle pour RPI4 ?
oui. c est bien la version pour rpi5
Bonjour @David_Marlinge,
Ceci n’engage que moi mais vu le nombre de tes messages depuis début mars, j’ai comme l’impression que tu cumules un peu dans tous les sens !!!
« Mais bon, là c’est plus possible de continuer comme cela avec HA, je ne peux absolument pas compter dessus !!! »
Là je suis très surpris car je trouve HA très puissant et très stable.
Peut-être n’as tu pas commencé par assez de lecture 
Il me semble que tu as peu d’éléments sur ton HA pour l’instant mais je me confonds peut être avec une autre présentation.
estimated_db_size 1452.77 MiB
Tu as des très bons spécialistes qui te répondent, mais juste quand même :
Déjà la taille de la base me parait énorme, as-tu paramétré le recorder?
Fais-tu les choses les unes après les autres avec une sauvegarde de ce qui fonctionne après avoir regardé les journaux pour vérifier que tu ne vas pas cumuler les problèmes ?
Bob
Hello
Est ce que ton pi est toujours pingable lorsque HA est planté ? Peux tu toujours te connecter en SSH dessus (install l’add-on ssh since n’est pas le cas)
C’est intéressant de savoir si c’est l’os du rpi qui est planté ou juste HA
Bonjour,
écoute, j’ai bien essayé de lire au début, mais quand tu changes complétement la philosophie entre jeedom et HA, ce n’est pas facile de la faire en abstraction totale.
Donc à un moment il a bien fallu que je passe à HA.
Franchement j’avais pas grand chose à mettre :
Je voulais remettre l’automatisation de ma psicine et du chauffeau !!!
La base de données, non je n’ai pas paramétré le recorder. D’ailleurs après 1 mois de galère, c’est la première fois hier , que j’en ai entendu parler …
Quand j’ai installé HA, il m’a trouvé mon NAS synology. Sur ce NAS j’ai deux caméras qui enregistrent le flux. Est-ce cela qui peut faire grimper la BD ?
Ensuite j’ai un module branché sur le linky qui envoie des données toutes les 5s, donc là aussi ça doit participer.
Maintenant avec l’effacement de l’ancienne BD, et mise en place d’une nouvelle, je n’ai plus eu de plantage depuis le dernier démarrage hier à 21h00.
Là je suis très surpris car je trouve HA très puissant et très stable.
ben oui, c’est bien pour cela que je veux tester HA. Je lis partout que c’est super …
Avoue que c’est pas plug and play, et après un mois dessus, je commence à peine à comprendre la philosophie du truc.
Je ne dois pas être le seul !
Pour le recorder, la doc est peut-être bien faite, mais en l’état inutilisable pour moi !
Par exemple je ne vois pas, un exemple tout con : on efface les données (toutes au bout d’un mois)
non, dans la doc on a l’impression qu’on doit paramétrer chaque composant …
Franchement à part pour energy, je me fous des données de plus d’un mois.
Maintenant, j’adore l’interface, bien plus contemporaine que jeedom.
Ca à l’air super puissant, mais je me répète, en débutant on est complétement perdu …
Tiens autre exemple : HA m’e##erde: dès que j’allume ma shield, elle est détectée et provoque des erreurs dans le log. J’ai beau le mettre en disable, ça revient au prochain allumage de la shield… Je ne comprends pas. Surement un réglage à la noix, perdu quelque part
En tout cas merci à vous de prendre le temps de m’aider.
PS : depuis la mise en place de la nouvelle BD, celle-ci après 18h de fonctionnement fait 90Mb !
Logiquement photos / vidéos ne sont pas stockées en base.
Je n’ai pas de Linky, mais je pense que tu peux mettre un interval pour ne pas rapatrier trop de données.
Bob
C’est bien de se jeter dans le bain, mais perso je ne suis pas certain que jouer avec HA ce soit une bonne idée sans avoir lu la doc.
Et à minima d’y voir les concepts… On est pas obligé de tout savoir/lire/comprendre du premier coup mais au moins les choses qui sont utiles pour les besoins immédiats.
Et puis Jeedom c’est pareil, sachant qu’en plus la doc est pas toujours aussi propre/à jour que celle de HA…
Je t’invite par exemple à relire la doc… Le 1er principe est simple … On vire tout dans la base après X jours… ET on garde tout ce dont on a besoin (en faisant une liste) dans les statistiques à longs terme…
Et il y a plein mais alors plein de sujets et d’exemples sur le forum