Home Assistant multiple issues after upgrading to the latest version

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | 10.2.3
  • Distro version | trixie
  • Kernel version | Linux raspberry-pi 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11) aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi 4 Model B
  • Power supply used | Standard RaspberryPi 5V 1A
  • SD card used | USB external drive

Additional Information (if applicable)

  • Software title | Home Assistant
  • Was the software title installed freshly or updated/migrated?
    • Updated
  • Can this issue be replicated on a fresh installation of DietPi?
    • Don’t know
  • Bug report ID | I didn't send the bug report

Steps to reproduce

  1. Have Home Assistant 2026.2.1 installed on DietPi 10.2.3
  2. Backup in HASS
  3. Upgrade to the latest version of Home Assistant using: sudo dietpi-software reinstall 157
  4. Restore using backup from step 2
  5. Notice that “nothing works”, almost all integration have “Not loaded” errors underneath
  6. In logs I can see a lot of errors with ModuleNotFoundError

Expected behaviour

  • Integrations “just work” as it was with previous upgrades

Extra details

I had some issue with integration, and accidentally removed wrong device, so I wanted to restore from backup, but (don’t know if it’s DietPi or HASS issue) as deps folder is not a folder but symbolic link the restore in HASS never works, it requires some manual patching. I always forgot what are the proper steps then, and when HASS didn’t want to restore and start I went with reinstall path, but it was unfortunately also upgrade and I’ve managed to come up with a way of making the restore work, but now I’m having issues with “restoring functionality”.
The missing modules are:

  • metno
  • tuya_sharing

Is there a simple way of installing HASS in 2025.2.1 version?

Please update to the latest DietPi version, and reinstall Home Assistant:

dietpi-update 1
dietpi-software reinstall 157

The latest version fixes the backup restore issue. And since the Python environment is recreated once, possible dependency issues should be solved as well. Otherwise we can further investigate from there.

Why such an old version? dietpi-software will always install the latest version. You can downgrade manually, but no guarantee that this works well, i.e. whether configs and database of the new version will work without issues on an older version.

I managed to patch it up, by installing missing pip modules. Only Tuya integration and AsusWRT has issues. AsusWRT is logging: TypeError: AsusWrt.init() got an unexpected keyword argument ‘interface’. And Tuya logs: ModuleNotFoundError: Platform tuya.alarm_control_panel not found.

I’ll update DietPi and do a backup and reinstall and see if it helps.

Sorry: I had 2026.2.1 version of Home Assistant not 2025.2.1.

Wow! After DietPi upgrade and HomeAssistant reinstall everything worked!

Thank you very much!

As a side note I now got this warning from HomeAssistant:

This system is using the Core installation type, which has been unsupported since Home Assistant 2025.12. To continue receiving updates and support, migrate to a supported installation method.

Should I try to migrate to the supported installation type?

Nothing needs to be done. All good. As of now you can continue using your system.

EDIT: Ah lol, I thought the issues were present after the update+reinstall :smile:.

The supported installation type means their Docker container. However, only because they stopped supporting bare metal installations their end, does not mean that the HA core module cannot run well bare metal, just the way it does within their container. They just won’t help you anymore in their forum/GitHub, if you face issues related to the environment. Some background also here: Home Assistant Deprecating Core and Supervised installation methods, and 32-bit systems · Issue #7544 · MichaIng/DietPi · GitHub

“To continue receiving updates” is misleading. HA core is, as the name suggest, the core component of every HA installation type, so of course it is developed like the container images and everything around, and can be updated manually without a container or something.

Thanks you!