Seneye Binding

MickUrsell · December 6, 2018, 9:26pm

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

brononius · December 7, 2018, 5:19am

The channels are not in the paperUI.
I don’t see an option to (un)hide/more/advanced/… Just ‘disable’.

MickUrsell · December 7, 2018, 7:58am

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?!?

brononius · December 7, 2018, 7:59am

Sure, here we go:

235 │ Active │ 80 │ 2.4.0.M7 │ Seneye Binding

MickUrsell · December 7, 2018, 8:01am

Great thanks… should be the correct one.
Odd just trying to test on my setup.

MickUrsell · December 7, 2018, 8:28am

I just reverted my setup to 2.3 and run the upgrade again.
As soon as I launch 2.4M7 I see then new channels…
The first thing that springs to mind is did you clear cache and temp files when you upgraded?
clear the cache

brononius · December 7, 2018, 9:02am

hmmm, no luck.
I tried following:

uninstall binding (through paperUI)
stop OH2
Cleared the cache
start OH2
install binding (through paperUI)

In my logs, I see an error. But not sure if it’s linked with the problem/binding, or with my global installation.

2018-12-07 09:51:56.772 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-seneye': Error restarting bundles:
Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bundle org.eclipse.smarthome.io.rest.sse.

But after this, everything is working as above. Except the new channels…

2018-12-07 09:51:56.737 [hingStatusInfoChangedEvent] - 'seneye:monitor:5709eb0c' changed from UNINITIALIZED to INITIALIZING
2018-12-07 09:51:56.762 [hingStatusInfoChangedEvent] - 'seneye:monitor:5709eb0c' changed from INITIALIZING to ONLINE
2018-12-07 09:52:08.989 [vent.ItemStateChangedEvent] - mySeneye_NH4 changed from NULL to 28.67
2018-12-07 09:52:08.991 [vent.ItemStateChangedEvent] - mySeneye_O2 changed from NULL to 8.4
2018-12-07 09:52:08.992 [vent.ItemStateChangedEvent] - mySeneye_par changed from NULL to 0.0
2018-12-07 09:52:08.994 [vent.ItemStateChangedEvent] - mySeneye_PH changed from 7.86 to 7.84
2018-12-07 09:52:08.995 [vent.ItemStateChangedEvent] - mySeneye_lux changed from NULL to 0.0
2018-12-07 09:52:08.997 [vent.ItemStateChangedEvent] - mySeneye_kelvin changed from NULL to 0.0
2018-12-07 09:52:08.999 [vent.ItemStateChangedEvent] - mySeneye_lastreading changed from NULL to 2018-12-07T09:37:01.000+0100
2018-12-07 09:52:09.001 [vent.ItemStateChangedEvent] - mySeneye_slideexpires changed from NULL to 2019-01-03T18:05:27.000+0100

MickUrsell · December 7, 2018, 9:10am

I found this post that seams to be a similar issue, hopefully it helps a little?

smarthome io rest SSE internal error

brononius · December 7, 2018, 9:25am

As I understand it, this error comes from clearing the cache. If I know restart OH, no more error. Also a complete reboot went well.
But sadly still missing the new channels…

MickUrsell · December 7, 2018, 9:54am

Very strange, are you still getting the error message about the binding failing to install?
Sorry re-read, and saw the error had gone

MickUrsell · December 7, 2018, 10:04am

When you reinstalled the bindings what channels were listed in the events log?

brononius · December 7, 2018, 10:34am

No. I only have the error when I clear the cache.
So guess it’s an ‘issue’ with the bundle restarting without a present cache.

I see that all items are being linked with the channels.

log/events.log:2018-12-07 10:21:56.450 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_kelvin-seneye:monitor:5709eb0c:kelvin' has been added.
log/events.log:2018-12-07 10:21:56.488 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_Temperature-seneye:monitor:5709eb0c:temperature' has been added.
log/events.log:2018-12-07 10:21:56.525 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_par-seneye:monitor:5709eb0c:par' has been added.
log/events.log:2018-12-07 10:21:56.562 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_disconnected-seneye:monitor:5709eb0c:disconnected' has been added.
log/events.log:2018-12-07 10:21:56.594 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_NH4-seneye:monitor:5709eb0c:nh4' has been added.
log/events.log:2018-12-07 10:21:56.607 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_slideSerial-seneye:monitor:5709eb0c:slideserial' has been added.
log/events.log:2018-12-07 10:21:56.617 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_slideexpires-seneye:monitor:5709eb0c:slideexpires' has been added.
log/events.log:2018-12-07 10:21:56.617 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_lastreading-seneye:monitor:5709eb0c:lastreading' has been added.
log/events.log:2018-12-07 10:21:56.664 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_O2-seneye:monitor:5709eb0c:O2' has been added.
log/events.log:2018-12-07 10:21:56.665 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_outOfWater-seneye:monitor:5709eb0c:outofwater' has been added.
log/events.log:2018-12-07 10:21:56.668 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_NH3-seneye:monitor:5709eb0c:nh3' has been added. 
log/events.log:2018-12-07 10:21:56.680 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_PH-seneye:monitor:5709eb0c:ph' has been added.
log/events.log:2018-12-07 10:21:56.752 [.ItemChannelLinkAddedEvent] - Link 'mySeneye_lux-seneye:monitor:5709eb0c:lux' has been added.

MickUrsell · December 7, 2018, 10:39am

Maybe it was a timing issue when clearing the cache and restarting?
Do the new channels show in paper now? they are in the logs so hopefully they will!

brononius · December 8, 2018, 3:13pm

Found it!

Seems that an update of the binding was not enough.
I had to remove the thing from the paperUI, add it again.
Then, the new channels were present.

Thanks for you patience!

MickUrsell · December 8, 2018, 4:05pm

