Home Assistant OS 10: Better memory management and new board support

I just did an esphome build to try


and it comes no where near memory limits, so I’m still leaning towards CPU limits. (this is HOAS10.1)

the problem with a full crash is that the log only writes back the file every 5 minutes, so you can never be certain what happened just before the crash.

I’m also using the official Yellow Power Supply, So I assume that one is powerfull enough.

I updated to HAOS10 a few days ago, didn’t notice any problems.
After I tried the upgrade this morning I also see very high CPU usage after the update, everything is still running without problems, and it’s only after reading these threads I started to investigate.

I’m running on a Proxmox VM in an Intel NUC (i5 based) with 2 CPU’s for the VM and 8 GB ram…
I have a lot of addons.
Adguard Home, Advanced SSH & Webtermial, AppDaemon, Chrony, ESPHome, Grafana, HA Google Drive backup, InfluxDB, Let’s encrypt, MariaDB, Mosquitto, Node-RED, Samba share, Studio Code Server, Waultwarden, Zigbee2MQTT.
I only use BT through proxies, and don’t have nginx or motineye installed.

I was wondering if it is rebuilding / cleaning up the DB, and maybe the CPU usage is only temporary?
After 15 minuttes or so, the CPU usage seems to be back to normal.

Memory usage is just high, plain and simple:

tried to update my RPI4 today and now everything is broken. OS itself is booting, but it seems the supervisor is not. The ha console command also fails (it just doesn’t do or print anything). So all I currently can do is to login via SSH and that’s it :frowning: No idea how to fix this.

edit:
my setup:

  • RPI4 running HAOS 9.5 (at least until I tried to update)
  • data partition moved to external SSD (connected via USB3, located in a 4-bay HDD USB case)
  • 3 additional HDDs for media (connected via USB3, located in a 4-bay HDD USB case)

There aren’t any new database migrations in 2023.5.x

There are more auto repairs that can detect incorrect schema and repair it so maybe that’s it. It would have logged something.

I just updated to 10.1 and RAM stayed at around 1G. In other words mem usage seems fixed.

I didn’t see anything in the logs, well it’s not a reproducable problem at least, so it could be a lot of stuff irrelevant to HA.
With the 10.1 I did see the RAM usage drop.

