Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:304
Integration: Recorder (documentation, issues)
First occurred: 16:52:42 (1 occurrences)
Last logged: 16:52:42
Version 3.27.2 of SQLite is not supported; minimum supported version is 3.32.1. Starting with Home Assistant 2022.2 this will prevent the recorder from starting. Please upgrade your database software before then
I am running HA Core on a Raspberry PI…
$ cat /etc/rpi-issue
Raspberry Pi reference 2019-09-26
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 80d486687ea77d31fc3fc13cf3a2f8b464e129be, stage2
When I try to upgrade sqlite3 I get…
$ sudo apt install sqlite3 --upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
sqlite3 is already the newest version (3.27.2-3+deb10u1).
wget https://sqlite.org/2021/sqlite-autoconf-3360000.tar.gz
tar -xvf sqlite-autoconf-3360000.tar.gz
cd sqlite-autoconf-3360000
./configure
make
sudo make install
hass still complained. It turned out to be where the libraries were installed.
The old libraries were in /usr/lib/arm-linux-gnueabihf/, whereas the new ones were in /usr/local/lib.
At that point I took the easy option (hass is the only application running, so no risk to other apps)…
I tried a lot of different things to get this working, I didn’t want to overwrite the system sqlite.
Annoyingly there is no clean way to point a freshly compiled python at a freshly compiled sqlite (eg a --with-sqlite configure flag).
In the end I stood up a local mariadb instance.
What would be nice would be if HA supported using the pysqlite3 module, which offers compatibility with the stdlib sqlite3 but allows a custom sqlite build.
sudo apt install sqlite3 -t bullseye
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la informaciĂłn de estado... Hecho
No se pudieron instalar algunos paquetes. Esto puede significar que
usted pidió una situación imposible o, si está usando la distribución
inestable, que algunos paquetes necesarios aĂşn no se han creado o se
han sacado de «Incoming».
La siguiente informaciĂłn puede ayudar a resolver la situaciĂłn:
Los siguientes paquetes tienen dependencias incumplidas:
libc6-dev : Rompe: libgcc-8-dev (< 8.4.0-2~) pero 8.3.0-6+rpi1 va a ser instalado
E: Error, pkgProblemResolver::Resolve generĂł cortes, esto puede deberse a paquetes retenidos.
sudo apt install sqlite3 -t bullseye
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
I did this today, and it seemed to work as it should. Then I tried to reboot, and I now have two Pi’s that throws an error message saying “No session for pid xxx”, and the menu line in Buster doesn’t show. I have not yet found a fix for it.
Edit: And after an hour it’s worse, now I can’t even see the desktop with VNC on one of the Pi’s.
What happened is that it became a bastard version of Buster and Bullseye (latest Raspbian version), which made all sorts of probles. I’m glad I have backups…
Trying to pull in the bullseye version pulled in lots of other things, and ended up making the system unusable. I was forced to revert to a backup. But the solution from ColinRobbins worked fine for me!
Thanks for this answer. It helped me
I think if you use: ./configure --libdir= /usr/lib/arm-linux-gnueabihf/
You do not have to copy. I didn’t test this yet
Many thanks for the solution! As an alternative to overwriting existing sqlite library files, you can export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib before starting hass. This way you can keep both versions of the library and not affect any other current or future apps.
I have not yet found a fix for it.