openHAB Milestone builds

[Kim_Andersen]

It’s been there for some time before M6. You probably didn’t let the OH upgrade process change your cfg files.

“Low configured threads” warning Installation

We also noticed the warning while upgrading Karaf in #761 and opted for suppressing the warning with the logging changes you refused to apply. wink

I probably didn´t, cause I dont recall never be given the option!

Question is then - how to fix this?

I wonder if this could be related. I just discovered last night I have some serious problems with Grafana rendering png´s. After upgrading to M8 and now 2.4 release, it takes aprox one minute to render one picture. (with openhab 2.3 it took only a few seconds). Rendering more than one picture at the same time (same sitemap), ends with an timeout. (grafana error - “Signal: killed”).

[mstormi (Markus Storm)]

Question is then - how to fix this?

Reading the thread I linked to would have led you to

"Low configured threads" warning

I noticed the following to be in /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg.dpkg-dist. I (as probably you as well) refused to have the install routine replace my org.ops4j.pax.logging.cfg. # Filters warnings about small thread pools. # The thread pool is kept small intentionally for supporting resource constrained hardware. log4j2.logger.threadpoolbudget.name = org.eclipse.jetty.util.thread.ThreadPoolBudget log4j2.logger.threadpoolbudget.level = ERROR

and

Fix for Jetty error when running on host with many cores

If you’re running openHAB on a host computer with many cores, you may see an error in your log file that looks like this. 16:25:43.381 [ERROR] [et.http.internal.WebClientFactoryImpl] - Could not start Jetty http client java.lang.IllegalStateException: Insufficient configured threads: required=13 < max=10 for QueuedThreadPool[common]@75f3f957{STARTED,5<=5<=10,i=5,q=0}[ReservedThreadExecutor@16f08868{s=0/1,p=0}] at org.eclipse.jetty.util.thread.ThreadPoolBudget.check(ThreadPoolBudget.java…

I wonder if this could be related.

Unlikely.
Running Grafana is memory intensive so if you run on a SBC like a RPi you’re more likely to be out of memory.

[Kim_Andersen]

Reading the thread I linked to would have led you to

Sorry, you´re right, I didn´t. Just did… Thank you, I have something to look at tonight…

Unlikely.
Running Grafana is memory intensive so if you run on a SBC like a RPi you’re more likely to be out of memory.

Hmm, so what you say is, that the Rpi 3B is no longer suitable for openhab 2.4 due to be using more memory?

I know thats not what you specificly said, I just twisted it because this problem appeared after upgrading openHab from 2.3 to 2.4. So it could seem like this is the reason. Grafana has not changed, it´s still the same version.

[mstormi (Markus Storm)]

Any restart results in actual memory usage to change. And mem is so tight on any RPi that if you run OH PLUS (probably) InfluxDB PLUS Grafana any small change might be that little drop that makes the barrel overflow.
I’d remove it from there and run on another computer instead.
But we’re off-topic now.

[Nicholas_Waterton]

About the harmonyhub communication error:

This is harmony hub firmware 206. Logitech have removed access on port 522, so the binding will no longer work at all.

Not an OH issue.

I have hacked together an MQTT interface to the websockets server on harmony port 8088, this replaces the harmonyhub binding functionality, by using mqtt items.

The harmonyhub binding would have to be rewritten to use the websockets interface in order to restore functionality.

[sihui]

About the harmonyhub communication error:

Alternative:

Logitech Harmony Hub Binding - 4.15.206 firmware broke local API connection

Thank you for this.

[Nicholas_Waterton]

Interesting, looks like Logitech bowed to pressure.

I can’t see this developer version lasting though. I’ll probably stick with my hacked websockets version for now, it’s working well.

[johannesbonn (Johannes)]

I have the same problem with ThingAction. But if I remove ThingAction. I get the same error for the getThinfstatus expression. Could you please poste your code line with the ThingAction part.

Thanks a lot!

[sihui]

poste your code line

Before:

var status = ThingAction.getThingStatusInfo("zwave:device:uzb:node26").getStatus()

After:

var status = getThingStatusInfo("zwave:device:uzb:node26").getStatus()

[johannesbonn (Johannes)]

getThingStatusInfo(“zwave:device:uzb:node26”).getStatus()

Thank you!

[Kai (Kai Kreuzer)]

FYI: I’ve just did a 2.5.0.M1 build, which is available in the usual places - unfortunately, I don’t have a change log available for it, but all changes since 2.4 that have been merged until yesterday are included.

[mstormi (Markus Storm)]

Thanks.
FWIW, can you (@benjy ?) please re-affirm what’s the current repo.
I used to have
#deb https://dl.bintray.com/openhab/apt-repo2 testing main
which was the latest to find mentioned in this thread, too.
But I had to change to the same as for the snapshots in order to get to see the M1 build, i.e.
deb http://openhab.jfrog.io/openhab/openhab-linuxpkg testing main

Is thath correct ?

[Kai (Kai Kreuzer)]

You can see that the apt package is available here: https://bintray.com/openhab/apt-repo2/openhab2
But due to quota constraints, we might move it in the future to artifactory, but that’s not yet the case.

[pacive (Anders Alfredsson)]

I can’t get the latest milestone, apt tells me that all packages are up to date. I have this in my /etc/apt/sources.list.d/openhab2.list:

deb https://dl.bintray.com/openhab/apt-repo2 testing main

I used this to get the 2.4 milestones, but now I get nothing. I also tried updating to milestone through openhabian-config, but no dice…

[vossivossi]

I’ve just did a 2.5.0.M1 build, which is available in the usual places

There is also no link on the download page to this 2.5.0.M1 version, only stable and snapshot:

[Benjy (Ben Clark)]

All builds are put into Artifactory before being distributed to Bintray, so while the Artifactory repo will work, the Bintray repo will be faster and more stable.

Mind, there’s a problem I need to look at where Bintray isn’t allowing the download of packages automatically. I’ve just fixed this for the new M1 build.

[Kai (Kai Kreuzer)]

There is also no link on the download page to this 2.5.0.M1 version, only stable and snapshot:

Right, those had been deactivated with the 2.4 release (as there was no milestone available then).
I have created https://github.com/openhab/website/pull/149 to bring it back!

[fibu-freak (Peter)]

After installing the 2.5.0 M1 Version via openhabian-config i found the Rest-Api installed although i hadn’t installed before.

On Startup i now get this error messages:

2019-01-24 12:22:46.404 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : doFindMethod: Suitable but non-accessible method found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-01-24 12:22:46.426 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : findMethod: Suitable but non-accessible method setScheduler found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl, subclass of org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-01-24 12:22:46.430 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : bind method [setScheduler] not found; Component will fail
2019-01-24 12:22:46.433 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : bind method [setScheduler] not found
2019-01-24 12:22:46.437 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : doFindMethod: Suitable but non-accessible method found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-01-24 12:22:46.441 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : findMethod: Suitable but non-accessible method unsetScheduler found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl, subclass of org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-01-24 12:22:46.443 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : unbind method [unsetScheduler] not found; Component will fail
2019-01-24 12:22:46.446 [ERROR] [org.eclipse.smarthome.core          ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(87)] : unbind method [unsetScheduler] not found

Did i made anything wrong ?

[hilbrand (Hilbrand Bouwkamp)]

Issue: Scheduler errors on startup

[fibu-freak (Peter)]

thx, for fast reply. As i’m not very experienced, so what does this mean for me? Should i go back to 2.4 stable or can i live with the error 'til the next Milestone, as i won’t use snapshots ?