openHAB 2.3 Release Candidate available!


(Wouter Born) #21

I’m testing on Ubuntu 16.04.4 (amd64) and the Oracle 1.8.0_171 JVM. It’s same warning as @mstormi:

13:23:04.643 [WARN ] [.core.audio.internal.AudioManagerImpl] - An exception occurred while getting the volume of sink 'enhancedjavasound' : Cannot determine master volume level
java.io.IOException: Cannot determine master volume level
	at org.eclipse.smarthome.io.javasound.internal.JavaSoundAudioSink.getVolume(JavaSoundAudioSink.java:118) ~[?:?]
	at org.eclipse.smarthome.core.audio.internal.AudioManagerImpl.getVolume(AudioManagerImpl.java:184) ~[?:?]
	at org.eclipse.smarthome.core.audio.internal.AudioManagerImpl.play(AudioManagerImpl.java:122) ~[?:?]
	at org.eclipse.smarthome.core.audio.internal.AudioManagerImpl.stream(AudioManagerImpl.java:175) ~[?:?]
	at org.eclipse.smarthome.core.audio.internal.AudioManagerImpl.stream(AudioManagerImpl.java:169) ~[?:?]
	at org.eclipse.smarthome.model.script.actions.Audio.playStream(Audio.java:81) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeOperation(XbaseInterpreter.java:1085) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeOperation(XbaseInterpreter.java:1060) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._invokeFeature(XbaseInterpreter.java:1046) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeFeature(XbaseInterpreter.java:991) ~[?:?]
	at org.eclipse.smarthome.model.script.interpreter.ScriptInterpreter.invokeFeature(ScriptInterpreter.java:143) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:901) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:864) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:223) ~[?:?]
	at org.eclipse.smarthome.model.script.interpreter.ScriptInterpreter.doEvaluate(ScriptInterpreter.java:219) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:203) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:491) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:255) ~[?:?]
	at org.eclipse.smarthome.model.script.interpreter.ScriptInterpreter.doEvaluate(ScriptInterpreter.java:219) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:203) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:446) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:227) ~[?:?]
	at org.eclipse.smarthome.model.script.interpreter.ScriptInterpreter.doEvaluate(ScriptInterpreter.java:219) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:203) ~[?:?]
	at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:189) ~[?:?]
	at org.eclipse.smarthome.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:82) ~[?:?]
	at org.eclipse.smarthome.model.rule.runtime.internal.engine.RuleEngineImpl.lambda$2(RuleEngineImpl.java:345) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

When changing the volume on the openHAB 2.2.0 Demo it also does not work. It also does not log this warning.


(Kai Kreuzer) #22

I would claim that setting the master volume has actually never worked on Linux, so what is new is only the exception in the log. Or is anyone (@mstormi, @vzorglub) sure that it has been working before?


(Vincent Regaud) #23

No that was not working before. Not a new issue. Would be nice if it worked though.
I posted it in another thread not related to the 2.3RC1


(Wouter Born) #24

I’ve entered the following issue for this: https://github.com/eclipse/smarthome/issues/5604


(Kai Kreuzer) #25

Ok, thanks - that what I thought. I faintly had in mind that getting the system volume on Linux never worked (and I once spend a while trying to solve that, but I failed - so it would be up to someone else to make it eventually work!).
I have created https://github.com/eclipse/smarthome/pull/5605, which should suppress the warning, so that we have the same behavior as on 2.2 again.

I know, that’s why I pinged you here :slight_smile:


(Pali) #26

I faced the same problem you described, but also another Paper UI related issue. Binding which creates channels dynamically in runtime, channels can’t be linked from paper UI. Nothing happens when icon is pressed and following is logged to browser console.

angular.min.js:107 TypeError: Cannot read property 'category' of null
at r.e.linkChannel (controllers.min.js:2)
at r.e.enableChannel (controllers.min.js:2)
at fn (eval at compile (angular.min.js:213), <anonymous>:4:550)
at r.$eval (angular.min.js:133)
at app.js:1
at r.$eval (angular.min.js:133)
at r.$apply (angular.min.js:134)
at HTMLButtonElement.<anonymous> (app.js:1)

(Kai Kreuzer) #27

I asked @henning to have a look at the Paper UI issues tonight - let’s touch wood that it is easy for him to fix!


(Dirk) #28

Hello,

it is not possible to link Items in the Paper UI. This failure appeared already in the snapshot release just before RC1 was released. There is an item created but with no fuction.

Cheers
Dirk


(Wouter Born) #29

I get warnings about mismatched characters in rules files that were OK with OH 2.2.

When I use this piece of code in a rules file:

