OH5 does not work after upgrade using openhabian-config

I am running openhabian on Debian, inside a ProxMox VM (QEMU). For this system Java 21 is available so I made a backup of my VM and performed the update from openhab4 to by using openhabian-config.

Unfortunatelty after the upgrade openhab does not work, all things remain NOT YET READY. But I have no idea where to look, as no error is given in the log or from the service.

systeminfo
openhabian@openhabdeb:~$ fastfetch 
        _,met$$$$$gg.          openhabian@openhabdeb
     ,g$$$$$$$$$$$$$$$P.       ---------------------
   ,g$$P""       """Y$$.".     OS: Debian GNU/Linux 12 (bookworm) x86_64
  ,$$P'              `$$$.     Host: KVM/QEMU Standard PC (i440FX + PIIX, 1996) (pc-i440fx-9.2)
',$$P       ,ggs.     `$$b:    Kernel: Linux 6.1.0-39-amd64
`d$$'     ,$P"'   .    $$$     Uptime: 1 hour, 49 mins
 $$P      d$'     ,    $$P     Packages: 1219 (dpkg)
 $$:      $$.   -    ,d$$'     Shell: bash 5.2.15
 $$;      Y$b._   _,d$P'       Terminal: /dev/pts/2
 Y$$.    `.`"Y$$$$P"'          CPU: Common KVM processor (2) @ 2.39 GHz
 `$$b      "-.__               GPU: Red Hat, Inc. QXL paravirtual graphic card
  `Y$$b                        Memory: 1.29 GiB / 3.82 GiB (34%)
   `Y$$.                       Swap: Disabled
     `$$b.                     Disk (/): 9.08 GiB / 31.33 GiB (29%) - ext4
       `Y$$b.                  Local IP (eth0): 192.168.3.202/24
         `"Y$b._               Locale: en_US.UTF-8
             `""""
