Thank you very much. This looks more complete
I’ll try it later according to your instructions
unfortunately the apt update does not work:
openhabian@openHABianDevice:~ $ sudo apt update
OK:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Holen:2 http://davesteele.github.io/comitup/repo comitup InRelease [4.659 B]
OK:3 http://archive.raspberrypi.org/debian buster InRelease
Holen:4 https://deb.nodesource.com/node_12.x buster InRelease [4.584 B]
Holen:5 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease [12,8 kB]
Fehl:2 http://davesteele.github.io/comitup/repo comitup InRelease
Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 0959C4A3DCF89FBF
Fehl:5 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease
Die folgenden Signaturen waren ungültig: EXPKEYSIG 075721F6A224060A openHAB Bintray Repositories <owner@openhab.org>
Es wurden 4.584 B in 3 s geholt (1.316 B/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 117 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
N: Datei »openhab.liste« in Verzeichnis »/etc/apt/sources.list.d/« wird ignoriert, da sie eine ungültige Dateinamen-Erweiterung hat.
W: Während der Überprüfung der Signatur trat ein Fehler auf. Das Depot wurde nicht aktualisiert und die vorherigen Indexdateien werden verwendet. GPG-Fehler: http://davesteele.github.io/comitup/repo comitup InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 0959C4A3DCF89FBF
W: Während der Überprüfung der Signatur trat ein Fehler auf. Das Depot wurde nicht aktualisiert und die vorherigen Indexdateien werden verwendet. GPG-Fehler: https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease: Die folgenden Signaturen waren ungültig: EXPKEYSIG 075721F6A224060A openHAB Bintray Repositories <owner@openhab.org>
W: Fehlschlag beim Holen von http://davesteele.github.io/comitup/repo/dists/comitup/InRelease Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 0959C4A3DCF89FBF
W: Fehlschlag beim Holen von https://openhab.jfrog.io/artifactory/openhab-linuxpkg/dists/stable/InRelease Die folgenden Signaturen waren ungültig: EXPKEYSIG 075721F6A224060A openHAB Bintray Repositories <owner@openhab.org>
W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.
Openhabian-config was updated first:
openHABian users
The latest version of openHABian will do this for you, just run sudo openhabian-config and update openHABian - each time you open the menu, openHABian will check the key’s expiry date and do this for you
- do you have the ‘lastest’ version of openhabian-config ( you can check the version in the about section )
- the openhab signature will be stored under /usr/share/keyrings. Check if it is already there
- manual steps to get the key in place are described at Download openHAB | openHAB
- do you have the ‘lastest’ version of openhabian-config ( you can check the version in the about section )
I think so. Its from 12.12.23:
openHABian Configuration Tool — [openHAB3]{2023-12-12T18:59:04+01:00}(8e591be)
openHAB 3.4.2 - Release Build
- the openhab signature will be stored under /usr/share/keyrings. Check if it is already there
There are two files.
-rw-r--r-- 1 root root 2280 Dez 28 14:48 openhab.gpg
-rw-r--r-- 1 root root 1233 Mai 29 2012 raspbian-archive-keyring.gpg
Are these okay?
- manual steps to get the key in place are described at Download openHAB | openHAB
That is not necessary. The specified gpg file is already there.
Why don’t you just reinstall from scratch and import your old config as recommended ?
I shy away from the effort of a basic installation. I honestly don’t know what is necessary again until I can start oh-config and import a backup. And I still don’t know whether everything is really in the backup? Bindigs, settings etc.
Read the link I gave. You’ve already put more time into this than doing that would have costed.
Plus, unlike an OS upgrade, it’s reversible/non-destructive.
Yes, correct, the file for openhab is there. Is it also referenced in /etc/apt/sources.list.d/openhab.list ?
I have tested this. It is definitely faster.
But…
I got a new DHCP IP address and can no longer log in to the console with my openhabian password.
The browser-based log shows some errors, but I attribute most of them to the wrong IP.
Now yes.
And now the update to bullseye has also gone through.
Now I have an error message that Java 17 is still missing.
It’s all very complicated.
install the package openjdk-17-jre-headless or use openhabian-config to install the related java package.
You can ping the host ?
1 Like
Yes. The system runs with the new IP, which comes from DHCP.
I can ping the host and the website runs on Port 8080
It seems that only a few basic settings are missing.
e.g. a fixed IP address was set before
You can have your DHCP server assign a fixed IP address based on your Raspi’s MAC. Read the docs.
of course, it’s now the default (i.e. openhabian)
1 Like
Now it’s up and running. I went through the second suggestion again:
reinstall from scratch
It went faster now.
Changed password of openhabian and changed IP address (yes - I use fixed IPs for my servers and printers)
Mosquitto Broker still had to be installed, but that can be done quickly via oh-config.
Now it runs with bullseye.
Many, many thanks for your support.
Now the next challenge: Update to OH4.
Do you have any best-practice suggestions?
Read the FAQ others and I linked to.
Now I have bullseye and Java17.
The correct branch is set.
But I still get the message Old OpenHAB Version : “Attention!”
Everything seems to be ok. No errors or warnigs to be seen.
What could be the problem now?
What branch, set where and why do you think it is correct there?
when doing what ?
How am I supposed to know ? Read the docs to find out how to enable debugging (debug=maximum in openhabian.conf) and to provide a logfile of what’s going on, else noone can tell.
The branch is “openHAB branch”
I have selected the release option in OH-Config [01]:
I have just discovered that the Configuration Tool is probably out of date:
I think I have already seen a version from December.
I thought it was self-updating. Does it not? How can I do this manually?
Why did you change it before updating OH (or why at all?)
It should. Did you flash an old image ? Download latest and try again with that.
It was OpenHAB3 like recommended in the scratch reinstall.
No. Downloaded yesterday.
I’ll try debugging and get back to you
Thank you.