Bonjour,
Depuis quelques temps (je ne sais pas exactement), j’ai HA qui freeze. La conséquence est un freeze au niveau de l’application (web, compagnion, …).
Par exemple le terminal est presque inexploitable, la frappe se fait lettre par lettre, la consultation des équipements est extrêmement longue.
Par exemple la génération du rapport ci-dessous a durée environ 1/2 minutes avec pas mal d’erreurs.
Si vous avez des idées, merci.
Quelques logs :
2025-02-02 20:28:55.909 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/45df7312_zigbee2mqtt/stats request
2025-02-02 20:28:56.170 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/45df7312_zigbee2mqtt/stats -
2025-02-02 20:29:43.966 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_matter_server/stats request
2025-02-02 20:29:43.966 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_matter_server/stats -
2025-02-02 20:29:57.572 ERROR (SyncWorker_12) [custom_components.fusion_solar.fusion_solar.kiosk.kiosk_api] Retrieving the data failed. Raw response: {"buildCode":"2","data":"neteco.pvms.systemSetting.notExists","failCode":0,"params":[],"success":false}
2025-02-02 20:30:03.629 ERROR (MainThread) [custom_components.fusion_solar.fusion_solar.energy_sensor] Attribute dailyEnergy not in coordinator data
2025-02-02 20:30:03.630 ERROR (MainThread) [custom_components.fusion_solar.fusion_solar.energy_sensor] Attribute monthEnergy not in coordinator data
2025-02-02 20:30:03.631 ERROR (MainThread) [custom_components.fusion_solar.fusion_solar.energy_sensor] Attribute yearEnergy not in coordinator data
2025-02-02 20:31:22.262 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated
2025-02-02 20:31:22.265 WARNING (MainThread) [homeassistant.components.go2rtc.server] Go2rtc server didn't terminate gracefully. Killing it
2025-02-02 20:31:22.265 WARNING (MainThread) [homeassistant.components.go2rtc.server] Go2rtc unexpectedly stopped, server log:
2025-02-02 20:31:22.266 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:49:37.365 INF go2rtc platform=linux/arm64 revision=dbe9e4a version=1.9.7
2025-02-02 20:31:22.266 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:49:37.365 INF config path=/tmp/go2rtc_izlr92d1.yaml
2025-02-02 20:31:22.266 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:49:37.366 INF [rtsp] listen addr=127.0.0.1:18554
2025-02-02 20:31:22.266 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:49:37.366 INF [api] listen addr=127.0.0.1:11984
2025-02-02 20:31:22.266 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:49:37.367 INF [webrtc] listen addr=:18555/tcp
2025-02-02 20:31:22.267 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated
2025-02-02 20:32:56.672 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.ahk_salon_pm25 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) took 0.465 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2025-02-02 20:34:52.661 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated
2025-02-02 20:34:53.487 WARNING (MainThread) [homeassistant.components.go2rtc.server] Go2rtc unexpectedly stopped, server log:
2025-02-02 20:34:53.488 WARNING (MainThread) [homeassistant.components.go2rtc.server] 20:31:26.073 INF go2rtc platform=linux/arm64 revision=dbe9e4a version=1.9.7
2025-02-02 20:34:53.490 WARNING (MainThread) [homeassistant.components.go2rtc.server] 20:31:26.104 INF config path=/tmp/go2rtc_6vc43vos.yaml
2025-02-02 20:34:53.491 WARNING (MainThread) [homeassistant.components.go2rtc.server] 20:31:26.106 INF [rtsp] listen addr=127.0.0.1:18554
2025-02-02 20:34:53.491 WARNING (MainThread) [homeassistant.components.go2rtc.server] 20:31:26.107 INF [webrtc] listen addr=:18555/tcp
2025-02-02 20:34:53.491 WARNING (MainThread) [homeassistant.components.go2rtc.server] 20:31:26.108 INF [api] listen addr=127.0.0.1:11984
2025-02-02 20:34:53.491 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated
2025-02-02 20:35:06.614 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for a0d7b954_zwavejs2mqtt: Timeout connecting to Supervisor
2025-02-02 20:35:06.729 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for 77c0fc0d_mqtt-explorer: Timeout connecting to Supervisor
2025-02-02 20:35:06.731 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for core_zwave_js: Timeout connecting to Supervisor
2025-02-02 20:35:06.737 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for a0d7b954_vscode: Timeout connecting to Supervisor
2025-02-02 20:35:06.738 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for 45df7312_zigbee2mqtt: Timeout connecting to Supervisor
2025-02-02 20:35:06.740 ERROR (MainThread) [homeassistant.components.co2signal.coordinator] Error fetching co2signal data: Timeout occurred while connecting to the Electricity Maps API
2025-02-02 20:35:06.741 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for a0d7b954_appdaemon: Timeout connecting to Supervisor
2025-02-02 20:35:07.299 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for core_matter_server: Timeout connecting to Supervisor
2025-02-02 20:35:07.300 WARNING (MainThread) [homeassistant.components.hassio.coordinator] Could not fetch changelog for core_ssh: Timeout connecting to Supervisor
Ma configuration
System Information
version |
core-2025.1.4 |
installation_type |
Home Assistant OS |
dev |
false |
hassio |
true |
docker |
true |
user |
root |
virtualenv |
false |
python_version |
3.13.1 |
os_name |
Linux |
os_version |
6.6.62-haos-raspi |
arch |
aarch64 |
timezone |
Europe/Paris |
config_dir |
/config |
Home Assistant Community Store
error |
failed to load: unknown |
Home Assistant Cloud
logged_in |
false |
can_reach_cert_server |
failed to load: timeout |
can_reach_cloud_auth |
failed to load: timeout |
can_reach_cloud |
failed to load: timeout |
Home Assistant Supervisor
host_os |
Home Assistant OS 14.2 |
update_channel |
stable |
supervisor_version |
supervisor-2024.12.3 |
agent_version |
1.6.0 |
docker_version |
27.2.0 |
disk_total |
116.7 GB |
disk_used |
49.2 GB |
healthy |
true |
supported |
true |
host_connectivity |
true |
supervisor_connectivity |
true |
ntp_synchronized |
true |
virtualization |
|
board |
rpi4-64 |
supervisor_api |
failed to load: timeout |
version_api |
failed to load: timeout |
installed_addons |
File editor (5.8.0), MariaDB (2.7.2), Node-RED (19.0.0), OneDrive Backup (2.3.8), Mosquitto broker (6.5.0), Ring-MQTT with Video Streaming (5.8.0), Z-Wave JS UI (3.19.0), MQTT Explorer (browser-1.0.1), Z-Wave JS (0.9.0), Studio Code Server (5.18.1), Zigbee2MQTT (1.40.2-1), AppDaemon (0.16.7), Matter Server (7.0.0), Terminal & SSH (9.16.0) |
Dashboards
error |
failed to load: timeout |
Recorder
error |
failed to load: timeout |
C’est quoi ta configuration matérielle ?
Raspberry avec Carte SD ?
Raspbert PI4 avec un NVMe. Je n’ai volontairement pas mis de MicroSD à cause de la durée de vie.
1 « J'aime »
Tu as combien de RAM dessus ?
Tu as regardé au niveau de la puissance d’alimentation ? (peut être essayer un autre chargeur).
hello,
disk_used | 49.2 GB
ce sont des save ou une db de l’enfer?
cdt
Voilà la config système complète :
## System Information
version | core-2025.1.4
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.13.1
os_name | Linux
os_version | 6.6.62-haos-raspi
arch | aarch64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 4999
Installed Version | 2.0.5
Stage | running
Available Repositories | 1511
Downloaded Repositories | 37
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 14.2
-- | --
update_channel | stable
supervisor_version | supervisor-2024.12.3
agent_version | 1.6.0
docker_version | 27.2.0
disk_total | 116.7 GB
disk_used | 49.2 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | rpi4-64
supervisor_api | ok
version_api | ok
installed_addons | File editor (5.8.0), MariaDB (2.7.2), Node-RED (19.0.0), OneDrive Backup (2.3.8), Mosquitto broker (6.5.0), Ring-MQTT with Video Streaming (5.8.0), Z-Wave JS UI (3.19.0), MQTT Explorer (browser-1.0.1), Z-Wave JS (0.9.0), Studio Code Server (5.18.1), Zigbee2MQTT (1.40.2-1), AppDaemon (0.16.7), Matter Server (7.0.0), Terminal & SSH (9.16.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 5
-- | --
resources | 26
views | 19
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 22 janvier 2025 à 04:45
-- | --
current_recorder_run | 2 février 2025 à 21:04
estimated_db_size | 6350.10 MiB
database_engine | sqlite
database_version | 3.47.1
</details>
Je viens de le redémarrer et tout va bien pendant quelques dizaines de minutes, ensuite ça recommence.
J’ai 2 Go de RAM, 1Go utilisé actuellement
@freetronic ça doit être un db de l’enfer, mes backups sont envoyés sur onedrive mais j’ai 27 Go en local. Il reste donc 22 Go pour la db environ. Comment je peux voir ça ?
il y a cette ligne
estimated_db_size | 6350.10 MiB
Tu as beaucoup d’intégrations / appareils ?
Je regarde la mienne je suis à 628MiB
Effectivement c’est bizare, j’ai 27 intégrations, 188 appareils, rien de particulier je pense.
Les backups en fait c’est les backups d’avant mise à jour des intégrations. Le reste est bien sur onedrive (full tous les jours)
Re,
il faudrait aussi jeter un oeil sur la charge en ram (voir cpu) apès si on est limite ça va pas arranger les choses, mais faut déjà pas mal de choses pour taper 2Go
je tape entre 2 et 3Go de mon côté mais c’est déjà bien chargé
cdt
Je vais regarder ce point aussi effectivement, il y a peut être un effet de seuil avec de nouveaux appareils.
Là je suis à 65% d’utilisés sur la RAM et 26% CPU en moyenne.