openHAB 4.2 Milestone discussion

Wikibear · April 14, 2024, 12:56pm

Good point. I think that hits the nail.

Another thing i found out, that third party add-ons from SmartHomeJ will be removed after update from M1 to M2. I must reinstall them manually by hand.

J-N-K · April 14, 2024, 3:18pm

They should be automatically installed. Unfortunately there seems to be an issue with the continous installation/de-installation of bundles due to the add-on finder.

Mherwege · April 14, 2024, 9:02pm

@J-N-K I wasn’t aware of a problem on this related to the add-on finder. Is there an issue for it? Can you be more precise about what the problem is?

Lolodomo · April 15, 2024, 8:25am

There is this issue.

github.com/openhab/openhab-core

4.2: bundles automatically restored to their original version

opened 09:51AM - 30 Dec 23 UTC

lolodomo

bug

Using 4.2 snapshot (3808), I encounter a strange behaviour: if I update one bund…le (bundle:update) then after a short time (max few minutes), my bundle is automatically restored to its original version ! I encountered that behaviour yesterday after updating either o.o.core.io.transport.mdns or o.o.webui.ui.basic bundles. What could be the trigger of that behaviour ? Just to explain the conditions: I just installed the snapshot 3808 form scratch in a new directory. No kar file. Remote add-ons is enabled. I update bundles using bundle:update command. Earlier I played many hours with release 4.1 and applying many times updates of o.o.webui.ui.basic without encountering that behaviour. It seems something new in 4.2...

Also mentioned here while investigating JUPnP issue:

github.com/openhab/openhab-core

New version 3.0.0 of JUPnP library is breaking at least Sonos binding when several interfaces are up

opened 08:59AM - 10 Mar 24 UTC

closed 04:21PM - 02 Apr 24 UTC

lolodomo

bug

say in DSL rule is doing nothing. In console, voice:say or audio:play are not w…orking. The console commands I tried: ``` voice say "Voici un test de son" audio play barking.mp3 audio play doorbell.mps3 audio play sonos:PLAY5:chambre barking.mp3 audio play sonos:PLAY5:chambre doorbell.mp3 ``` I am using Sonos as audio sink and VoiceRSS as TTS. The only DEBUG logs I can find are: ``` 09:44:31.712 [DEBUG] [nhab.core.audio.internal.AudioServlet] - timeout 10 seconds => timestamp 4363672656075242 nanoseconds 09:44:41.718 [DEBUG] [nhab.core.audio.internal.AudioServlet] - Removed timed out stream 7e9d3aa8-00b5-406f-ba96-adb591315993 ``` If I check the audio and voice bundles: ``` openhab> bundle:list -s | grep audio 160 x Active x 80 x 4.2.0.M1 x org.openhab.core.audio 184 x Active x 80 x 4.2.0.M1 x org.openhab.core.io.rest.audio openhab> bundle:list -s | grep voice 193 x Active x 80 x 4.2.0.M1 x org.openhab.core.io.rest.voice 225 x Active x 80 x 4.2.0.M1 x org.openhab.core.voice 293 x Active x 80 x 4.2.0.M1 x org.openhab.voice.voicerss 294 x Active x 80 x 4.2.0.M1 x org.openhab.voice.voskstt openhab> ``` @GiviMAD : as you are the one that updated this part recently, I am very afraid you broke it. I am going to switch back to OH 4.1.1 to check if audio/voice stuff is working again.

holger_hees · April 15, 2024, 8:29am

Hi, what is the recommended way to document breaking changes for the upcoming release. I made some changes related to default paths in jython binding for the 4.2 release and I want to mention it there. In the official binding documentation it is already described.

Lolodomo · April 15, 2024, 10:10am

Create a PR like this one.

All these alerts will then be documented in the release note.

pacive · April 18, 2024, 10:42am

I updated to 4.2.M2 last weekend, and noticed now that the DBQuery binding has stopped working, the bridge starts initializing, but then gets set to UNKNOWN. Enabled trace logging, and can see a log statement that says it’s connecting (to influxdb), but then nothing. Influxdb persistence works without a problem though.

