openHAB 3.1 Milestone discussion

Please restrict your discussion and question to issues that are specific to latest OH 3.1 milestone
else open your own thread.

On VSC “slowing” OH, think of the LSP server which does “remote” syntax checking of the VSC code in OH. This is particularly nasty if compilation/parsing of a file takes long on your OH box as is sometimes the case e.g. when using Java primitives on ARM.

I understand I should have opened a different thread, sorry for that.
Let me just report my status, for the sake of consistency…
I had various other problems with my OH3 system. Not only the system was slow, stopping VSC did improve, stopping OH did improve even more… but also I had group Items that were simple migration from my OH2 setup that were not updating properly.
All this to say, I ended up changing my SD card and things are now looking much more normal now.

1 Like

When scanning using zigbee binding or anything really I get in dev console:

TypeError: t.$inputEl is undefined
    value http://192.168.0.76:8080/js/app.js:7
    loadInbox http://192.168.0.76:8080/js/16.app.js:1
    at http://192.168.0.76:8080/js/app.js:7
    Qe http://192.168.0.76:8080/js/app.js:7
    promise callback*Ye http://192.168.0.76:8080/js/app.js:7
    at http://192.168.0.76:8080/js/app.js:7
    update http://192.168.0.76:8080/js/app.js:7
    update http://192.168.0.76:8080/js/app.js:7
    notify http://192.168.0.76:8080/js/app.js:7
    set http://192.168.0.76:8080/js/app.js:7
    set http://192.168.0.76:8080/js/app.js:7
    loadInbox http://192.168.0.76:8080/js/16.app.js:1
    promise callback*loadInbox http://192.168.0.76:8080/js/16.app.js:1
    intervalId http://192.168.0.76:8080/js/16.app.js:1
    setInterval handler*scan/< http://192.168.0.76:8080/js/16.app.js:1
    promise callback*scan http://192.168.0.76:8080/js/16.app.js:1
    qe http://192.168.0.76:8080/js/app.js:7
    n http://192.168.0.76:8080/js/app.js:7
    qe http://192.168.0.76:8080/js/app.js:7
    $emit http://192.168.0.76:8080/js/app.js:7
    a http://192.168.0.76:8080/js/app.js:7
    a http://192.168.0.76:8080/js/app.js:7
    dispatchEvent http://192.168.0.76:8080/js/app.js:23
    onClick http://192.168.0.76:8080/js/app.js:23
    mounted http://192.168.0.76:8080/js/app.js:23
    qe http://192.168.0.76:8080/js/app.js:7
    tn http://192.168.0.76:8080/js/app.js:7
    insert http://192.168.0.76:8080/js/app.js:7
    O http://192.168.0.76:8080/js/app.js:7
    Fr http://192.168.0.76:8080/js/app.js:7
    _update http://192.168.0.76:8080/js/app.js:7
    a http://192.168.0.76:8080/js/app.js:7
    get http://192.168.0.76:8080/js/app.js:7
    run http://192.168.0.76:8080/js/app.js:7
    pn http://192.168.0.76:8080/js/app.js:7
    at http://192.168.0.76:8080/js/app.js:7
    Qe http://192.168.0.76:8080/js/app.js:7
    promise callback*Ye http://192.168.0.76:8080/js/app.js:7
    at http://192.168.0.76:8080/js/app.js:7
    update http://192.168.0.76:8080/js/app.js:7
app.js:7:11689

Would this prevent scanning? How can I see in the logs that the zigbee binding is actually scanning?

First, start a new thread. Next,. read the Zigbee binding documentation & enable DEBUGH logs as instructed there.

Yesterday I installed M3 SNAPSHOT Build 2307 which seems to have introduced a new issue in the Mail binding (see log below). The error NoSuchMethodError seems to imply a broken dependency. => Any thoughts?

2021-04-05 10:56:46.104 [WARN ] [ab.binding.mail.internal.SMTPHandler] - Sending the email to the following server failed : <myserver>:465
2021-04-05 10:56:46.106 [WARN ] [ab.binding.mail.internal.SMTPHandler] - java.lang.NoSuchMethodError: 'boolean javax.activation.MimeType.isSpecial(char)'

There is no such thing. If you installed a SNAPSHOT it is off-topic for this thread. This thread is for M3 issues only.

Sweet.

1 Like

If you want any help state accurately what you installed.

3.1.0.SNAPSHOT Build 2307 (from yesterday)

Off-topic for Milestone 3 thread then. As I stated you need to start a new thread with your issue.

ftr I am facing the same error. Sending mails does not work anymore. I already filed an issue on GitHub for tracking.

3 Likes

Me too.

Hi
just switched from 3.0.1 stable to 3.1.0 M3 and this is coming every few seconds in the log.

10:22:00.603 [ERROR] [.converter.ZigBeeConverterSwitchOnoff] - 04CF8CDF3C794DE9: Error 0xffff setting client binding

I will reboot and see if it stays … just as an info for the moment.

Hi there,

I have been using the 3.1 M3 official docker image (debian based) on a Synology 920+ since it came out. I noticed a strange behaviour with the rules engine in M3. The rule engine (13:06:33.782 [INFO ] [re.automation.internal.RuleEngineImpl] - Rule engine started.) started only 5 minutes after system startup. If I remember correctly it used to start up much faster in M2.

Any idea what might cause this ?

This sounds like a Good Thing given peoples frequent troubles with start-up races.

1 Like

Well, I consider it an unwanted behaviour. During that time my logs are full of exceptions of rules which cannot be executed and basically a restart of the container takes around 10 minutes … I cannot imagine this is as intended.

1 Like

That is odd. Who is running those rules then?

same issue here :slight_smile: 3.1.0 build #2312

Off-topic for the Milestone thread. I assume you opened an issue on GitHub for this or commented on an existing one?

1 Like