Ha restore from backup - addons issue

I upgraded my HA rasp pi4 from Buster to Bullseye using the raspberry pi home assistant official image.

I then restored from backups (2 different ones so far) and HA is built with 90% of my ADDONS missing and is thus unusable. It means pretty much every device is no longer functional in HA, as Mosquitto broker, zigbeemqtt and numerous other connections have gone.

One thing I noticed before opening the HA cli successfully was that it was not accessible after the initial restore, even though the pi screen seemed complete, along with the homeassistant.local:8123 url info.

I had to power up the Pi4 again before I could access the cli.

Any suggestions how to proceed? It is a lot of missing addons and I am not sure which I need.

I am NOT using Docker but am using supervisor

OK. Situation altered now. I did a partial restore of the files and add-ons.

I noticed that the add-ons installation appears to work differently since my last restores a few months back. These are installed in sequence after the hA gui is back up. Have to say, even though I accept there will be good reasons for this, it makes a half hour restore take over 4 hours in my case.

However, issue not resolved. I backed this partially restored HA up with the original core image from the raspberry pi imager, just to play safe.

Of course, this had none of my dashboards, webhooks, alexa settings etc. So then tried a partial restore of the buster backup HA core, to complete the full restore.

This seemed to be stuck for hours with no movement. Eventually, had to restart HA at the pi terminal screen. Opened HA and core seems to be unchanged. None of my dashboards, webhooks etc.

Thinking about manually re-adding these using the backups if possible, assuming a full backup does store dashboards and other core settings in an accessible backup location. Any ideas on whether these can be retrieved?

A backup is just a gzipped tar file. Unzip, untar and copy to /usr/share//hassio (that is where a supervised installation should keep its files)

But why not upgrade to bookworm ? Bullseye will be unsupported in a few months.

I simply thought I would upgrade to the supported Raspberry Pi image. Seemed sensible to get away from an OS that even HomeAssistant deem out-of-date. I will have a go with the usr/share/hassio folders. Really not sure what was happening with the restores as I selected folders and thought this would suffice. I will try the manual update route.

Running Raspberry OS or Debian ? Raspberry OS is unsupported anyway for a supervised installation.

I realise I have got some things mixed up. I was upgrading more RPI4s, some of which were Raspbian OS. At the same time, I created a fresh HA RPI4 using the official RaspberyPiImager Home Assistant OS 10.4 and restored my HA backup to this one. Probably a pointless exercise that has got me in this tangle. Of course my backup and new installation were the HA OS so I did not need to do this at all. However, I am where I am and this is something of a mess. I am going to try even older backups and restoring those.

OK needs fresh update now my brain is working better.

Have full backup of HA supervised system with core 2023.7.3.

Installed fresh HA from RaspberryPi Imager Home Assistant OS. Decided to downgrade new installation to 2023.7.3 I.e. same version. Hoped this would help solve issues if same version.

Did full restore. It took several hours but finally had a system up. However, several addons were not Started and wouldn’t when I manually attempted to start. List is:

zigbee2mqtt
nodered
zwave js specific not ui
tileboard
ring mqtt with video
ewelink
grafana
influxdb
ring livestream
Samba nas
tasmo admin

Others had started.

I was aware of the issue with restores and addons not starting so uninstalled some of these and reinstalled, intending to do partial addon restores later. However, even with combinations of system unintalling and system restarts, then installing with system restarts, addons are not starting in their “vanilla” format. For example, Zigbee2mqtt is showing that it is receiving mqtt from zigbee devices in the logs after I press Start but it does not show as started and still has the dreaded red spot showing as Stopped. Please help!!!

Closing and restarting as fresh topic as initial description was incorrect and confused matters