Part of downgrading was that I needed to access scripts and rules to do another backup method. I can reconstruct most of my OH setup via the REST api, so if I retrieve the needed data I will have another go at 5.2
Since oh5.2 systeminfo binding never gets online
in the logs I only see
xxx [TRACE] [o.internal.handler.SystemInfoHandler] - Initializing thing systeminfo_smarthome with thing type computer
xxx [TRACE] [o.internal.handler.SystemInfoHandler] - Restoring channel configurations
xxx [DEBUG] [eminfo.internal.model.OSHISystemInfo] - OSHISystemInfo service starts initializing
xxx [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing 'systeminfo:computer:systeminfo_smarthome' takes more than 5000ms.
see here
I have been testing for the last couple of days, and I am happy to report that 5.2 is behaving very well. All the scripts/rules, widgets, and addons are working perfectly.
The only issue is again with the Tuya binding. The cloud project connects and then disconnects again (around every 5 minutes). The sensor, though, once online, is sending updates nevertheless (which is good).
The cloud project gives an invalid token error
but then comes up again and sensor data is flowing. debug logs not showing beyond what is shared.
I looked into the ports. The tuya items as opposed to the binding have not the ports exposed. I checked other bindings/items there is not conflict. Changing the default port actually disconnects the connection to the items. Noting this worked perfectly on 5.1.1 with the ports fixed to the default.
How can I continue debugging the binding (maybe not on this forum) so we get the fix in the next release?
Have a good weekend
Espresso
Following up my previous issues, this post outlines the exact problem:
https://community.openhab.org/t/no-login-to-webui-after-upgrade-5-0-3-5-1-0/167692/11
My items are now updating as well, perhaps the authorisation issue was simply not allowing the webpage access to items.
If you had implicit user turned off, nothing will update, because the SSE connections wonât be allowed to be established. Thereâs a bug that makes them not authenticate even when they should, and until the bugfix is released, you will get no updated with the implicit user off, and you wonât get a logic screen when trying to enter MainUI if youâre not already logged in - just a blank screen. Enabling the implicit user solves both.
Iâd suggest opening an issue on github openhab-addons repo
The upgrade to OH 5-2-0 went almost without a hitch.
These are the topics that did not work:
- Some chart pages did not display any data. I found out that the chart series configuaration just showed the label of the item but the item was not linked any more to the series.
After configuring the items again for each series it was ok. - I could not search for market place widgets via Addon-Store/UI any more. Also I got a âwidget not foundâ error for one of my marketplace widgets (garbage list).
After waiting a few hours (or because of getting to runlevel 100??) the marketplace widgets are shown again and I could reinstall the missing widget. - In the WLED binding the segments did not come online, see [wled] Cannot invoke "java.util.List.iterator()" because "this.state.jsonResponse.palettes" is null · Issue #21215 · openhab/openhab-addons · GitHub
BTW: Thanks to all the contributors of OH!
I am using OpenHab 5.2.0 on Windows 11. The use of Dimensionless + unit % (e.g. for humidity) is problematic. With this setting, dynamic icons stop working (not even the default icon is displayed). The error â2026-07-21 12:18:04.601 [WARN ] [org.eclipse.jetty.server.HttpChannel] - handleException /icon/humidity org.eclipse.jetty.http.BadMessageException: 400: Unable to parse URI queryâ appears in the log. In other cases, dynamic icons work.
Hi,
On a page (/settings/pages/layout/overview), context can no longer be given via the UI for a rule. It is currently necessary to insert this manually via YAML (actionRuleContext).
Tested with component: oh-label-cell, oh-cell and oh-list-item; OH 5.2.0 and
5.3.0-snapshot; different Browsers
Can you give a slightly more in-depth explanation, perhaps with some sample YAML to reproduce the problem?
Gladly. actionRuleContext was inserted via YAML. Inserting and editing in the UI (Cell Setting) was not possible.
component: oh-cell
config:
title: Test
action:
- rule
actionRule: Wake_on_Lan
actionRuleContext:
Thing: network:pingdevice:Rechner_Ping
E: In the browser console there is an error message as soon as âEdit Scriptâ or the square is clicked
index-DDkq2neh.js:17617 App initialization: 13.70 ms
rc2Contentscript.js:1 Uncaught SyntaxError: Identifier 'intermediateBody' has already been declared (at rc2Contentscript.js:1:1)
jquery.js:2 Error: <path> attribute d: Expected number, "⊠tc0.2,0,0.4-0.2,0âŠ".
xe @ jquery.js:2
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
Loading the font '<URL>' violates the following Content Security Policy directive: "font-src 'self' data:". The action has been blocked.
overview/:1 Uncaught (in promise) SecurityError: Failed to register a ServiceWorker for scope ('https://192.168.178.91:8443/') with script ('https://192.168.178.91:8443/sw.js'): An SSL certificate error occurred when fetching the script.
index-DDkq2neh.js:16546 Day.js locale set to de
index-DDkq2neh.js:16550 Init data loading: 226.60 ms
useWidgetAction-BQBVbTkY.js:937 Opening external URL https://192.168.178.50:8442/
toolbarContentscript.js:113 {"message":"A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received"}
overview/:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
useWidgetAction-BQBVbTkY.js:937 Opening external URL https://community.openhab.org/latest
overview/:1 Loading the stylesheet 'https://fonts.googleapis.com/css?family=Open+Sans&display=swap' violates the following Content Security Policy directive: "default-src 'self' 'unsafe-inline' 'unsafe-eval'". Note that 'style-src-elem' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.
Node cannot be found in the current page.
widget-config-popup-Cfhju3RC.js:188 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
enableMovablePopup @ widget-config-popup-Cfhju3RC.js:188
(anonymous) @ widget-config-popup-Cfhju3RC.js:181
widget-config-popup-Cfhju3RC.js:188 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
enableMovablePopup @ widget-config-popup-Cfhju3RC.js:188
(anonymous) @ widget-config-popup-Cfhju3RC.js:181
vue.runtime.esm-bundler-BusZxOMj.js:952 TypeError: Cannot read properties of undefined (reading 'navigate')
at Proxy.openPopup (config-parameter-COs2T-n2.js:362:23)
at a.onClick.t2.<computed> (config-parameter-COs2T-n2.js:394:43)
at In (vue.runtime.esm-bundler-BusZxOMj.js:914:17)
at z (vue.runtime.esm-bundler-BusZxOMj.js:921:14)
at HTMLAnchorElement.n2 (vue.runtime.esm-bundler-BusZxOMj.js:3415:5)
Rn @ vue.runtime.esm-bundler-BusZxOMj.js:952
Ln @ vue.runtime.esm-bundler-BusZxOMj.js:948
In @ vue.runtime.esm-bundler-BusZxOMj.js:916
z @ vue.runtime.esm-bundler-BusZxOMj.js:921
n2 @ vue.runtime.esm-bundler-BusZxOMj.js:3415
I upgraded today my OH from 5.1.3 to 5.2.0 and now Iâm having some problems with the android app. I can connect to OH5.2 without any issues when my phone is connected to our internal wifi but when I try to connect e.g. from a mobile network I get an SSL error.
I have also tried to use the certificate which the android app proposes (com.samsung.euicc_ds) but this doesnât help.
I have used URL https://xxx.no-ip.com:10000 since OH3 without any issues but this doesnât seem to work under OH5.2.
Can you expand on this part, specifically on how the app supposedly proposes a certificate? I donât think it actually does that.
Since 5.2.0 sitemaps have their own menu item, but in the developer sidebar sitemaps are listed under pages.
If I want to edit one listed sitemap and click the pencil icon I get the error Unknown page type. Check the `component` of your page definition.
Is this a bug and should I define an issue?
Iâm not entirely sure, but I guess what happens there is that myOH offers client certificate authentication, and your phone subsequently asks you to choose a certificate for doing so, but the only available certificate is the eSIM one. Does choosing cancel on that dialog get you further?
Nope, after clicking cancel I get the same error message as in my first post. Something wrong with SSL.
Yes, this was overlooked when moving sitemaps out of pages. Please create an issue.