Issue with Souliss binding after update

Setup, Configuration and Use Runtime
1

After yeasterday update on OH2 Souliss binding is not working anymore.
I got this error
2017-01-14 16:23:59.336 [ERROR] [b.core.service.AbstractActiveService] - Error while executing background thread Souliss Refresh Service
java.lang.NullPointerException
at org.openhab.binding.souliss.internal.SoulissBinding.execute(SoulissBinding.java:350)[201:org.openhab.binding.souliss:1.9.0.201701130210]
at org.openhab.core.binding.AbstractActiveBinding$BindingActiveService.execute(AbstractActiveBinding.java:157)[184:org.openhab.core.compat1x:2.0.0.201701121723]
at org.openhab.core.service.AbstractActiveService$RefreshThread.run(AbstractActiveService.java:173)[184:org.openhab.core.compat1x:2.0.0.201701121723]
2017-01-14 16:23:59.387 [ERROR] [b.core.service.AbstractActiveService] - Error while executing background thread Souliss Refresh Service
java.lang.NullPointerException
at org.openhab.binding.souliss.internal.SoulissBinding.execute(SoulissBinding.java:350)[201:org.openhab.binding.souliss:1.9.0.201701130210]
at org.openhab.core.binding.AbstractActiveBinding$BindingActiveService.execute(AbstractActiveBinding.java:157)[184:org.openhab.core.compat1x:2.0.0.201701121723]
at org.openhab.core.service.AbstractActiveService$RefreshThread.run(AbstractActiveService.java:173)[184:org.openhab.core.compat1x:2.0.0.201701121723]

Can you help me?

2

Still not solved … Can someone help me?

3

Hi,

is there anybody out there working on the Souliss binding to move it to a OH2 version?

I just created a complete new installation with the OH2.1 snapshot
There are a few issues I which did not dissapear:

Some not to Souliss related functions (Yamaha receiver binding or using a setpoint slider) result in a NullPointer Exception:

2017-02-05 14:59:08.944 [WARN ] [org.apache.karaf.services.eventadmin] - EventAdmin: Exception during event dispatch [org.osgi.service.event.Event [topic=openhab/command/LightDuration] {bridgemarker=true, item=LightDuration, command=2} | {org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={event.topics=openhab/*, service.pid=org.openhab.souliss, component.name=org.openhab.binding.souliss, component.id=160, service.id=294, service.bundleid=185, service.scope=bundle} | Bundle(org.openhab.binding.souliss_1.10.0.201702040211 [185])]
java.lang.NullPointerException
	at org.openhab.binding.souliss.internal.SoulissBinding.receiveCommand(SoulissBinding.java:135)[185:org.openhab.binding.souliss:1.10.0.201702040211]
	at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:42)[186:org.openhab.core.compat1x:2.1.0.201702051222]
	at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.FutureTask.run(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[:1.8.0_111]
	at java.lang.Thread.run(Unknown Source)[:1.8.0_111]

So there seems to be some “crosstalk” to the souliss binding, whatever happens there.

Also Typical T51 for analog read seems not to work at all.

So it would be really nice, if there is sombody who could take a look to these issues.

4

Is there anybody who can work on the Souliss binding?
Or am I riding here a dead horse? :frowning:

5

I noticed the same problem with the mqtt and souliss.
This is what warning i get when i try to turn on a light over my mqtt configuration

15:49:03.729 [WARN ] [org.apache.karaf.services.eventadmin] - EventAdmin: Exception during event dispatch [org.osgi.service.event.Event [topic=openhab/command/Light_Dinning_Room] {bridgemarker=true, item=Light_Dinning_Room, command=OFF} | {org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={event.topics=openhab/*, service.pid=org.openhab.souliss, component.name=org.openhab.binding.souliss, component.id=241, service.id=373, service.bundleid=251, service.scope=bundle} | Bundle(org.openhab.binding.souliss_1.10.0 [251])]
java.lang.NullPointerException
	at org.openhab.binding.souliss.internal.SoulissBinding.receiveCommand(SoulissBinding.java:135)[251:org.openhab.binding.souliss:1.10.0]
	at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:45)[176:org.openhab.core.compat1x:2.1.0]
	at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]

Do we have anything new abou this?

6

Clearly a bug in that binding. The first obvious step would be to create a bug report.
And yes, 6 days ago, one has been created: https://github.com/openhab/openhab1-addons/issues/5369
And a few minutes later, there was a fix for it: https://github.com/openhab/openhab1-addons/pull/5370

Should be available in the next distro build :slight_smile:

7

Beta 2.0 Souliss binding is available on souliss-it forum.
Still a raw beta but works better than the 1.0 one and has the autodiscover function which improve quite a bit the setting of a large net of souliss devices.
Regards
Lorenzo