This topic can be used to discuss problems/experiences/questions on the openHAB 4.3 release as announced in this topic.
Upgraded from 4.2.3-1 with no issues.
Everything seems to work.
Big thank you to all involved.
Well done as usual.
Same here, only had a to correct The DateTimeType methods, which is named in the release notes.
Thanks to all for this release
I use OpenHAB with the EnOcean binding (USB300 Dongle, FSB14). Unfortunately, after the update to 4.3, nothing works anymore.
So far I donāt see any errors in the log, just that the thing is no longer online also after restart. NOT_YET_READY in status thing USB300.
Iāll have to investigate it further. Maybe someone can let me know if it works for them.
My EnOcean binding setup still works. But my Eltako units are connected to openHAB via FGW14-USB.
I donāt get the log to workā¦
Also, if I press āPlayā, nothing happensā¦ I donāt think there is documentation about the UI Log; if there is, I missed it and will be happy with a link, of course.
Can you please provide some information about your client as well as which protocol (http or https) you use or whether you use a reverse proxy?
Mmm, Iām afraid I canātā¦ Just out-of-the-box stuff.
Do you mean that Iām using an Android phone and thus the Android app? Via https://home.myopenhab.org.
When logged in into the UI, go to the about page, expand technical information and click on show details.
Copy it and PM me on the community.
Please also PM me whether the server URL in the Android app settings starts with HTTP or HTTPS.
Maybe your server is not logging a lot and you have not wait enough to get first logs?
Because old logs are not shown.
But should nothing happen when I click on Play? Anyway, I left the window open for 10 minutes, and nothing got logged. When I ātailā the logs through the CLI, thereās a log entry every 10 seconds, mostly.
It is not just no logs to display. The play button will be disabled, and the stop/pause buttons enabled if the websocket connection is made. So there is some sort of underlying network issue.
I assume youāre on the same network - ie youāre not using OH cloud?
Mmm, looks like I am. Which is good when Iām not home, but redundant when I am home. But I assume thereās no way to differentiate like that?
Iām not familiar with the Android app, but the iOS app will (or should) select the local network if available, and the cloud connector if the direct local connection is not available. The logger will currently only work if youāre on the same local network as your OH server - I think the cloud connector doesnāt provide websockets services at this stage.
Hi,
updated yesterday from 4.2.2 to 4.3.0. After restart, everything came up flawless. Just minor warning regarding deprecated getZonedDateTime in my rules, fixed that using getInstant as discussed in another thread here.
Thanks for your dedication and awesome work. Merry Christmas
Same problem on my side. No logging.
Just a question regarding upcoming OH 5.
I will upgrade to a Raspberry Pi 5 and openhabian soon.
Is the current openhabian version (1.93 64-Bit Release) based on bullseye or bookworm?
Upgrade went fine, but all existing ECMA 2021 scripts donāt run.
Creating a new ECMA 2021 script action in the rule and coping the code makes it runnable again. Seems to be an error in the migration. The type is changed from 4.2.x to 4.3 and OH doesnāt recognize it anymore. So probably the easy fix is changing the header.
edit: yes, removing the ā;version=ECMAScript-2021ā in the code tab also fixes the issue.
4.2.x ECMA 2021 script action header:
actions:
- inputs: {}
id: "4"
configuration:
type: application/javascript;version=ECMAScript-2021
script: >-
4.3 ECMA 2021 script action header:
- inputs: {}
id: "7"
configuration:
type: application/javascript
script: >-
Thanks for the new Release! Great!
Is it just me - Go to āSettingsā ā āThingsā and then to an Generic MQTT Thing and try to display / change it. But now I only can copy and delete, I cannot see all the details, items or code and make any changes. I deleted browser cache & cookies already, also disabling / enabling the Thing is not helping. It is generic MQTT, not the HomeAssistant MQTT.
As I understand in the openHABian part of the blog post it is āmove to a Bullseye-based Linux distributionā.