All, please help with testing openHABian for the upcoming OH4 release.
I’ve just updated the main branch to offer installing OH4 by default
I need you to check it out, please test it in the field.
Switch to main branch. Set debugmode=maximum and record the window output.
Let me know issues in this thread. Thanks.
Hi Markus,
I just checked it on my dev system. I first changed this
which updated nicely to
I did not chose 02 but I then went to 41 (I did not run this but always cancelled it):
Note, I am on a snapshot build which is already beyond OH4 M3, so I do expect a downgrade warning, which I get but it says openHAB 2
I did it anyway and it starts to download openHAB 2. Is this intended?
The same applies to Milestone which warns me to go back to OH2 milestone.
Then I went to 02 (having selected the release branch as mentioned above) and installs 4.0.0-SNAPSHOT (#3487)
The I chose latest and nothing changes (it comes back pretty quickly). So I presume release and latest are currently the same and this is the intended effect?
I hope that this is what you expected.
I intent to purge the whole system tomorrow to setup OH4 again as described in the OH4 milestone thread now that you provided this update I want to try it afain… Let me know if you want me to do anything in a particular sequence to upgrade my OH3 instance to OH4.
First, enable debugmode=maximum and record the output.
What’s the output of dpkg -s 'openhab' 2>/dev/null | grep Config-Version ?
Eventually edit openhab4_is_installed() in /opt/openhabian/functions/helpers.bash to fix the check
Repeat 41
Well starting from a snapshot isn’t quite what I’m looking for in the first place, commonly users would not be on any snapshot but OH3. Well appreciated, though.
yes as the release package isn’t available, this option installs the milestone.
I somewhat doubt that is intended, its probably just a forgotten text update. I would fix it but I’m unable to, @mstormi can you look at it?
Also yes, for those wondering I’m alive and should be back to full activity and contribution in about 1 year following the completion of my missionary service.
How should I exactly do that?
sudo openhabian-config > ohc.txt
doesn’t really work nicely because it doesn’t allow me to be completely interactive anymore. Anyway, I was able to capture something.
ohc.txt (12.7 KB)
dpkg -s ‘openhab’ 2>/dev/null | grep Config-Version
Config-Version: 4.0.0~S3487-1
How exactly do you want me to fix this function?
openhab4_is_installed() {
if [[ $(dpkg -s 'openhab' 2> /dev/null | grep Config-Version | cut -d' ' -f2 | cut -d'.' -f1) =~ 4 ]]; then return 0; else return 1; fi
}
Well starting from a snapshot isn’t quite what I’m looking for in the first place, commonly users would not be on any snapshot but OH3.
As soon as we are done with the above I will start with OH3.4 and a backup of my prod system. Just let me know the exact steps you want me to do then, but first I would think, let’s finalize the above steps on the snapshot and fixing the OH2 thing?
Edit openhabian.conf
Record in PuTTy or whatever terminal you use.
That should work then but you say it does not. Show the debug recording please.
How to set debug was clear → see the attached file. I have it on anyway the whole time. I just wasn’t sure how to “record” it. Will do tomorrow…
Did you check the attached file ohc.txt? It should have recorded something already.
no it did not contain anything useful
I was able to find a way to do the recording in iterm. however, I had to reinstall as I downgraded unintentionally to openHAB 2, so it is not a typo , it really does the downgrade.
Even worse, I am not able to go to OH4 now. I set 01 to latest and therefore updated openhabian. Then It said I could go to openHAB 4 but it doesn’t. I tried the upgrade menu and it stayed on 3.4.4 and I tried 41 to go to the latest version and same there.
Therefore, Markus, can you tell me the exact steps how I should proceed after installation of the latest openhabian that should bring me to the latest OH4 snapshot (I know it had worked before) and I will then record this.
I am currently on 3.4.4 with a plain installation.
Stefan it depends on the details of your existing openhabian install (which branch is it etc) and what steps you already took. It doesn’t make sense that way.
Ensure you are on main branch. Record and show the log else I cannot say anything about it.
Ok, I am on Main:
dpkg -s ‘openhab’ 2>/dev/null | grep Config-Version
reveals an EMTPY result
openhab-cli info
reveals Version: 3.4.4 (Build)
Now I start the recording and I start 02
and it comes back extremely fast. Here is the log: (edit: → deleted log)
Sorry but that’s a useless log.
Enable debugging in openhabian.conf, and do a proper recording so the output is ASCII-readable.
Use script or a different terminal program,
Sorry, my bad, due to the reinstall the debug setting got lost and I forgot about it. Here you go.
oh344-oh4.log (111.2 KB)
When i start again SSH i have this information:
sed: can’t read /var/lib/openhab2/etc/version.properties: No such file or directory
With Legacy openhabian, I have this splash screen:
Linux openhabian 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jun 7 15:49:51 2023 from 192.168.0.69
###############################################################################
############### openhabian ##################################################
###############################################################################
## Ip = 192.168.0.163
## Release = Raspbian GNU/Linux 11 (bullseye)
## Kernel = Linux 6.1.21-v8+
## Platform = Failed to start Check for Raspberry Pi EEPROM updates.
## Uptime = 0 day(s). 0:0:36
## CPU Usage = 59.09% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
## CPU Load = 1m: 2.67, 5m: 0.73, 15m: 0.25
## Memory = Free: 6.65GB (87%), Used: 1.01GB (13%), Total: 7.67GB
## Swap = Free: 2.43GB (100%), Used: 0.00GB (0%), Total: 2.43GB
## Root = Free: 43.35GB (77%), Used: 12.53GB (23%), Total: 58.29GB
## Updates = 0 apt updates available.
## Sessions = 1 session(s)
## Processes = 146 running processes of 32768 maximum processes
###############################################################################
_ _ _ ____ _
___ ___ ___ ___ | | | | / \ | __ ) (_) ____ ___
/ _ \ / _ \ / _ \ / _ \ | |_| | / _ \ | _ \ | | / _ \ / _ \
| (_) | (_) | __/| | | || _ | / ___ \ | |_) )| || (_) || | | |
\___/| __/ \___/|_| |_||_| |_|/_/ \_\|____/ |_| \__|_||_| | |
|_| openHAB 3.4.4 - Release Build
Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help
When switching openhabian to main or openhab4 I have some issues:
A cosmetic issue since some time: installing deCONZ with a non-standard port (e.g., 8007) is possible, but openhabian’s final screen says that port 8001 has been selected.
Actually, installing deCONZ needs a special fix since some days due to a Debian error. Therefore, openhabian fails to install as well.
I don’t see anything unusual about this log. Option 02 is supposed to update all packages to their latest version, and so it does. You didn’t select any of the 4X options.
Take a recording of the action that you believe should behave different.
what’s your point? Posting logs without any reasonable description is pointless.
The main version don’t install Firemot and i have an issue with /var/lib/openhab2/.
I also try install Firemot again via openhabian but the problem persist.
Linux openhabian 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch 64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jun 7 23:17:24 2023 from 192.168.0.13
2023-06-07 23:17:24,903: FireMotD: Info: No FireMotD ExportFile detected. Please generate with "sudo .\/FireMotD -S"
sed: can't read /var/lib/openhab2/etc/version.properties: No such file or direct ory
sed: can't read /var/lib/openhab2/etc/version.properties: No such file or direct ory
Welcome to __ _____ ____ _
____ ____ ___ ____ / / / / | / __ )(_)___ _____
/ __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __ / / __ `/ __ \
/ /_/ / /_/ / __/ / / / __ / ___ |/ /_/ / / /_/ / / / /
\____/ .___/\___/_/ /_/_/ /_/_/ |_/_____/_/\__,_/_/ /_/
/_/
openHAB ()
Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help'
2023-06-07_23:24:53_WEST [openHABian] Updating Linux package information... OK
2023-06-07_23:24:53_WEST [openHABian] Downloading FireMotD...
Update...
$ update_git_repo /opt/FireMotD master
2023-06-07_23:24:53_WEST [openHABian] Updating FireMotD, master branch from git. ..
$ git -C /opt/FireMotD fetch origin
$ git -C /opt/FireMotD fetch --tags --force --prune
$ git -C /opt/FireMotD reset --hard origin/master
HEAD is now at 3d2bea6 fix
$ git -C /opt/FireMotD clean --force -x -d
$ git -C /opt/FireMotD checkout master
Already on 'master'
Your branch is up to date with 'origin/master'.
OK
OK
2023-06-07_23:24:56_WEST [openHABian] Installing FireMotD...
$ make --always-make --directory=/opt/FireMotD install
make: Entering directory '/opt/FireMotD'
cp FireMotD /usr/local/bin/FireMotD
chmod 755 /usr/local/bin/FireMotD
mkdir -p /usr/share/firemotd/data
mkdir -p /usr/share/firemotd/templates
mkdir -p /usr/share/firemotd/themes
mkdir -p /usr/share/firemotd/cache
cp templates/* /usr/share/firemotd/templates
cp themes/* /usr/share/firemotd/themes
make: Leaving directory '/opt/FireMotD'
$ make --always-make --directory=/opt/FireMotD bash_completion
make: Entering directory '/opt/FireMotD'
cp bash_completion.d/FireMotD /etc/bash_completion.d/FireMotD
make: Leaving directory '/opt/FireMotD'
OK
2023-06-07_23:24:56_WEST [openHABian] Generating FireMotD theme...
$ FireMotD -S -d -D all
2023-06-07 23:24:56,706: FireMotD: Info: Debug mode
2023-06-07 23:24:56,715: FireMotD: Info: FireMotD action save started
2023-06-07 23:24:56,725: FireMotD: Info: Action "save"
2023-06-07 23:24:56,734: FireMotD: Info: Exportfile /usr/share/firemotd/data/Fir eMotD.json found.
2023-06-07 23:24:56,743: FireMotD: Info: Template type set to all. Overwriting..
2023-06-07 23:24:56,840: FireMotD: Info: Exploring HostIp
2023-06-07 23:24:57,037: FireMotD: Info: Exploring Release
2023-06-07 23:24:57,244: FireMotD: Info: Exploring Kernel
2023-06-07 23:24:57,440: FireMotD: Info: Exploring Platform
2023-06-07 23:24:57,655: FireMotD: Info: Exploring InstallDate
2023-06-07 23:24:57,845: FireMotD: Info: Exploring Updates
2023-06-07 23:25:04,395: FireMotD: Info: Exploring Httpd
2023-06-07 23:25:04,582: FireMotD: Info: Exploring Nginx
2023-06-07 23:25:04,768: FireMotD: Info: Exploring Mysql
2023-06-07 23:25:05,081: FireMotD: Info: Exploring Postgres
2023-06-07 23:25:05,266: FireMotD: Info: Exploring Php
2023-06-07 23:25:05,548: FireMotD: Info: Exploring Elasticsearch
2023-06-07 23:25:05,734: FireMotD: Info: Exploring Logstash
2023-06-07 23:25:05,919: FireMotD: Info: Exploring Kibana
2023-06-07 23:25:06,103: FireMotD: Info: Export system data to "/usr/share/firem otd/data/FireMotD.json" finished.
2023-06-07 23:25:06,120: FireMotD: Info: ExportFile: -rwxrw-rw- 1 root root 3231 Jun 7 23:25 /usr/share/firemotd/data/FireMotD.json
2023-06-07 23:25:06,130: FireMotD: Info: FireMotD action save finished
$ FireMotD -G Gray
OK
2023-06-07_23:25:20_WEST [openHABian] Setting up FireMotD apt updates count service...
Make FireMotD check for new updates every night...
$ install -m 644 /opt/openhabian/includes/firemotd/firemotd.service /opt/openhabian/includes/firemotd/firemotd.timer /etc/systemd/system/
$ systemctl -q daemon-reload
Make FireMotD check for new updates after using apt...
$ install -m 644 /opt/openhabian/includes/firemotd/15firemotd /etc/apt/apt.conf.d/
Initial FireMotD updates check
$ FireMotD -S
OK
2023-06-07_23:25:33_WEST [openHABian] Checking for default openHABian username:password combination... FAILED
2023-06-07_23:25:33_WEST [openHABian] We hope you got what you came for! See you again soon ;)
openhabian@openhabian:~ $
That’s just a cosmetic problem and does not happen on new installs.
This thread is explicit about testing the changes and procedures for OH4.