milo · April 21, 2024, 6:01pm

Will openhab 4.2 be Java21 ready?

glhopital · April 21, 2024, 6:42pm

There is already ongoing work to have it working with Java 21. [CI] Add Java 21 compiling to J17 and native J21 by holgerfriedrich · Pull Request #4186 · openhab/openhab-core · GitHub

holgerf · April 21, 2024, 7:46pm

@holger_hees, you could add a breaking change alert to update.lst in the distro repo.

github.com

openhab/openhab-distro/blob/main/distributions/openhab/src/main/resources/bin/update.lst#l133-l136


      
          [4.2.0]
          ALERT;AndroidTV Binding: The thing configuration of 'port' has been renamed and split to 'googletvPort' and 'shieldtvPort'
          ALERT;evcc Binding: Update to evcc API version 0.123.1 results in several new or updated channels. Existing Items will need to be adjusted.
          ALERT;ISM8 Binding: Most channels have changed and are now using Units of Measurements. Items must be adapted and the things must be recreated.

Section 4.2.0 (in alphabetical order).

holger_hees · April 22, 2024, 6:30am

done

milo · April 26, 2024, 4:26am

Hello, is there an answer to my question?

Lolodomo · April 26, 2024, 5:50am

Work is in progress (not finished) to make openHAB runnable with Java 21.
OH 4.2 will not require Java 21 to run and recommendation will remain using Java 17.

kristofejro · April 26, 2024, 6:10am

Just for the record. Start and stop of openhab service (4.2.0.M2 on openhabian Pi4) looks like this for me:

Apr 26 07:26:06 openHABianPi systemd[1]: Stopping openhab.service - openHAB instance, reachable at http://openHABianPi:8080...
Apr 26 07:26:16 openHABianPi karaf[798]: Exception in thread "Timer-5" java.lang.NullPointerException: Cannot invoke "org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse.getState()" because "response" is null
Apr 26 07:26:16 openHABianPi karaf[798]: Exception in thread "Timer-4"         at org.openhab.binding.zwave.internal.protocol.ZWaveNode$WakeupTimerTask.run(ZWaveNode.java:1518)
Apr 26 07:26:16 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
Apr 26 07:26:16 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.run(Timer.java:516)
Apr 26 07:26:16 openHABianPi karaf[798]: Exception in thread "Timer-8" java.lang.NullPointerException: Cannot invoke "org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse.getState()" because "response" is null
Apr 26 07:26:16 openHABianPi karaf[798]:         at org.openhab.binding.zwave.internal.protocol.ZWaveNode$WakeupTimerTask.run(ZWaveNode.java:1518)
Apr 26 07:26:16 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
Apr 26 07:26:16 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.run(Timer.java:516)
Apr 26 07:26:17 openHABianPi karaf[798]: java.lang.NullPointerException: Cannot invoke "org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse.getState()" because "response" is null
Apr 26 07:26:17 openHABianPi karaf[798]:         at org.openhab.binding.zwave.internal.protocol.ZWaveNode$WakeupTimerTask.run(ZWaveNode.java:1518)
Apr 26 07:26:17 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
Apr 26 07:26:17 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.run(Timer.java:516)
Apr 26 07:26:17 openHABianPi karaf[798]: Exception in thread "Timer-7" java.lang.NullPointerException: Cannot invoke "org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse.getState()" because "response" is null
Apr 26 07:26:17 openHABianPi karaf[798]:         at org.openhab.binding.zwave.internal.protocol.ZWaveNode$WakeupTimerTask.run(ZWaveNode.java:1518)
Apr 26 07:26:17 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
Apr 26 07:26:17 openHABianPi karaf[798]:         at java.base/java.util.TimerThread.run(Timer.java:516)
Apr 26 07:26:25 openHABianPi systemd[1]: openhab.service: Deactivated successfully.
Apr 26 07:26:25 openHABianPi systemd[1]: Stopped openhab.service - openHAB instance, reachable at http://openHABianPi:8080.
Apr 26 07:26:25 openHABianPi systemd[1]: openhab.service: Consumed 6h 32min 58.528s CPU time.
-- Boot 8498248331b545d3939b21c53a4b083d --
Apr 26 07:27:21 openHABianPi systemd[1]: Started openhab.service - openHAB instance, reachable at http://openHABianPi:8080.
Apr 26 07:29:40 openHABianPi karaf[790]: org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=shell; type=karaf.feature; version="[4.4.5,4.4.5]"; filter:=">
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:433)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:420)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:374)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:256)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:399)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069)
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004)
Apr 26 07:29:40 openHABianPi karaf[790]:         at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
Apr 26 07:29:40 openHABianPi karaf[790]:         at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
Apr 26 07:29:40 openHABianPi karaf[790]:         at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
Apr 26 07:29:40 openHABianPi karaf[790]:         at java.base/java.lang.Thread.run(Thread.java:840)
Apr 26 07:29:40 openHABianPi karaf[790]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve shell/4.4.5: missing requirement [shell/4.4.5] osgi.identity; osgi.identity=org.apache.karaf.shell.core; type=os>
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Apr 26 07:29:40 openHABianPi karaf[790]:         ... 12 more
Apr 26 07:29:40 openHABianPi karaf[790]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.apache.karaf.shell.core/4.4.5: missing requirement [org.apache.karaf.shell.core/4.4.5] osgi.wiring.package; >
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Apr 26 07:29:40 openHABianPi karaf[790]:         ... 13 more
Apr 26 07:29:40 openHABianPi karaf[790]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.eclipse.osgi/3.18.0.v20220516-2155: missing requirement [org.eclipse.osgi/3.18.0.v20220516-2155] osgi.ee; fi>
Apr 26 07:29:40 openHABianPi karaf[790]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Apr 26 07:29:40 openHABianPi karaf[790]:         ... 14 more

