The issue should have been in the webui repo. A PR to fix this has been created: Fix sitemaps in developer sidebar by mherwege Ā· Pull Request #4397 Ā· openhab/openhab-webui Ā· GitHub
My mistake 
- I should have thought of that, since itās not a sitemap error but a Main UI error.
I have now some problems with Javascript scripting addon because itās status seems to be āwaitingā and it still has the same status when I type command
bundle:restart 338
This problem affects the Entsoe binding because my ECMA script transformation is not working (see discussion Entsoe Binding - #31 by jlikonen).
I have tried to uninstall JavaScript Scripting addon and reinstall it but this hasnāt helped.
Below is a copy extracted from the log-file:
2026-07-27 07:34:34.706 [ERROR] [.internal.GraalJSScriptEngineFactory] - bundle org.openhab.automation.jsscripting:5.2.0 (338)[org.openhab.automation.jsscripting.internal.GraalJSScriptEngineFactory(463)] : Error during instantiation of the implementation object
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:74)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
at org.apache.felix.scr.impl.inject.internal.ComponentConstructorImpl.newInstance(ComponentConstructorImpl.java:326)
at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:286)
at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115)
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:1001)
at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:974)
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:919)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:220)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:217)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:118)
at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:547)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:534)
at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:660)
at org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:88)
at org.apache.felix.scr.impl.inject.methods.BindMethod.getServiceObject(BindMethod.java:669)
at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2625)
at org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:2091)
at org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:2074)
at org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:442)
at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:337)
at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:304)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1232)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1152)
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:959)
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:895)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1184)
at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:118)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:123)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:961)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:937)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:874)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:141)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:262)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:500)
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:931)
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:917)
at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:133)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:986)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:754)
at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1287)
at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1238)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1232)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1152)
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:959)
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:895)
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1184)
at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:118)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:123)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:961)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:937)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:874)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:141)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:262)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:500)
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:931)
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:917)
at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:133)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:986)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:754)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:676)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:439)
at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:671)
at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:341)
at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:610)
at org.apache.felix.scr.impl.Activator.access$200(Activator.java:75)
at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:477)
at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196)
at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169)
at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:488)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:420)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232)
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:949)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:229)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:138)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:130)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:217)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:499)
at org.eclipse.osgi.container.Module.start(Module.java:486)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
Caused by: java.lang.IllegalStateException: No language and polyglot implementation was found on the module-path. Make sure at last one language is added to the module-path.
at org.graalvm.polyglot.Engine$PolyglotInvalid.noPolyglotImplementationFound(Engine.java:2000)
at org.graalvm.polyglot.Engine$PolyglotInvalid.createHostAccess(Engine.java:1991)
at org.graalvm.polyglot.Engine$PolyglotInvalid.createHostAccess(Engine.java:1953)
at org.graalvm.polyglot.Engine$Builder.build(Engine.java:844)
at org.openhab.automation.jsscripting.internal.GraalJSScriptEngineFactory.<init>(GraalJSScriptEngineFactory.java:115)
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
... 98 more
Any ideas?
Looks like a download issue.
Can you install the openhab-addons package if you are on Linux package install?
Iām running OH5.2 under Win11 box, not under Linux. I copied the kar file to addons folder and restarted OH but the status of the JavaScript Scripting addon is still āwaitingā.
I managed to sort out this problem by reinstalling OH5.2.0.
I finally took the time to upgrade. I was still on 4.3.9, but yesterday did a one step upgrade to 5.2.0. Reading the breaking changes (also the intermediate ones for 5.0 and 5.1), I was prepared. The breaking changes were only little.
Last January I already reinstalled my Pi4, as back in 2021 I apparently installed a 32 bit debian i.s.o the 64 bit. With java 21 required for OH5, I had to prepare for the future. Now with testing of bindings on a VM, there was no more reason to defer upgrading.
The upgrade went smooth and only had to repair two minor issues:
Some of my DSL rules that took
Item1.sendCommand(item2.state)
as a valid command in 4.3 (both items defined as String type), did not work in 5.2. Had to change it to
Item1.sendCommand(item2.state.toString)
to make it work.
Also my (five) apple Homekit items were recreated in Homekit and no longer linked to Homekit automations and assigned to the default Homekit room. As two of thos items are used for presence detection by Homekit, my presence automations no longer functioned. But again, that was a matter of relinking in Homekit.
Overall: great job on system stability and very little breaking changes (but I was prepared for them anyway).
Thanks and kudos to the developer team and the binding developers!
After upgrading from openHAB 5.1.3 to 5.2.0 I have a reproducible problem with the MainUI when accessing it via myopenHAB.
Findings:
-
Local MainUI (
http://<local-ip>:8080/overview/) works perfectly. -
MainUI via
connect.myopenhab.orgoften shows a blank page (sometimes partially rendered). -
Sitemaps via myopenHAB work.
-
Push notifications work.
-
The failing JavaScript module changes on every reload.
-
Browser console reports:
Failed to load module script:
Expected a JavaScript module script but the server responded with aMIME type of āā.
Looking into Chrome DevTools shows:
- HTTP 200 OK
- empty response body (~0.3 kB transferred)
- no
Content-Typeheader on the failing requests Transfer-Encoding: chunked- disabling browser cache and disabling the Service Worker makes no difference.
Has anyone seen this after upgrading to 5.2.0, or is there anything else I could check?
After installation of 5.2 my Zigbee controller, Zigbee extender, various Zigbee devices (sockets & LED controllers) have all come back online and are behaving as expected. However I have 20 window/door sensors (all the same type of sensor) and these are reporting as āOfflineā. I have tried ātriggeringā the devices that are offline (i.e. opening and closing the window / door) but this has not changed the status of the devices. All of these were working and reporting battery level / battery voltage / contact status / etc before the upgrade.
I have stopped the OpenHAB service, cleared the cache, and waited for a considerable amount of time after restarting but the devices have still not yet come āOnlineā. Donāt know if itās relevant but Iām running OpenHAB 5.2.0 Release Built on a Raspberry Pi:
###############################################################################
############### openhabian ##################################################
###############################################################################
## Ip = 192.168.100.20
## Release = Debian GNU/Linux 12 (bookworm)
## Kernel = Linux 6.12.47+rpt-rpi-v8
## Platform = BCM43455 37.4MHz Raspberry Pi 3+-0190
## Uptime = 0 day(s). 03:52:32
## CPU Usage = 66.21% avg over 4 cpu(s) ( core(s) x - socket(s))
## CPU Load = 1m: 5.49, 5m: 5.35, 15m: 4.37
## Memory = Free: 0.04GB (1%), Used: 3.78GB (99%), Total: 3.75GB
## Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
## Root = Free: 18.94GB (69%), Used: 8.28GB (31%), Total: 28.70GB
## Updates = 0 apt updates available.
## Sessions = 1 session(s)
## Processes = 148 running processes of 4194304 maximum processes
###############################################################################
Upgrade was done (as always) via the openhab-config utility.
Anyone else having / seeing similar issues or has any suggestions? Many thanks.
I have resolved the situation.
I had to remove each thing one by one, then rescan. Device was picked up immediately when re-scanned after removal. As I added with the same Thing name all the existing Items just started working.
Upgraded, no big issues. The most annoying is widget variables taking up to 3 (data) refreshes before showing the values. The slowest takes about 10 minutes to display correct.
And a white line on top of my dashboard but a breaking change in the sizing was announced so expected and I have to look into that.
Edit: According to internet the line is a combination of a chrome bug and the website behaviour. But the tip was ā¦ Turn the device to dark mode. This makes the line black so you donāt see it. Perfect workaround!
All in all, great work (as usual) 
After upgrading to 5.2.1 (Docker install), my installation is still quite broken - same as with 5.2.0. The last working version for me is 5.2.0.M4.
At startup, I get the following logs:
2026-08-02 21:33:09.737 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading DSL model 'upb.rules'
2026-08-02 21:33:10.384 [WARN ] [e.internal.VoiceManagerConfiguration] - No configuration description found for system:voice, unable to apply defaults!
2026-08-02 21:33:10.489 [ERROR] [Events.Framework ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.mqtt.frigatesvr [250]
Unresolved requirement: Import-Package: org.openhab.binding.mqtt.handler
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
2026-08-02 21:33:10.493 [ERROR] [Events.Framework ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: no.seime.openhab.binding.esphome [251]
Unresolved requirement: Import-Package: org.openhab.binding.bluetooth
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
2026-08-02 21:33:16.572 [ERROR] [.handler.AbstractScriptModuleHandler] - Script execution of rule with UID 'startup-1' failed: 'sendMail' is not a member of 'org.openhab.core.thing.binding.ThingAct
ions'; line 6, column 3, length 74 in startup
2026-08-02 21:33:16.573 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2026-08-02 21:33:32.408 [WARN ] [.transform.util.ItemDisplayStateUtil] - Failed transforming the state 'NULL' on item 'SecondFloor_Tstat_OpMode' with pattern 'MAP(ct100-mode.map):%s': Transformatio
n service of type 'MAP' is not available.
2026-08-02 21:33:32.408 [WARN ] [.transform.util.ItemDisplayStateUtil] - Failed transforming the state 'NULL' on item 'FirstFloor_Tstat_OpMode' with pattern 'MAP(ct100-mode.map):%s': Transformation
service of type 'MAP' is not available.
2026-08-02 21:33:32.409 [WARN ] [.transform.util.ItemDisplayStateUtil] - Failed transforming the state 'NULL' on item 'Basement_Tstat_OpMode' with pattern 'MAP(ct100-mode.map):%s': Transformation s
ervice of type 'MAP' is not available.
So basic addons that should have been included are not loaded: mqtt, bluetooth, JS transform. This breaks all my rules and a lot of bindings, although the Web UI and other bindings appear to continue to work.
openhab 5.2.1 installed over 5.2.0 all good. I did have to start openhab twice but it was ok after the second time.
Thanks
No release notes or announcement about 5.2.1? Did it slip out before it was meant to?
The patch release announcement is here: openHAB 5.2 has landed! - #8 by Kai
It always comes only after the release is made available. 
I think the org.openhab.binding.mqtt.frigatesvr binding is causing your issues. Probably a custom (not shipped) jar that is not updated as it fails to install dependencyās.
If you remove the jar from the addons folder openHAB should start as expected.
You can get more support here: New comprehensive Frigate binding - #128 by Stepko
Updating from 5.2.0 to 5.2.1 in the Docker container on my Synology NAS went smoothly. The only thing I had to install manually afterwards was the Signal binding from the Marketplace.
Many thanks to all.
After updating from 5.2.0 to 5.2.1 the Matter Controller Thing is stucked in INITIALIZING. The Matter Bridge is in state STOPPED.
I tried: disabling/reenabling the Matter Controller Thing, restarting the Matter binding, restarting openHAB, restarting the server, uninstalling/reinstalling the Matter binding, nothing helped.
Going back to 5.2.0 solved the issue, everything is working again.
Trace log after restarting the Matter binding on 5.2.1:
Just for your information.
Hereās still 5.2.0 offered:
https://www.openhab.org/download/
For the time being I guess it should be 5.2.1