openHAB 3.1 Release discussion

[elcosomalo (El coso)]

I managed to fix my problem by uninstalling some dependencies stated in the Sony TV binding thread. It was this binding after all.
OH 3.1.0 is working now.

Check my post there if you are having issues like mine:

Sony Devices Binding

In case this helps anyone out there: I updated to OH 3.1.0 stable and had problems, things where not showing up. Long story short, some dependencies of this binding where causing havoc on the new OH version. Here is how I fixed it: 1- in karaf UNINSTALL all the dependencies stated in the OP and ONLY LEAVE THESE ONES: feature:install openhab-transport-upnp feature:install openhab-transformation-map 2 - Then I deleted the userdata/sony directory 3 - Also deleted the JSON in the addons direc…

[MrHenky93]

I seem to have this same issue with my Denon X2300W receiver. Wasn’t sure whether the upgrade to OH 3.1 was to blame or the recent firmware update I did on the Denon.

Keep me in the loop on this one if you will

[milo (M)]

Hello,

I found another issue. I needed to add/download the additional add-ons which are not in the official addon repo again into the addon folder. Otherwise they won’t recognized. In the milestone builds this was not an issue.

[NCO (E. Gerland)]

Sure - I will - as soon as I find out what’s causing it.
It seems that more than just the channels above are not updated properly.

[NCO (E. Gerland)]

@DOliana

I know I should avoid startup rules

Really?
Why is that?
I use start up rules as well and I am pretty happy with it.
(Although on openhab 3.0.2 system started as a trigger did not work)

[djpsycho82 (Jeroen de Vries)]

Same problems here, i didn’t find any topic about this so created this one:

DenonMarantz Binding broken after update to OH3.1

Hi Guys, I saw a post in the OH3.1 thread about problems with the DenonMarantz binding. I have the same problem which is: The items are not updated with the status of the receiver > Change volume on the receiver and the item ‘denonVolume’ doesn’t update. The other way around works, so when I send 40 to the denonVolume item, the receiver sets the volume to 40. Hope someone has a solution! Restarting the binding doesn’t solve the problem but gives an error in the log, maybe due to the java u…

[DOliana]

I cannot find the threads here in the forum right now, but afaik using startup text (DSL) rules should be avoided due to different issues that can come up. examples are timing or things like I am experiencing where builtin libraries are not loaded when the rule is executed (I had to introduce a sleep so that logInfo is available).
Another example: system started did work for me on OH 3.0.2…

[robr57 (Rob Roos)]

Florian, did you find a solution ? I get the same issue with OH 3.1
I searched all fora for openhab to find a solution, but nothing seems to work. The remark that we have to whitelist isnt explained either, the key question is which classes do exist and if needed to whitelist, how to do that.

Script execution of rule with UID ‘e475b81b79’ failed: org.graalvm.polyglot.PolyglotException: TypeError: Access to host class org.openhab.core. is not allowed or does not exist

I am trying to find a way to get javascript to execute the sendHttpPutRequest again…

[rossko57]

@DOliana

using startup text (DSL) rules should be avoided due

It’s not so much “should be avoided” as “limitations should be understood”. And yes, there can be timing issues in relation to other system services also starting up.
There’s no problem with self contained tasks like setting up some variables, or starting a timer for later actions.

[rlkoshak (Rich Koshak)]

@florian-h05

So how can I found out which aliases to use for what class?

The short answer here is that the new GraalVM JavaScript addon has almost nothing in common with the built in Nashorn JavaScript support. So pretty much everything is going to work differently. Unfortunately there are not a whole lot of examples of docs written for this add-on yet so your best bet will be to look at the README and actual code at GitHub - jpg0/ohj: Openhab Javascript Library for examples on how to use it.

As you figure it out I’m certain contributions to the docs would be most welcome.

@DOliana

I cannot find the threads here in the forum right now, but afaik using startup text (DSL) rules should be avoided due to different issues that can come up. examples are timing or things like I am experiencing where builtin libraries are not loaded when the rule is executed (I had to introduce a sleep so that logInfo is available).

Most of those issues were fixed in OH 3. OH 3 introduced startup levels which makes it possible to delay the execution of startup rules until the rest of OH is ready. However the way that system started rule triggers changed. In OH 2 when you reload a .rules file it will trigger the system started rules. That is not longer the case. Instead system started rules only run when the system started. If OH is already up and running and you load a .rules file, the system started rules will not trigger again because the system has already started.

There was an issue to add a new rule loaded trigger but I don’t know the status of that.

[Arno1st (Arnaud Gautier)]

Hi all,

I have just upgraded my OH 3.0.2 to the 3.1.0. Both on Docker through Synology.

Everything is OK except these two error lines (in ‘openhab.log’):

2021-07-04 20:42:29.452 [WARN ] [ty.util.ssl.SslContextFactory.config] - Trusting all certificates configured for Client@3f172cc3[provider=null,keyStore=null,trustStore=null]
2021-07-04 20:42:29.459 [WARN ] [ty.util.ssl.SslContextFactory.config] - No Client EndPointIdentificationAlgorithm configured for Client@3f172cc3[provider=null,keyStore=null,trustStore=null]

Is there a way to solve this problem?

