Seneye Binding

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

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

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

Sure, here we go:

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

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

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

hmmm, no luck.
I tried following:

  1. uninstall binding (through paperUI)
  2. stop OH2
  3. Cleared the cache
  4. start OH2
  5. 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 of bundle

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

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

smarthome io rest SSE internal error

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…

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

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

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.

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!

Found it! :wink:

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!

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

I’ve created an issue for this:

1 Like

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( ~[?:?]
        at org.openhab.binding.seneye.internal.SeneyeService.lambda$0( ~[?:?]
        at java.util.concurrent.Executors$ ~[?:?]
        at java.util.concurrent.FutureTask.runAndReset( ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?]
        at java.util.concurrent.ThreadPoolExecutor$ [?:?]
        at [?:?]

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

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

I’ve only used email address + password for login, I must be doing something wrong since everybody succeeds but I don’t :roll_eyes: . 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

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?