I can only find this in openhab.logs, after this nothing (I tried it again yesterday, last log was around 17h,…)
2018-10-15 17:15:53.334 [ERROR] [ome.core.thing.link.ThingLinkManager] - Exception occurred while informing handler: null
java.lang.NullPointerException: null
at org.openhab.binding.seneye.handler.SeneyeHandler.newState(SeneyeHandler.java:69) ~[?:?]
at org.openhab.binding.seneye.handler.SeneyeHandler.handleCommand(SeneyeHandler.java:58) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.channelLinked(BaseThingHandler.java:278) ~[?:?]
at org.eclipse.smarthome.core.thing.link.ThingLinkManager.lambda$0(ThingLinkManager.java:300) ~[?:?]
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) [?:?]
It seems when I initialise/save my settings, it will fetch data, but only once. Also only temperature and NH3 is collected, not pH so far. I have no issues going into the seneye.me or app and have a valid slide.
I now have set up de seneye via PaperGUI. It says the device is online. in the overview/control tab of paper GUI the data is the same/not updated. For my items I used the channel which is shown in the screenshot below (seneye:monitor:3054d5ed:temperature).
Seems something with the scheduler? when I edit Thing in paper GUI and save again I get this instantly in the logs:
09:54:51.622 [WARN ] [e.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
09:54:52.249 [WARN ] [ommon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception
java.lang.NullPointerException: null
at org.openhab.binding.seneye.handler.SeneyeHandler.newState(SeneyeHandler.java:69) ~[?:?]
at org.openhab.binding.seneye.internal.SeneyeService.lambda$0(SeneyeService.java:77) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
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) [?:?]
2018-10-16 10:54:30.650 [DEBUG] [binding.seneye.handler.SeneyeHandler] - Initializing Seneye API service.
2018-10-16 10:54:30.671 [WARN ] [.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
2018-10-16 10:54:31.298 [DEBUG] [inding.seneye.internal.SeneyeService] - seneye '54450' read
2018-10-16 10:54:31.311 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception
java.lang.NullPointerException: null
at org.openhab.binding.seneye.handler.SeneyeHandler.newState(SeneyeHandler.java:69) ~[?:?]
at org.openhab.binding.seneye.internal.SeneyeService.lambda$0(SeneyeService.java:77) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
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) [?:?]
There is nothing jumping out at me… You could try putting something in the location field (although I can’t see that causing any issues)
You could also try the test version of an update to the binding, to do this:-
Uninstall the current binding via paper.
Download the .jar from
I’ll try updating to latest version, but prefer to do that when I’m on location. It’s a live environment with a lot of hvac control. Will post update later on…
No problem,
Unfortunately I’m not the original author of the binding, so there is still loads I do not understand.
The update has some bits I added due to issues I was having, as well as adding a couple of extra channels.
If we work out why it doesn’t work for you hopefully I can add that as well.
I’m running now the latest version (2.4.0.M7) since a day of 2. And no issues found!
Great job, and thank you very much !!!
I’m just missing 1 thing in this story: An out of the water trigger.
Seneye is able to send you a message when the sensor is out of the water. Can we also check this with Openhab? I’m very interested in this. This way I can cut fe the power of the filterpump…
The Binding should now include four new channels disconnected, slideserial, outofwater and wrongslide.
The readme on openHAB has been updated with the details. Readme
Let me know how you get on
Hi Ben,
Before you make any changes can you check the following for me.
In PaperUI if you go to configuration, then things, then the Seneye thing.
Can you check if the new channels are shown, and are unselected?
Just want to see if it hides the new channels or not.
Many thanks
Can you log into the openHAB console and enter bundle:list and confirm what version seneye is reporting?
For some reason it doesn’t appear to have updated fully?!?