Clean install 2.5 from repo gives 404

In my continued efforts to try and get openHAB to work with a Zigbee USB stick: I’m currently trying to use a laptop to avoid any potential virtualisation quirks, but I cannot get it to install.

I have a clean install of openSUSE Tumbleweed. Have installed openjdk 1.8 runtime and installed 2.5.0 from the official stable repo.

When I start it up though I just get a Jetty 404 on localhost:8080.

  • Platform information:
    • Hardware: Intel i7-3520M @ 2.9GHz | 8GB RAM | Ooodles of free space
    • OS: openSUSE Tumbleweed 20191230
    • Java Runtime Environment: openjdk version “1.8.0_232”
      OpenJDK Runtime Environment (IcedTea 3.14.0) (build 1.8.0_232-b08 suse-1.1-x86_64)
      OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
    • openHAB version: 2.5

The log files are thoroughly uninspiring:

openhab> log:display 
10:22:30.151 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at
10:22:30.158 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at
10:22:30.336 [INFO ] [rthome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
10:22:36.590 [INFO ] [i.dashboard.internal.DashboardService] - Stopped Dashboard

I feel like I’m missing something obvious, just no idea what! Thanks for the help.

Did you also install the openhab2-addons package? It is known to break things and is only needed if you plan on running the system where it does not have Internet access to install addons.

If you did not really need the package, uninstall it and openhab2. Then reinstall openhab2. If you need the package there is a workaround until 2.5.1 is released.


May need to restart OH a few times after the install. Took me three restarts to get OH working. BTW, make sure to give OH time to completely start before each restart.

That was it. I was getting baize and just installing bits. Although I think it should be noted somewhere, if anybody wants to use that package, they can’t, as it simply doesn’t work by the looks of things.

There is a workaround I tested and posted. This issue slipped by the developers and hopefully will be fixed in a patch release this month.
There was a lot of reorganization within the project and a completely new build system. That is why it took a year to release 2.5.

1 Like