For anyone who is interested, i’;ve just sucessfully migrate my HA install *(running on a ‘hooby’ linux VM on my unraid server’ on to the Odroid M1 and have been very impressed!

Usng the instructions in the blog. I upgraded the firmware, installed a nvme drive (Samsung 980 512gb - overkill but was on my shelf spare) and have been able to migrate my Home Assistant install over to the Odroid, using the Google Backup add to move my most recent backup over. It too a long time on the insital boot, and and then 30 mins to restore the backup…be patient!

It’s not sat in a cupbroad next to my modem and maint switch on a UPS, so feels like a proper comsumer device.

I’m now on OS10 with 2023.5.2.

So far its running really well, as performance is on par with my previous install (running on a linux VM hosted on nvme drive).

I’ve since decied to move pi-hole/adaware, and my nginx installs over from my main server to the Odroid too and this will enable me to have these core network functions running on dedicted hardware, and will also enable me to consider turning my server off for a few hours each night to save some power, as the other function (file backup and media serving dont need to run 24/7.

I’ve yet to measue the power draw of the Odroid but expect it to be really low as its mostly idling at<10% with only 1.5gb ram usage.
I’d seriously conider buy more for other network functions…

Good luck!

Warning: HA newb

HA OS doesn’t see Bluetooth device on 10.1 or 9.5. Host is PopOS 22.04, HA running in KVM, Bluetooth device is Intel 9460/9560 Jefferson Peak (JfP) which was added to the VM in virt-manager after setting the USB to USB 3. If I can get copy to work in the Terminal addon … (argh) … nope have to fat finger it …

$ dmesg | grep Blue
...
Bluetooth: hci0: command 0xfc05 tx timeout
Bluetooth: hci0: Reading Intel version command failed (-110)

My intel NUC installation Bluetooth broke too after upgrade. Works fine on backup RPI4. What are you going to do? Downgrade?

I’m having bluetooth issues on Intel NUC with v10.

I just tried to pugrade from HAOS 9.x to 10.1 and got the folllowing error’s in the supervisor log…

23-05-13 16:04:19 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:09:25 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:09:25 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:09:25 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:09:25 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:14:31 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:14:31 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:14:31 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:14:31 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:19:37 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:19:37 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:19:37 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:19:37 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:24:43 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:24:43 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:24:43 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:24:43 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:29:49 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:29:49 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:29:49 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:29:49 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:30:25 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
23-05-13 16:30:25 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
23-05-13 16:30:35 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
23-05-13 16:30:35 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
23-05-13 16:30:38 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
23-05-13 16:30:38 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
23-05-13 16:30:48 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
23-05-13 16:30:48 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
23-05-13 16:31:00 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug b4c59745
23-05-13 16:31:00 INFO (MainThread) [supervisor.backups.manager] Backing up b4c59745 store Add-ons
23-05-13 16:31:00 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_zwave_js
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_zwave_js
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_adguard
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_adguard
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 6a3d001f_assistant_relay
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 6a3d001f_assistant_relay
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_duckdns
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_duckdns
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 5c53de3b_esphome
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 5c53de3b_esphome
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on cebe7a76_hassio_google_drive_backup
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon cebe7a76_hassio_google_drive_backup
23-05-13 16:31:04 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mosquitto
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_mosquitto
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_nut
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_nut
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_nodered
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_nodered
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on e92a3241_paradox_alarm_interface
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon e92a3241_paradox_alarm_interface
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on db21ed7f_qbittorrent
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon db21ed7f_qbittorrent
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 15d21743_samba_backup
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 15d21743_samba_backup
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_samba
23-05-13 16:31:05 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_samba
23-05-13 16:31:13 INFO (SyncWorker_3) [supervisor.docker.addon] Export image 00185a40/amd64-addon-simplescheduler to /data/tmp/tmpr1ipip82/image.tar
23-05-13 16:31:15 INFO (SyncWorker_3) [supervisor.docker.addon] Export image 00185a40/amd64-addon-simplescheduler done
23-05-13 16:31:15 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 00185a40_simplescheduler
23-05-13 16:34:00 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-05-13 16:34:19 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 00185a40_simplescheduler
23-05-13 16:34:19 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_ssh
23-05-13 16:34:19 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_ssh
23-05-13 16:34:19 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_unifi
23-05-13 16:34:55 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:34:55 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:34:55 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:34:55 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_unifi
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on db21ed7f_arpspoof
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon db21ed7f_arpspoof
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_check_config
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon core_check_config
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 7d80160c_container-stats
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 7d80160c_container-stats
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 15ef4d2f_esphome
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 15ef4d2f_esphome
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 15ef4d2f_esphome-beta
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 15ef4d2f_esphome-beta
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_grafana
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_grafana
23-05-13 16:35:33 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_grocy
23-05-13 16:35:35 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_grocy
23-05-13 16:35:36 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on core_mariadb
23-05-13 16:40:02 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:40:02 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:40:02 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:40:02 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:45:07 WARNING (MainThread) [supervisor.jobs] ‘OSManager.update’ blocked from execution, system is not running - CoreState.FREEZE
23-05-13 16:45:08 WARNING (MainThread) [supervisor.addons.options] Option ‘anonymous’ does not exist in the schema for Mosquitto broker (core_mosquitto)
23-05-13 16:45:08 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:45:08 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
23-05-13 16:45:08 WARNING (MainThread) [supervisor.addons.options] Option ‘interface’ does not exist in the schema for Samba share (core_samba)
23-05-13 16:45:12 WARNING (MainThread) [supervisor.jobs] ‘OSManager.update’ blocked from execution, system is not running - CoreState.FREEZE

It wouldn’t let me upgrade. Any ideas?

Freeze means that a backup or restore is in progress, in your case it’s a backup taking place (your logs say that) wait until that is done and try again

Also fix all your out of date add-on configuration options. Not that it would have prevented you from updating.

Gave 10.2 a go today, but same Bluetooth issues as before, so rolled back to 9.5 again.

1 Like

I’m on 10.2 on an Intel NUC. Bluetooth seems to be ok for me.

I added those 3 notifications

- id: '1683048260046'
  alias: HA Power Status notification
  description: ''
  trigger:
  - platform: state
    entity_id:
    - binary_sensor.rpi_power_status
    to: 'on'
  condition: []
  action:
  - service: notify.mobile_app_iphone
    data:
      title: 'Power Status Failure, status: {{states(''binary_sensor.rpi_power_status'')}}'
      message: 'Power Status Failure, status: {{states(''binary_sensor.rpi_power_status'')}}'
      data:
        image: https://cdn.icon-icons.com/icons2/409/PNG/64/power_40791.png
  mode: single
- id: '1683048750505'
  alias: HA CPU temp warning
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.processor_temperature
    above: 80
  condition: []
  action:
  - service: notify.mobile_app_iphone
    data:
      title: 'HA cpu temp warning, temp: {{states(''sensor.processor_temperature'')}}'
      message: 'HA cpu temp warning, temp: {{states(''sensor.processor_temperature'')}}'
      data:
        image: https://cdn.icon-icons.com/icons2/788/PNG/512/temperature_icon-icons.com_65084.png
  mode: single
- id: '1683228713768'
  alias: HA Ram Usage
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.memory_use_percent
    above: 80
  condition: []
  action:
  - service: notify.mobile_app_iphone
    data:
      title: 'HA ram usage warning, ram usage: {{states(''sensor.memory_use_percent'')}}'
      message: 'HA ram usage warning, ram usage: {{states(''sensor.memory_use_percent'')}}'
      data:
        image: https://cdn.icon-icons.com/icons2/1990/PNG/512/chipcircuitcomputerintegratedmemorymicroprocessorprocessor_123068.png
  mode: single

to know why ha crashes, this morning HA crashed again, so it crashes about once a month, but no notifications has been received.

the log as usual doesn’t tell me anything,
but what are those red characters on the very last line?

edit: forgot to mention that only the Red led was turned on at the time

The release notes for 10.3: * Add patch to fix Bluetooth LE advertisement stall (#2535) (#2598) @agners - Just tested this on NUC and all Bluetooth now seems solid still.

1 Like

I just installed HASSIO and I have a few problems with it.
Especially since the storage is RO it is hard to store changes.

One issue, since I don’t use a lot of sensors, I can easily use ‘conservative’ instead of ‘performance’ with my M1. But where do I store the settings?
Second issue, for HA functions: one meter was set with ‘W’ as unit, another with ‘kW’ as unit. I prefer ‘W’ for unit as 0.123kW does seem awkward. But I need to repeat the settings after each restart of HA (never mind a real reboot).

For the second issue: can I access the configuration.yaml somewhere?
With the developer options I see several yaml files but they seem to be read-only/unchangable.

No you didn’t, because hassio is a product name that disappeared a couple of years ago. I assume you mean HAOS.

configuration.yaml is in /config. Access it via

  1. SSH using the Advanced SSH & Terminal addon; or
  2. The File Editor addon; or
  3. The Studio Code Server addon.

As far as setting units, bring up the entity in the UI and click on the Cog (for settings) and choose a unit. This particular entity is energy rather than power, but you get the idea.

EDIT: to add, don’t know anything about setting your M1 sorry.

The thing about the M1 is, I did choose not to configure the system in detail, accepting not having a fine control. But for small optimizations which are available in the system I only need to see how to switch them on. If I could do that I’d have the best of 2 worlds.

The thing with the units is more that I can change the units, but the changes work only until the next restart. Searching for changing units do show some tips, but I experience some gap in experiments in a template and results showing in a dashboard.

Both problems can eventually be reduced to “how do I write changes back to a mostly read-only system”. And I think it is a general problem with systems like this, regardless of the hardware used.