Closed tyron closed 1 week ago
I can confirm the problems with Studio Code Server Addon. The RAM usage of the Addon went above 15% (4GB on RPI4). After stopping the Addon it's running smooth again. I'm now using File Editor Addon.
I found this bug report in the VSCode add-on, and I'm in the process of fixing all my automations to the new syntax (based on this comment). I'll update here if that solves my issue
Initial testing tells me this was the problem indeed. The syntax check is very resource hungry, and the new syntaxes introduced in 2024.08 and expanded in 2024.10 seem to have caused the crash on RPi4. I'll file a bug report in the home-assistant/core repo, to raise attention and asking if there are plans on doing an automated migration of these things.
Describe the issue you are experiencing
Recently I started seeing many more crashes on my Home Assistant installation running on a Raspberry Pi 4. It wasn't an issue until recent months, so I'd say it got worse around 2024.08 release.
From a hunch, it seems to happen more when I'm interacting with Visual Studio add-on.
Additional details:
What operating system image do you use?
rpi4-64 (Raspberry Pi 4/400 64-bit OS)
What version of Home Assistant Operating System is installed?
13.2
Did the problem occur after upgrading the Operating System?
No
Hardware details
Raspberry Pi 4 2GB RAM 256Gb SSD Increase swap addon (to add 4GB SWAP to my SSD https://github.com/TazzerMAN/increase_swap_addon)
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1444 Downloaded Repositories | 18Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 13.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.10.2 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 219.4 GB disk_used | 120.9 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 | Home Assistant Google Drive Backup (0.112.1), Terminal & SSH (9.15.0), Studio Code Server (5.17.1), Duck DNS (1.18.0), NGINX Home Assistant SSL proxy (3.11.0), Node-RED (18.1.1), File editor (5.8.0), Z-Wave JS (0.8.0), Matter Server (6.6.0), Mosquitto broker (6.4.1), SQLite Web (4.2.2), eufy-security-ws (1.9.1), Scrypted (v0.118.0-jammy-full), Cloudflared (5.1.21), go2rtc (1.9.4), Increase Swap (1.1.3), Z-Wave.Me Add-on (v4.1.4), ESPHome (2024.9.2)Dashboards
dashboards | 8 -- | -- resources | 7 views | 19 mode | storageRecorder
oldest_recorder_run | September 18, 2024 at 1:22 PM -- | -- current_recorder_run | October 17, 2024 at 8:49 PM estimated_db_size | 642.70 MiB database_engine | sqlite database_version | 3.45.3Spotify
api_endpoint_reachable | ok -- | --Additional information
I left a
journalctl -f
session running while I interacted with my installation, and these were the last relevant logs captured before it hang (I had just requested Matter add-on to restart, and I switched to Visual Studio add-on to configure it):