If anyone is able to give me a buddy check, I’d appreciate it. Your mission is to install OpenHAB 2 on Debian on a Raspberry Pi Zero and get it to show you any web UI.
After installing OpenHAB2 on Debian 12 (bookworm), I can’t get it to start and serve up the page that asks me which installation I want (e.g. standard). Instead I just get an error 404 from Jetty.
I have reproduced this problem on hardware as well as in a VM, and I’m sad to report that it seems to be repeatable, and also affect Debian 11 (bullseye). Yes, you read that right, the same scripts that used to work to produce a working image no longer work.
The logs show error about downloading add-ons, which were reported here and another thread that I commented on but was unable to resolve.
According to rlkoshak, this shouldn’t happen in 2.5.12 (which is what I have installed; confirmed by both apt and openhab-cli). I also saw the strange report of OpenHAB being 2.5.3 (with openhab-cli, IIRC). I think all the things in this paragraph are red herrings, but I wanted to report them in case anyone trying to reproduce my work sees the same things.
If you want to use literally the same scripts I’m using, check out the v1.5-dev branch of HestiaPi / raspberrypi-automation · GitLab and run this (set up SSH keys first and put the IP of your raspberry pi in there):
cd ansible
ansible-playbook -i 192.168.1.137, --extra-vars "device=mmcblk0 partition_1=mmcblk0p1 partition_2=mmcblk0p2" hestiapi.yml
When it gets stuck and eventually times out, you should be able to browse to http://192.168.1.137:8080 to see the error message from Jetty.
If I don’t get this sorted out in a few days, I’m going to switch gears and try splitting the front-end from the back end. That’ll allow me to try to install OpenHAB 4 on a traditional server and port all the rules over to that. I might try OpenHAB 2 on a traditional server just to see if I can reproduce this issue outside of a Raspberry Pi Zero.