Glad its working, I have learned something new!
Hopefully others will see this post if they have similar problems and it will help them!

wborn · December 16, 2018, 8:38am

I’ve created an issue for this:

github.com/eclipse-archived/smarthome

SSE breaks due to BundleException in SseActivator.start() on first startup

opened 06:22PM - 15 Dec 18 UTC

closed 11:44AM - 01 Dec 19 UTC

wborn

When the runtime is started for the first time, sometimes the following exceptio…ns occur: ``` 18:16:48.496 [ERROR] [org.eclipse.smarthome.io.rest.sse ] - FrameworkEvent ERROR - org.eclipse.smarthome.io.rest.sse org.osgi.framework.BundleException: Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bundle org.eclipse.smarthome.io.rest.sse. at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:800) ~[?:?] at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) [?:?] at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933) ~[?:?] at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309) ~[?:?] at org.eclipse.osgi.container.Module.doStart(Module.java:581) ~[?:?] at org.eclipse.osgi.container.Module.start(Module.java:449) ~[?:?] at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468) ~[?:?] at org.eclipse.osgi.container.ModuleContainer.start(ModuleContainer.java:750) ~[?:?] at org.eclipse.osgi.container.ModuleContainer.applyDelta(ModuleContainer.java:741) ~[?:?] at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:511) ~[?:?] at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:457) ~[?:?] at org.eclipse.osgi.container.ModuleContainer.refresh(ModuleContainer.java:1001) ~[?:?] at org.eclipse.osgi.container.ModuleContainer$ContainerWiring.dispatchEvent(ModuleContainer.java:1382) ~[?:?] at org.eclipse.osgi.container.ModuleContainer$ContainerWiring.dispatchEvent(ModuleContainer.java:1) ~[?:?] at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?] at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?] Caused by: java.lang.LinkageError: ClassCastException: attempting to castbundleresource://31.fwk1468303011/javax/ws/rs/ext/RuntimeDelegate.class to bundleresource://31.fwk1468303011/javax/ws/rs/ext/RuntimeDelegate.class at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:146) ~[?:?] at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120) ~[?:?] at javax.ws.rs.core.MediaType.valueOf(MediaType.java:179) ~[?:?] at org.glassfish.jersey.media.sse.SseFeature.<clinit>(SseFeature.java:62) ~[?:?] at org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start(SseActivator.java:49) ~[?:?] at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) ~[?:?] at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) ~[?:?] at java.security.AccessController.doPrivileged(Native Method) ~[?:?] at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) ~[?:?] ... 15 more ``` ... ``` org.apache.karaf.features.internal.util.MultiException: Error restarting bundles: Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bundle org.eclipse.smarthome.io.rest.sse. at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1005) at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025) at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) Suppressed: org.osgi.framework.BundleException: Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bundle org.eclipse.smarthome.io.rest.sse. at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:800) at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309) at org.eclipse.osgi.container.Module.doStart(Module.java:581) at org.eclipse.osgi.container.Module.start(Module.java:449) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:402) at org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:161) at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1116) at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:997) ... 6 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.glassfish.jersey.media.sse.SseFeature at org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start(SseActivator.java:49) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) ... 16 more ``` As a result SSE doesn't work properly and updates aren't received by for instance Basic UI. When the runtime is restarted the exceptions no longer occur and SSE works properly. This is an old issue and has been around since at least August 2016, see this [community post](https://community.openhab.org/t/broken-my-openhab/12967?u=wborn). A community search shows [similar issue reports](https://community.openhab.org/search?q=org.eclipse.smarthome.io.rest.sse.internal.SseActivator%20order%3Alatest). Sometimes issues are opened for this in other repositories: * https://github.com/openhab/openhab-distro/issues/427 * https://github.com/openhab/openhab2-addons/issues/2003 Here's a [console.log](https://github.com/eclipse/smarthome/files/2682958/console.log) with Karaf debug logging enabled while reproducing the issue with openHAB 2.4.0.RC1.

scratch009 · December 20, 2018, 9:05am

I’m still can’t get this binding to work. I upgraded to stable 2.4 yesterday. uninstalled seneye binding, reinstalled, removed seneye thing in PaperUI and added it again. It shows online. My temperature gets pulled once, but then nothing is updated. I see all the channels in PaperUI but in Control screen all are empty (except temperature which is pulled once, but also seems old value). Then I get this error every time I change something in the config:

09:58:07.407 [WARN ] [e.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
09:58:08.177 [WARN ] [ommon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
        at org.openhab.binding.seneye.internal.handler.SeneyeHandler.newState(SeneyeHandler.java:70) ~[?:?]
        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) [?:?]

I’m curious on how the rest is able to get this working Do you guys create the thing via PaperUI or a seperate Things file? I used PaperUI at least.

MickUrsell · December 20, 2018, 1:55pm

Are you using username or email address to login?
I think email address is more reliable!
I use both Paperui definitions and some in items at present… I will be updating this to all in items as soon as I get chance

scratch009 · December 20, 2018, 3:04pm

I’ve only used email address + password for login, I must be doing something wrong since everybody succeeds but I don’t . The only thing that’s different now then before, my slide has expired last week, and haven’t replaced it yet. But now in the winter months I was planning on waiting for a bit. However, I don’t see why this shouldn’t work without an active slide. I get temperature updates via de login/app

MickUrsell · December 20, 2018, 5:49pm

Double check you have no old text file configs for this (.items, .things etc), or references in other config files.
The current binding should definitely work with expired slide, as I am using it like that at the moment.
Have you got a persistence service running that could have the old reading?
Do you mention/use the binding in any rules?
One other thing that is worth checking, is in a previous post; you hadn’t populated the location field in paperUI. It might be worth adding the location details, just to rule that out?