4 hours without any log entry from supervisor. That is not normal. Even on my ‘unsupported’ raspbian installation I get a lot of log entries in 4 hours.
indeed, so my HA has lost his bits haha.
See more strange things, there is a update but I can’t update don’t see the button.
Snapshots are small in file size and not backup all add-ons.
Maybe a clear install with only configuration restore and install addons one by one.
in /var/log/daemon.log I see supervisor lines:
Aug 18 17:40:01 hassio hassio-supervisor[939]: #033[32m20-08-18 15:40:01 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository#033[0m
Aug 18 17:40:01 hassio hassio-supervisor[939]: #033[32m20-08-18 15:40:01 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository#033[0m
Aug 18 17:40:01 hassio hassio-supervisor[939]: #033[32m20-08-18 15:40:01 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/Limych/hassio-addons repository#033[0m
Aug 18 17:40:01 hassio hassio-supervisor[939]: #033[32m20-08-18 15:40:01 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/sabeechen/hassio-google-drive-backup repository#033[0m
Aug 18 17:40:03 hassio hassio-supervisor[939]: #033[32m20-08-18 15:40:03 INFO (MainThread) [supervisor.store] Load add-ons from store: 69 all - 0 new - 0 remove#033[0m
Aug 18 17:41:06 hassio hassio-supervisor[939]: #033[32m20-08-18 15:41:06 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token#033[0m
Aug 18 17:42:07 hassio hassio-supervisor[939]: #033[32m20-08-18 15:42:07 INFO (MainThread) [supervisor.api.security] /snapshots access from cebe7a76_hassio_google_drive_backup#033[0m
Aug 18 17:42:25 hassio hassio-supervisor[939]: #033[32m20-08-18 15:42:25 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json#033[0m
Aug 18 17:42:25 hassio hassio-supervisor[939]: #033[33m20-08-18 15:42:25 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'#033[0m
Aug 18 18:11:09 hassio hassio-supervisor[939]: #033[32m20-08-18 16:11:09 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token#033[0m
Aug 18 18:32:02 hassio hassio-supervisor[939]: #033[32m20-08-18 16:32:02 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json#033[0m
Aug 18 18:32:02 hassio hassio-supervisor[939]: #033[33m20-08-18 16:32:02 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'#033[0m
Maybe this is also the problem that I can’t update to 0.114.2?
Can't process version data
Yup. If Supervisor can’t process version data, supervisor can’t know there is an update.
Is there a way to solve this?
I was able to follow this guide and setup everything on my NUC. HA is running and I’m not getting any errors. Now I’ll move my settings from the Ubuntu/Docker machine which was getting an unsupported environment warning to this machine running Debian/Docker, a supported configuration.
Thanks much for the guide and scripts for a painless installation.
2 Likes
I can’t take credit for the script, but thanks for the feedback on the guide.
Finally got the Debian 10 64Bit image running on SSD on a RPi4 - Here my full steps.
P.S. Since then super fast HA. 
Flash image on a SDCard. Add SDcard and your SSD to your RPi4
You can also add already ssh option and you wifi settings on the /boot/ partition of SDcard
Remove the old dphys version
sudo /etc/init.d/dphys-swapfile stop
sudo apt-get remove --purge dphys-swapfile
Refresh your OS
sudo apt-get update
sudo apt-get full-upgrade
Prepare RPi4 for USB Boot
Refresh your OS with the latest firmware
sudo nano /etc/default/rpi-eeprom-update
sudo rpi-eeprom-update -d -a
reboot
Install RPICLONE (For cloning from SDCard to my SSD, my SSD is /dev/sda, yours can be different)
git clone https://github.com/billw2/rpi-clone.git
cd rpi-clone
sudo cp rpi-clone rpi-clone-setup /usr/local/sbin
sudo rpi-clone sda
After RPICLONE is done open a new terminal window
nano /mnt/clone/boot/cmdconfig.txt
Add rootdelay=5 cgroup_memory=1 cgroup_enable=memory to the line and save the file.
Exit the terminal
shutdown now
Remove the SDCard and boot from SSD now.
Correct location and timezone
raspi-config
Install Docker
sudo -i
apt-get install software-properties-common -y
apt-get update
apt-get install modemmanager
reboot now
Reason I install modem manager first and reboot, because when do with network-manager my RPi freeze
apt-get install network-manager
apt-get install apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq socat bash curl
curl -fsSL get.docker.com | sh
Install Hass.io
systemctl stop ModemManager
systemctl disable ModemManager
curl -sL https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh | bash -s -- -m raspberrypi4
DONE
Here some links I get the information from:
1 Like
Note disabling a service does not mean is isn’t started or cannot be started, simply that it is not started at boot. If another service ‘wants’ or ‘requires’ a disabled service, the service will start.
The way to prevent the service ever being started is to use systemctl mask on the service.
1 Like
I do this only so rpi won’t freeze when I install network-manager… If this is running and install network-manager at certain point of install there is a freezing. I can’t connect to the pi anymore with ssh
Thank you, these instructions worked perfectly for me, on my NUC.
1 Like
there is no boot directory in clone ??? and shouldn’t this be sudo nano?
Do you have the /mnt/clone/boot/?
If so whats in there?
there is no boot directory in clone…doesn’t exist on my system…also see my latest note…some other documentation issues
other errors?
Before you install modem manager you need to enter sudo -i after the reboot.
dphys-swapfile stop is not recognized…I just skipped that step.
I’ll tried evetything now 3 times. last time is system I now running HA on…
Im not a wiskid, just check other pages and combine the steps.
I keep seeing that my installation is unsupported in the log files and also written next to the supervisor version. I plan to wipe my system and install this on my NUC with your guide, but I don’t want to lose all my items. In addition to various integrations, configs, and secrets in the secrets yaml, I also have various items in zwave and zigbee through a USB stick. Can I just run a snapshot in supervisor and save it in a separate location, then run through your steps and restore? Will this guarantee my setup returns to the way it was prior to wiping and running through these steps?
Nothing is guaranteed. If you take a snapshot of your current installation, and also take a manual backup of your ./storage folder, all .yaml files, www folder, etc, you can be as safe as possible.
2 Likes
Thanks. So I run through these steps and restore the snapshot?
That’s it 