Well then. Latest guidance is here, on RPi stay on SD and add mirroring. SSDs aren’t supported.
1 Like
Just stupid question from my side…
If I choose 41 openhab Release today:
What will be installed?
Openhab 3.4.4 Stable or Openhab 4.0.0 M5?
If I choose openhab Release tomorrow will than bei Openhab 4.0.0 RC1 installed?
Thank you in advance…
latest OH4 milestone will be installed.
1 Like
Thank you
Ah no if you go that way via menu it’s probably release so still 3.4.4
Enable debugging and see for yourself
I can confirm that
- the release branch will install 3.4.4-2
- the openHAB Milestone build will install 4.0.0~RC1-1
Unfortunately install openJDK 17 via 45.
I have added a session recording that shows the issue
$ apt-get install --yes -o DPkg::Lock::Timeout= openjdk-17-jre-headless
+ apt-get install --yes -o DPkg::Lock::Timeout= openjdk-17-jre-headless
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:
openjdk-17-jre-headless : Depends: libc6 (>= 2.29) but 2.28-10+rpt2+rpi1+deb10u2 is to be installed
Depends: libgcc-s1 (>= 3.5) but it is not installable
oh4-installjdk17.txt (39.6 KB)
I then made sure that openhabian has the latest updates in particular because of the outdated public key (see Linux Repo Public Key is Expiring Soon) but unfortunately it doesn’t make a difference. Note that the update-line given in that thread doesn’t solve that problem either.
apt-get update fails
sudo apt-get update
Hit:1 http://phoscon.de/apt/deconz buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 http://davesteele.github.io/comitup/repo comitup InRelease [4,659 B]
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 http://archive.raspberrypi.org/debian buster InRelease
Hit:6 https://deb.nodesource.com/node_16.x buster InRelease
Get:7 https://repos.influxdata.com/debian buster InRelease [7,038 B]
Get:8 https://packages.grafana.com/oss/deb stable InRelease [5,984 B]
Hit:9 https://openhab.jfrog.io/artifactory/openhab-linuxpkg testing InRelease
Hit:10 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bullseye InRelease
Err:3 http://davesteele.github.io/comitup/repo comitup InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0959C4A3DCF89FBF
Err:7 https://repos.influxdata.com/debian buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
Err:8 https://packages.grafana.com/oss/deb stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E439B102CF3C0C6
Fetched 7,038 B in 6s (1,230 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://davesteele.github.io/comitup/repo comitup InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0959C4A3DCF89FBF
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E439B102CF3C0C6
W: Failed to fetch http://davesteele.github.io/comitup/repo/dists/comitup/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0959C4A3DCF89FBF
W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E439B102CF3C0C6
W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
W: Some index files failed to download. They have been ignored, or old ones used instead.
well that doesn’t happen on a fresh image install so must be related to your previous activity on your box
Do you have any idea how to solve it?
Would the following be a solution that could work?
- Install a new openHAB 3.4
- import a backup of my prod system
- then upgrade to 4.0?
so I would omit the “broken” openhabian setup on my production system?
yes that should work.
Or g**gle how to resolve Debian dependencies. It’s usually about using a different repo in one of the /etc/apt/source.list.d/* repo definition files.
Check if they still refer to buster and change to bullseye for a test
1 Like
I tried the latter for the last hours but wasn’t really successful.
I was even able to install zulu-17 on my machine via SDKMAN but then I have to set JAVA_HOME myself (probably in setenv) but I wonder if that is a good idea as I like to still use openhabian-config in the future and I am kind of going astray from its own management of the setup).
So I will try the above path. Hopefully that goes well (I will report for anyone who wants to follow the same approach).
On Raspi try
deb [trusted=yes] http://mirrors.ocf.berkeley.edu/raspbian/raspbian bullseye main
It took me a while because I needed to restore the sd card from where I started (I already had tried too many things).
- I have added the above to /etc/apt/sources.list and did an “sudo apt update && sudo apt upgrade -y”
- I still got the PUPKEY errors but it installed a lot (>550 installs) including updating from 3.4.2 to 3.4.4-2 and then it takes “aaages” (30 minutes +) until everything was installed, it seemed to have updated an afwul lot.
and I ended up with the regression
“Some .kar files are not installed yet. Delaying add-on installation by 15s” … 
You have to update the pubkey, otherwise apt won’t install nothing from the openHAB repository.
I’ve used this command:
wget -4qO- https://openhab.jfrog.io/artifactory/api/gpg/key/public | gpg --dearmor | sudo tee /usr/share/keyrings/openhab.gpg >/dev/null
(I had to pin to IPv4 to have success, if you don’t have issues with IPv6, omit the -4- option (so the start of the line would be wget -qO- )
If there is any error for this command, you probably have some missing packets (e.g. gpg)
JFTR: since June the current version (debian and Raspberry Pi OS) is bookworm, which works flawless for me 
but of course I wouldn’t recommend to upgrade from a version other than bullseye. 
1 Like
Latest openHABian should be updating the repo key for you on start.
Please enable debugmode=maximum and check if it does, the code is in /opt/openhabian/functions/openhabian.bash in a routine called openhabian_update_check() that you should see flying by.
cc @Benjy
I just downloaded the latest version 1.8 of openhabian as wanted to start with 3.4.4, install my backup and then upgrade but it is automatically installing 4.0 as mentioned in the release notes.
Does it make sense therefore to download openhabian 1.7, install my backup and then upgrade with openhabian-config?
No. But you can manually downgrade to OH3 apt-get install openhab=....
ok, thanks, that’s a pity. → no complaining:
I don’t get my 3.2 to a valid state anymore and installing 3.4.4. can only be achieved by the downgrade above. I am now in the midst of following the idea of directly moving to 4.0 (already installed and backup is restored) and importing my backup from 3.2 (though that is obviously not the recommended way as it also is missing the migration tool which is not applied). Hopefully this will be more successful than the full day yesterday I tried to rescue 3.2 and upgrade it. If that doesn’t work I will try the downgrade idea. Thanks Markus.
Check out how to manually run the upgrade tool that comes with 4.0.
Use it before you start OH4 with your 3.2 config. It’s converting a 3.x config to a 4 config.
I’ve never used so can’t tell the details but it’s probably linked in the OH4 release notes.
1 Like
Just a short note. If you use openhabian-config point 41 to switch to the latest version, which is now 4.0, it still says „ OH3 installing“.
trying to install influxdb on a debian 12 give this:
Err:7 https://repos.influxdata.com/debian bookworm Release
404 Not Found [IP: 13.224.222.56 443]
Hit:8 https://openhab.jfrog.io/artifactory/openhab-linuxpkg testing InRelease
Get:9 https://packages.grafana.com/oss/deb stable/main amd64 Packages [133 kB]
Reading package lists... Done
E: The repository 'https://repos.influxdata.com/debian bookworm Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
isnt the openhabian based on latest debian 12 sorry for not ready latest progress …