openHAB 4.0 Milestone discussion

[J-N-K (Jan N. Klug)]

But no rules on the system that runs OH4.M1?

[apella12 (Bob Eckhoff)]

Sorry wasn’t clear. 25 rules on the Rpi3. They are very simple. I will see if I can attach them.
They are DSL, no scripts, mostly Cron and counting.
HEM-refresh.rules.txt (3.5 KB)
Wattage_reports.rules.txt (6.1 KB)

[J-N-K (Jan N. Klug)]

The more important information is: what language. Rules and their script engines are always a good candidate for memory leaks because they are created quite often.

[apella12 (Bob Eckhoff)]

More information: the RRD4j persistence began to fail about an hour and a half prior to the actual crash. Log is repetitive, but excerpt attached. I don’t know if this was the cause or the effect of low memory.
precrashlog.txt (6.4 KB)

[nYce (JK)]

Thx! I found the item that is causing the problem.

the Link had a Profile (hpa.js) but “JSONPATH” wasnt selected anymore. After choosing it my error changed to

[WARN ] [ofiles.JSonPathTransformationProfile] - Could not transform state ‘98952.66’ with function ‘hpa.js’ and format ‘%s’

Changing the format to %.2f doesnt help.

is there any way to transform my values in a link profile now or do i have to wait until the script transform can do that?

hpa.js contains the following:

(function(i) {
    return ((i / 100) / Math.pow((1 - (232 / 44330)), 5.255));
})(input)

[hafniumzinc (T)]

@nYce

is there any way to transform my values in a link profile now

From the master post

Inline JS scripts in transformations and JS profiles are still work in progress.

openHAB 4.0 Milestone Builds

Dear community, You had to wait for a long while, but I am now happy to announce that we have the first milestone build of openHAB 4.0 ready for download! There has been a major technical change by moving from Java11 to Java17, which involved upgrading many libraries to very recent versions. This is all successfully done and the snapshot builds were already tested by many of you, which helped on identifying and fixing regressions. The positive effect is that we are now on a very future-proof …

[moody_blue (Hugo)]

Replaced HTTP binding by the SmartHome/J HTTP Binding and errors are gone. Also things come up without the 2 minute delay.

Bindings Miio and Daikin still show errors and delayed start.

[JimT (jimtng)]

I noticed about 40s delay after being connected to the openhab cloud and before sitemaps and Things were loading, but there were no errors in the log, just silence. Which log prefixes must I turn on to see what’s going on?

[GadgetGuy (Bill)]

A little disappointed I didn’t get a reply to my HomeKit question. After the problems with 4.0 and other issues I’ve had (no binding support for several of my devices, near zero support on Youtube) I decided to move on. I finally made the switch to Home Assistant container and haven’t looked back.

[Udo_Hartmann]

Standards seem to be extremly high nowadays…

[JimT (jimtng)]

@GadgetGuy

A little disappointed I didn’t get a reply to my HomeKit question. After the problems with 4.0 and other issues I’ve had (no binding support for several of my devices, near zero support on Youtube) I decided to move on. I finally made the switch to Home Assistant container and haven’t looked back.

You could’ve downgraded back to a STABLE version instead.

Milestone releases, let alone the FIRST milestone is meant for those who are willing to test and understand that there will be issues. Nobody gets paid to work here and to provide customer support. There is certainly no mechanism within this single thread to keep track of individual issue/case, so it’s easy to get buried. Each individual developer works on things that they’re working on, there are many moving parts and they do not all monitor this forum / topics. I’m guessing sooner or later, if it’s a bug it’ll get discovered, or in the case that the problem only exists on your system, you’ll need to provide more details to make it easier for others to help you.

In any case, I’m glad that you’re happier now, that’s all that matters. This is a hobby for ALL of us, developers and users alike.

[ML1982]

I just tried to upgrade my openhabian to openHAB 4.0.0.M1.

But Openhab doesn’t start any more. Here is the log. Any Ideas or suggestions what I can do?

2023-03-25 20:36:06.247 [ERROR] [Events.Framework                    ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.xtext [128]
  Unresolved requirement: Require-Bundle: org.objectweb.asm; bundle-version="[9.4.0,9.5.0)"; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.eclipse.emf.mwe.core; bundle-version="1.3.21"; visibility:="reexport"; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.eclipse.emf.mwe.utils; bundle-version="1.3.21"; visibility:="reexport"; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.eclipse.xtend; bundle-version="2.2.0"; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.eclipse.xtend.typesystem.emf; bundle-version="2.2.0"; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.eclipse.xtext.util; visibility:="reexport"
	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) ~[org.eclipse.osgi-3.18.0.jar:?]
2023-03-25 20:36:06.260 [ERROR] [Events.Framework                    ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.freeathomesystem [27]

[Udo_Hartmann]

Did you update to Java 17 first?

[ML1982]

no, accidental afterwards

[Udo_Hartmann]

Already tried to reboot?

[ML1982]

serveral times.

But I just restored a Backup, and with the correct sequence of updating Java from Java11 to Java17 and the openhab update afterwards it works.

I’ve problems with the netatmo binding but I think, that’s another issue.

[morph166955 (B R)]

Have you cleared cache?

[jswim788 (John Schmitz)]

Just hit this issue with OH4 M1. I didn’t have this in OH3.4. Any suggestions on debugging this further?

2023-03-26 06:20:42.457 [WARN ] [org.eclipse.jetty.util.Scanner      ] -
java.nio.file.FileSystemException: /var/lib/openhab/etc: Too many open files
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:100) ~[?:?]
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) ~[?:?]
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]
        at sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:440) ~[?:?]
        at java.nio.file.Files.newDirectoryStream(Files.java:482) ~[?:?]
        at java.nio.file.FileTreeWalker.visit(FileTreeWalker.java:301) ~[?:?]
        at java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:323) ~[?:?]
        at java.nio.file.Files.walkFileTree(Files.java:2804) ~[?:?]
        at org.eclipse.jetty.util.Scanner.scanFiles(Scanner.java:671) ~[?:?]
        at org.eclipse.jetty.util.Scanner.scan(Scanner.java:640) ~[?:?]
        at org.eclipse.jetty.util.Scanner$1.run(Scanner.java:558) ~[?:?]
        at java.util.TimerThread.mainLoop(Timer.java:566) ~[?:?]
        at java.util.TimerThread.run(Timer.java:516) ~[?:?]

[jswim788 (John Schmitz)]

Also seeing this issue, could not normalize configuration for Zwave:

4.0M1 Zwave issue - Could not normalize configuration

I upgraded to 4.0 M1 and now I see this issue: 2023-03-26 13:24:10.334 [WARN ] [core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'zwave:device:d09e64fb:node6' because the thing type was not found in registry. 2023-03-26 13:24:10.335 [WARN ] [core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'zwave:device:d09e64fb:node6' because the thing type was not found in registry. 2023-03-26 13:24:10.347 [WARN ] [core.thing.internal.ThingManagerImpl]…

[J-N-K (Jan N. Klug)]

Does this happen all the time or did it happen once? If it happens more than once: When does it happen (immediately after starting? after some time?). What bindings are installed? Anything from 3rd party or community marketplace? Any errors in the log before?