---
openhabian@openhabdeb:~$ getconf LONG_BIT
64
journalctl -u openhab
openhabian@openhabdeb:~$ sudo journalctl -u openhab --no-pager | tail -20
Sep 11 20:33:56 openhabdeb karaf[439130]:         at org.jupnp.protocol.ReceivingAsync.run(ReceivingAsync.java:71)
Sep 11 20:33:56 openhabdeb karaf[439130]:         ... 3 more
Sep 11 20:34:04 openhabdeb systemd[1]: openhab.service: Deactivated successfully.
Sep 11 20:34:04 openhabdeb systemd[1]: Stopped openhab.service - openHAB - empowering the smart home.
Sep 11 20:34:04 openhabdeb systemd[1]: openhab.service: Consumed 2min 7.902s CPU time.
Sep 11 20:34:04 openhabdeb systemd[1]: Starting openhab.service - openHAB - empowering the smart home...
Sep 11 20:34:04 openhabdeb systemd[1]: Started openhab.service - openHAB - empowering the smart home.
Sep 11 20:37:43 openhabdeb systemd[1]: Stopping openhab.service - openHAB - empowering the smart home...
Sep 11 20:37:51 openhabdeb systemd[1]: openhab.service: Deactivated successfully.
Sep 11 20:37:51 openhabdeb systemd[1]: Stopped openhab.service - openHAB - empowering the smart home.
Sep 11 20:37:51 openhabdeb systemd[1]: openhab.service: Consumed 1min 16.641s CPU time.
-- Boot 7001b37744ea40b596a1a749510682fe --
Sep 11 20:38:21 openhabdeb systemd[1]: Starting openhab.service - openHAB - empowering the smart home...
Sep 11 20:38:21 openhabdeb systemd[1]: Started openhab.service - openHAB - empowering the smart home.
Sep 11 22:06:15 openhabdeb systemd[1]: Stopping openhab.service - openHAB - empowering the smart home...
Sep 11 22:06:23 openhabdeb systemd[1]: openhab.service: Deactivated successfully.
Sep 11 22:06:23 openhabdeb systemd[1]: Stopped openhab.service - openHAB - empowering the smart home.
Sep 11 22:06:23 openhabdeb systemd[1]: openhab.service: Consumed 3min 18.019s CPU time.
Sep 11 22:06:23 openhabdeb systemd[1]: Starting openhab.service - openHAB - empowering the smart home...
Sep 11 22:06:23 openhabdeb systemd[1]: Started openhab.service - openHAB - empowering the smart home.
openhab.log
penhabian@openhabdeb:~$ cat  /var/log/openhab/openhab.log
2025-09-11 22:06:31.252 [INFO ] [org.openhab.core.Activator          ] - Starting openHAB 5.0.1 (Release Build)
2025-09-11 22:06:32.435 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Amsterdam'.
2025-09-11 22:06:32.444 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to '51.363858998108896,6.128619312985394'.
2025-09-11 22:06:32.452 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_NL'.
2025-09-11 22:06:34.884 [WARN ] [.transport.servlet.ServletController] - Can't find the request for http://openhabdeb.familie-dokter.lan:8080/rest/events's Observer 
2025-09-11 22:06:39.577 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Voordeur_LowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.580 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_Dimmer_Woonkamer_Haldeur_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.582 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Voordeur_KeypadLowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.584 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_dimmer_switch_Hal_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.589 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_Dimmer_Overloop_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.596 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Achterdeur_LowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:39.598 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Josha_dimmer_switch_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:06:40.967 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-09-11 22:06:41.237 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'assistant.rules'
2025-09-11 22:06:42.399 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'miniswitch.rules'
2025-09-11 22:06:42.594 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'huedimmer.rules'
2025-09-11 22:06:43.834 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'bel.rules'
2025-09-11 22:06:44.116 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'yamaha.rules'
2025-09-11 22:06:44.729 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: a091a093-2b3c-4a90-acf6-cbfa7460e6d7
2025-09-11 22:06:44.732 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: a0fd11f4-cae3-42f5-be64-3b19c20785e0
2025-09-11 22:06:44.733 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: be5449d7-7227-43d2-b483-0134ca41220b
2025-09-11 22:06:44.735 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: 6f7fa381-b1cb-4e34-9570-baaaf6d2328c
2025-09-11 22:06:47.030 [WARN ] [ty.util.ssl.SslContextFactory.config] - Trusting all certificates configured for Client@2566f725[provider=null,keyStore=null,trustStore=null]
2025-09-11 22:06:47.031 [WARN ] [ty.util.ssl.SslContextFactory.config] - No Client EndPointIdentificationAlgorithm configured for Client@2566f725[provider=null,keyStore=null,trustStore=null]
2025-09-11 22:06:52.897 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = 94...db, base URL = http://localhost:8080)
2025-09-11 22:06:52.976 [INFO ] [.influxdb.InfluxDBPersistenceService] - InfluxDB persistence service started.
2025-09-11 22:07:35.870 [WARN ] [core.karaf.internal.FeatureInstaller] - The binding add-on 'philipsair' does not exist - ignoring it.
Java version
openhabian@openhabdeb:~$ java -version
openjdk version "21.0.8" 2025-07-15 LTS
OpenJDK Runtime Environment Temurin-21.0.8+9 (build 21.0.8+9-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.8+9 (build 21.0.8+9-LTS, mixed mode, sharing)
1 Like

Please use code fences when postiong logs and code.

```
code goes here
```

For code, the white space can be meaningful. For logs it’s a ton easier to read.

When OH is upgraded, the cache gets cleared. When the cache gets cleared, all the add-ons need to be redownloaded and reinstalled. Thisa can take some time.

Usually the first start of OH after an upgrade will be filled with errors because OH starts up and tries to start using stuff (Things, rules) for which the add-on is not yet been installed.

The best procedure is to wait until things settle down after that first boot. Then restart openHAB. In otherwords, ignore the errors until the add-ons get installed and then restart which should be clean.

In this log, as best as I can read it (see code fences discussion above) you have a few errors in your semantic model which you can ignore for now.

The errors from the ScriptEngine come from the cast that JS Scripting isnt’ installed yet.

Eventually we see that InfluxDB comes online so at least that add-on has finally been installed.

There’s a warning about the philpsair add-on not existing. I’m not sure what that bindign does or why it doesn’t exist, but that shouldn’t prevent OH from installing the rest of the add-ons. If there is an error installing the add-ons it’s probably going to be after these logs.

I see I used the code fences for all info except for the log, so fixed that.
I will leave openhab running and have a look tomorrow morning..

Just woke up. After a 9hrs wait OH5 is still not working.

There was one line added to the log (after about 8 hours of nothing)
WebSocket error: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms

Full log:

openhabian@openhabdeb:~$ cat /var/log/openhab/openhab.log
2025-09-11 22:32:15.311 [INFO ] [org.openhab.core.Activator          ] - Starting openHAB 5.0.1 (Release Build)
2025-09-11 22:32:15.982 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Amsterdam'.
2025-09-11 22:32:15.986 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to '51.363858998108896,6.128619312985394'.
2025-09-11 22:32:15.986 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_NL'.
2025-09-11 22:32:23.179 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Voordeur_LowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.181 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_Dimmer_Woonkamer_Haldeur_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.181 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Voordeur_KeypadLowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.182 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_dimmer_switch_Hal_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.183 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Hue_Dimmer_Overloop_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.185 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Nuki_Achterdeur_LowBattery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:23.191 [WARN ] [antics.internal.SemanticsServiceImpl] - Item 'Josha_dimmer_switch_Low_Battery' (Point): Invalid combination of semantic tags: Energy (Property) and LowBattery (Property). Only one Point and optionally one Property tag may be assigned.
2025-09-11 22:32:24.420 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-09-11 22:32:24.544 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'assistant.rules'
2025-09-11 22:32:25.923 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'miniswitch.rules'
2025-09-11 22:32:26.112 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'huedimmer.rules'
2025-09-11 22:32:27.579 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'bel.rules'
2025-09-11 22:32:27.880 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'yamaha.rules'
2025-09-11 22:32:28.521 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: ea6a69b8-981e-4a3a-a886-a6d65238a837
2025-09-11 22:32:28.524 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: 04468923-8337-4b9f-af9c-7bf309214e40
2025-09-11 22:32:28.526 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: 00de421a-f167-4002-b060-9689630deb8e
2025-09-11 22:32:28.529 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript' could not be found for identifier: 74e7c61d-0ab3-4917-8a0c-97707a910dc4
2025-09-11 22:32:30.735 [WARN ] [ty.util.ssl.SslContextFactory.config] - Trusting all certificates configured for Client@639dbd64[provider=null,keyStore=null,trustStore=null]
2025-09-11 22:32:30.735 [WARN ] [ty.util.ssl.SslContextFactory.config] - No Client EndPointIdentificationAlgorithm configured for Client@639dbd64[provider=null,keyStore=null,trustStore=null]
2025-09-11 22:32:36.592 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = 94...db, base URL = http://localhost:8080)
2025-09-11 22:32:36.651 [INFO ] [.influxdb.InfluxDBPersistenceService] - InfluxDB persistence service started.
2025-09-11 22:33:19.572 [WARN ] [core.karaf.internal.FeatureInstaller] - The binding add-on 'philipsair' does not exist - ignoring it.
2025-09-12 06:13:47.837 [INFO ] [b.core.io.websocket.log.LogWebSocket] - WebSocket error: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms

I logged into the openhab console to have a look at the add-ons (as that is what you are referring to in your reply @rlkoshak. I saw that some bundles were active, but some have status “Resolved”. I restarted those (bundle:restart 311 313...) and that brought some live back into OH!

Unfortunately, after restarting the openhab service, I go back to the same issue. I restarted the add-ons 1 by 1 to see if i could find which one is the culprit. But only after restarting all of them, OH will start running normally. So still mot out of the woods..

openhab> bundle:list| grep -v Active
START LEVEL 100 , List Threshold: 50
 ID │ State    │ Lvl │ Version               │ Name
────┼──────────┼─────┼───────────────────────┼──────────────────────────────────────────────────────────
253 │ Resolved │  80 │ 1.2.18                │ jffi, Hosts: 252
311 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Automation :: JavaScript S
313 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Bosch Smart Home Binding
314 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Chromecast Binding
317 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Home Connect Binding
318 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: HTTP Binding
322 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Millheat Binding
324 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Awtrix 3
325 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT EspMilightHub
326 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT FPP
327 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Things and Channels
328 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT HomeAssistant Convent
329 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Homie Convention
330 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Ruuvi Gateway
333 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Pushover Binding
334 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Remote openHAB Binding
335 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: SolarEdge Binding
341 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: ZigBee Console Ember
342 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
360 │ Resolved │  80 │ 5.0.1                 │ openHAB Core :: Bundles :: Configuration Serial
368 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Persistence Service :: RRD

I had a couple of health issues mentioned in my OH interface. For which I edited the items mentioned in the health issue (Semantic Property was both Energy & Low Battery) once I fixed all of those openhab seems to work a bit bette, even after a restart.

Can’t reproduce the exact error and error situation as OH5 will not allow me to select both Semantic Properties again.
But still some bundles will not become active (and it shows in the UI (handler missing):

openhab> bundle:list| grep -v Active
START LEVEL 100 , List Threshold: 50
 ID │ State    │ Lvl │ Version               │ Name
────┼──────────┼─────┼───────────────────────┼──────────────────────────────────────────────────────────
253 │ Resolved │  80 │ 1.2.18                │ jffi, Hosts: 252
317 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Home Connect Binding
318 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: HTTP Binding
322 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Millheat Binding
324 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Awtrix 3
325 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT EspMilightHub
326 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT FPP
327 │ Resolved │  81 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Things and Channels
328 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT HomeAssistant Convent
329 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Homie Convention
330 │ Resolved │  82 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: MQTT Ruuvi Gateway
333 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: Pushover Binding
335 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: SolarEdge Binding
341 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: ZigBee Console Ember
342 │ Resolved │  80 │ 5.0.1                 │ openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
360 │ Resolved │  80 │ 5.0.1                 │ openHAB Core :: Bundles :: Configuration Serial

The semantic tags on the Items is not related to the bundles issue.

I’m not sure where to go from here. A first thing to try is clearing the cache. Again, same as with an upgrade, that first start of OH after clearing the cache will show errors as OH tries to use bundles that are not yet installed. Waiting five minutes or so should be sufficient and then restart OH and see if this resolves anything.

That warning about the philipsair might be relevant. If ythe above doesn’t resolve the issue, try removing this add-on and restarting or clearing the cache again after removing.

Cleaning the cache did the trick!

That philipsair add-on has me confused (as I did indeed use that in version 4 (or3). I can’t seem to find it anywhere in the config or in the UI, so can’t remove it, as it is not there.

Anyway, cleaning the cache, solved the issue.

Now on to the issue that I hoped upgrading would solve: connecting my new Hue Bridge Pro to openhab…

Thanks @rlkoshak !