milo · April 26, 2024, 11:42am

Hey,

misunderstanding I replied to my issue in post

moody_blue · April 27, 2024, 2:55pm

With 4.0 the log started to include warnings about delayed start of Daikin and MiiO bindings. Now with 4.2.0,M2 these warnings contain more info

2024-04-26 08:44:33.522 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'daikin:ac_unit:cozinha' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-04-26 08:44:33.543 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'daikin:ac_unit:cozinha': {thing/channel=Type description daikin:acunit-specialmode-powerful for daikin:ac_unit:cozinha:specialmode-powerful not found, although we checked the presence before.}
2024-04-26 08:44:33.576 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'daikin:ac_unit:suite' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-04-26 08:44:33.579 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'daikin:ac_unit:suite': {thing/channel=Type description daikin:acunit-specialmode-powerful for daikin:ac_unit:suite:specialmode-powerful not found, although we checked the presence before.}
2024-04-26 08:44:33.588 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'daikin:ac_unit:sala' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-04-26 08:44:33.590 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'daikin:ac_unit:sala': {thing/channel=Type description daikin:acunit-specialmode-powerful for daikin:ac_unit:sala:specialmode-powerful not found, although we checked the presence before.}
2024-04-26 08:44:53.624 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'miio:gateway:1072B9E6' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-04-26 08:44:53.627 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'miio:gateway:1072B9E6': {thing/channel=Type description miio:LUMI_GATEWAY_MIEU01_guard for miio:gateway:1072B9E6:guard not found, although we checked the presence before.}

Maybe now the binding maintainners can correct this.

DarkoG · April 28, 2024, 7:12pm

The fix for Tapo is still not merged

J-N-K · April 28, 2024, 8:21pm

I don’t see an open Pull Request for tapo:

https://github.com/openhab/openhab-addons/pulls?q=is%3Apr+is%3Aopen+tapo+in%3Atitle

Can you point me to that?

moody_blue · April 28, 2024, 9:30pm

It was merged this morning

mstormi · May 6, 2024, 6:12am

A post was split to a new topic: Kodi install fails