I read some previous comments about the same problem but I did not find a solution.

Thanks a lot for your help.

Arnaud

[Wolfgang_S]

@Arno1st

Everything is OK except these two error lines (in ‘openhab.log’):
Is there a way to solve this problem?

They are warnings an can be ignored. See Some bindings give ssl warnings after 3.0.1.M3 (were ok in 3.0.1.M2) · Issue #10446 · openhab/openhab-addons · GitHub
You can filter them out by using an expression in the logging setup.

[florian-h05 (Florian H.)]

@robr57

@robr57

Florian, did you find a solution ? I get the same issue with OH 3.1

Sorry, but at the moment I have no idea of using the openHAB core actions.

I am only able to import the services which are pre-included in the Nashorn JavaScript support.

// import in Nashorn JS pre-included services
var { itemRegistry, things, rules, events, actions } = require('@runtime')

[roli (Andrej Rolih)]

I have an issue that appeared after upgrading to OH 3.1 (from 3.0) as well… Mainly my Z-Wave USB stick stopped working. And judging by the debug logs it seems to be a serial port issue:

2021-07-10 15:45:52.495 [DEBUG] [ort.serial.internal.RxTxPortProvider] - No SerialPortIdentifier found for: /dev/ttyACM0

It was working just fine with 3.0 for months and survived several minor upgrades, but not the 3.1 one. If anyone has any ideas, I have a thread open here:

Z-Wave USB stick not working after OH 3.1 update

Hi! I have an issue with my Aeotec gen 5 Z-wave stick which has stopped working after I upgraded from OH 3.0.x to 3.1 recently. And I need help getting it working again. Here is a debug log of the binding (and the serial binding) when I enable my z-wave thing: 2021-07-10 15:45:47.469 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:ebf2caa1 with scan time of 60 2021-07-10 15:45:47.475 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWa…

[BG56 (Bernhard Geis)]

I upgraded from OH3.0 to OH3.1. I didn’t see any error messages during the upgrade. Everything is working except the icons used on pages within cards are no longer displayed. These icons are stored in the folder /etc/openhab/html/icons (SMB share: \\openhab\openHAB-conf\html\icons ). It might be a problem with access rights or the OH build-in webserver. Any hints how to solve or analyse the problem?

I rebooted several times and checked the log.

The following warnings show up about 30s after the start:

2021-07-14 18:25:17.330 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to ‘Europe/Vienna’.
2021-07-14 18:25:17.367 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to ‘47.51782094289231,10.717695237253793’.
2021-07-14 18:25:17.370 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to ‘de_AT’.
2021-07-14 18:25:17.371 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to ‘SI’.
2021-07-14 18:25:25.142 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘SmartHome.items’
2021-07-14 18:25:26.340 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘rrd4j.persist’
2021-07-14 18:25:31.272 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2021-07-14 18:25:31.517 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘SmartHome.rules’
2021-07-14 18:25:41.900 [INFO ] [org.openhab.ui.internal.UIService ] - Started UI on port 8080

2021-07-14 18:25:45.389 [WARN ] [ty.util.ssl.SslContextFactory.config] - Trusting all certificates configured for Client@19e4d10[provider=null,keyStore=null,trustStore=null]
2021-07-14 18:25:45.391 [WARN ] [ty.util.ssl.SslContextFactory.config] - No Client EndPointIdentificationAlgorithm configured for Client@19e4d10[provider=null,keyStore=null,trustStore=null]

I don’t know if these warnings are indicators of a authentication problem. Any idea how to solve that?
This behavior started after the upgrade from 3.0 to 3.1 without any other change. Same problem on Windows PC Web-Browser and Android App on two tablets. I run openhabian on PI4.
Your help is very much appreciated.

[denisdmenace (Denis)]

3.1.0 Release version spawned a terminal error list so I reverted back to 3.1.0-M4 because I didn’t trust it. 3.1.0-M4 has always had an error free terminal window,
I did a logout/startup of the new OH a few times but it still generated this error list in the terminal.
Screen shots of terminal window attached. Does anyone understand this gibbberish??
I did my upgrade in the usual way by creating a backup and then restoring that backup into the newly downloaded version.
Thanks in advance.

[Wolfgang_S]

Looks like that one of your items that is being used in mapdb persistence is null.
NPE ( NullPointerExeception ) was recently introduced.

[denisdmenace (Denis)]

Hi Wolfgang, so OH3.1.0 release now flags these inconsistencies? Can I just ignore the problem? I think there were errors showing up run the OH user log too. How would I find and fix the problematic item? All my items have seemed fine and nothing has showed as null up till this upgrade claims that something is amiss.

[rossko57]

If MapDB were throwing an error over Item state NULL, that would be a bug. That should be silently ignored when persisting, and as it is ignored there should not be any persisted NULLs either. You’ll likely have hundreds of Items in NULL state at system startup.

Equally random guess, there’s a bit of rubbish in your MapDB database (potentially from OH1 days depending on your migration route) that new persistence code is choking on.
I wonder what happens when an Item changed type since last recorded. Maybe a restore-on-startup used to fail silently and now complains.

How costly would it be to delete your DB and let it start a fresh one? MapDB is usually only used for restore-on-startup