val Procedures.Procedure2<Boolean, ArrayList<SwitchItem>> switchItems = [Boolean condition, ArrayList<SwitchItem> items |
	val newState = if (condition.booleanValue) ON else OFF
	items.filter[i | !i.state.equals(newState)].forEach[i | i.sendCommand(newState)]
]

These warnings are logged:

22:29:58.599 [WARN ] [del.core.internal.ModelRepositoryImpl] - Configuration model 'appliances.rules' has errors, therefore ignoring it: [21,73]: mismatched character ' ' expecting ']'
[21,91]: missing EOF at ','
[23,14]: mismatched character ' ' expecting ']'
[23,53]: mismatched character ' ' expecting ']'

Seems like I need to add white space to get rid of these warnings:

val Procedures.Procedure2<Boolean, ArrayList<SwitchItem>> switchItems = [ Boolean condition , ArrayList<SwitchItem> items |
	val newState = if (condition.booleanValue) ON else OFF
	items.filter [ i | !i.state.equals(newState) ].forEach[ i | i.sendCommand(newState) ]
]

Such warnings for whitespace are quite confusing.


(Wouter Born) #30

Usually I now also see about 20 of these warnings when I start openHAB:

00:58:02.865 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set
00:58:02.865 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set
00:58:02.866 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set
00:58:02.867 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set
00:58:02.867 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set
00:58:02.868 [WARN ] [internal.DiscoveryServiceRegistryImpl] - Inbox not set

There are times they don’t get logged. But then when I restart openHAB they do get logged again.


(Kai Kreuzer) #31

This is a really nasty bug that has been introduced with the unit support (like 23 [°C]) - this new notation seems to have broken the lambda support… We are looking into it (next time, please report it a few weeks ahead of a release, please :stuck_out_tongue_closed_eyes:).

Usually I now also see about 20 of these warnings when I start openHAB

Thanks, this is fixed by https://github.com/eclipse/smarthome/pull/5618.


(dj1) #32

yepp ,same issue here 2.2 had no such problem


(Vincent Regaud) #33

This one appeared this morning. Didn’t noticed them yesterday but going through the log they were there. NO errors before RC1

2018-05-24 09:30:00.006 [ERROR] [nhab.io.caldav.internal.job.EventJob] - error executing event job

org.quartz.JobExecutionException: cannot get event-container for config: openhab_tasks and eventId: 04iq7hvhss8rgat9cbd6fim2kl@google.com

	at org.openhab.io.caldav.internal.job.EventJob.execute(EventJob.java:46) [235:org.openhab.io.caldav:1.12.0.RC1]

	at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [107:org.eclipse.smarthome.core.scheduler:0.10.0.oh230RC1]

	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) [107:org.eclipse.smarthome.core.scheduler:0.10.0.oh230RC1]

(Kai Kreuzer) #34

Should hopefully be addressed by https://github.com/eclipse/smarthome/pull/5621 - many thanks to @sjka to deeply dig into this.
There wasn’t any easy solution to the problem, so as a result, the DSL syntax for number with units had to be changed (from 23 [°C] to 23|°C or also (more ugly) 5|"µm"). I will update the openHAB docs accordingly.


(Vincent Regaud) #35

@Kai
After updating to RC1, how to get back to snapshots, please?
Ubuntu apt install


(Kai Kreuzer) #36

I’d guess the same way as you did for switching to the RC: Change the apt repo from testing back to unstable.


(Vincent Regaud) #37

That’s the thing. I didn’t do anything. Just sudoku apt get upgtade


(Kai Kreuzer) #38

And you are sure that you got the RC1? @Benjy is that expected? If so, I guess it will soon be automatically replaced again as a snapshot build is running this minute.


(Ben Clark) #39

I think it’s due to APT believing that .RC1 should be newer than ~<snapshotdate>. I had missed that our previous release client version was named 2.0.0~RC1.

The snapshots repo also contain the testing packages.

To install the latest snapshot you’ll need to install the version specifically, find the latest using:

sudo apt-cache madison openhab2

Then pick the version in the second line, e.g:

sudo apt install openhab2=2.3.0~20180524170945-1

(Alain) #40

I made a fresh install of RC1 on my Windows 10 test machine. I have an issue with the Sonos binding :

the “zonegroup” channels of my 3 players are never populated, ( == NULL in my rules or when using the REST API or with Karaf console) even when I change the topology with the Sonos app. The other “group” channels (coordinator, localcoordinator, zonegroupid) are correct and the link to zonegroup is added during the startup process. I restarted and cleaned the cache several times and always the same issue.

On my prod machine with 2.3.0 Build 1246 zonegroup channels are correctly populated with the groups structure.