Hassbian Problems with Upgrade

I had Hassbian working on a RP3. I noticed that there were several notifications of problems. These seemed to be centered around no database program installed. I attempted to install sqlite3. However, the installed libraries were newer that what sqlite3 required and I got errors about broken packages. Nothing I did seemed to get past this and everything on the Internet said reinstall.

As a test I put that SD Card aside and got a fresh copy of the Hassbian zip file. Put it on a clean SD card. After it got done installing and configuring, I logged in and attempted to upgrade it with hassbian-config and install mosquitto

I got messages about missing archives as shown below:

E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/m/mosquitto/libmosquitto1_1.5.7-1_armhf.deb 404 Not Found [IP: 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/m/mosquitto/mosquitto_1.5.7-1_armhf.deb 404 Not Found [IP: 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/m/mosquitto/mosquitto-clients_1.5.7-1_armhf.deb 404 Not Found [IP: 80]

Basic Noob Questions:

  1. Is Hassbian still supported?
  2. If not Hassbian, what is the recommended basic install for a RP3?
  3. Did I miss something on the setup that is causing these archive issues?
  4. What database is recommended for Hassbian on a Raspberry PI?


---- Steve


sudo apt-get update
  1. It’s been deprecated and no longer officially supported. However, it’s Raspbian + HA…
  2. Raspbian Buster + venv install will give you the same thing as you’re used to
  3. Probably not
  4. The default SQLite works, but MariaDB is always a good choice

Thank you for the very fast information.
sudo apt-get update did not resolve any of the repo issues. However,
sudo apt-get --allow-releaseinfo-change update seemed to do the trick.

I think the Buster release was still experimental when the last Hassbian scripts were created, so they could not have pointed to the correct folders since they did not exist yet.

In any event, since Hassbian is depreciated, I will stop using it and go with one of the other methods you suggested.
Thanks again.

No, you don’t need to change anything.

you already have Raspbian + HA in a venv. That is what hassbian ends up providing to you when you run the hassbian install script by burning the image and booting up the Pi. It’s all done automatically.

The only thing that might change is that some of the hassbian scripts might stop working at some point in the future.

the bottom line is that you don’t need to do anything and you will barely notice that hassbian is no longer supported until/if/when you ever need to re-install your HA.

1 Like