Tried to download the latest verion I could find, cleared cache (!) created a new thing…
Currently running verison:
261 | Active | 80 | 2.5.0.201904031156 | Seneye Binding
Error log at start… (why can’t those java guys create better error logs? ):
2019-04-03 16:57:23.657 [WARN ] [.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
2019-04-03 16:57:24.708 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
at org.openhab.binding.seneye.internal.SeneyeService.initialize(SeneyeService.java:121) ~[?:?]
at org.openhab.binding.seneye.internal.handler.SeneyeHandler.initializeSeneyeService(SeneyeHandler.java:132) ~[?:?]
at org.openhab.binding.seneye.internal.handler.SeneyeHandler.lambda$0(SeneyeHandler.java:126) ~[?:?]
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) [?:?]
— edit —
It seems to work after a reboot of the server?
grep Botje log/events.log| grep _Tem
2019-04-03 17:32:19.529 [.ItemChannelLinkAddedEvent] - Link 'BotjeVijver_Temperature-seneye:monitor:062cdb09:temperature' has been added.
2019-04-03 17:32:19.572 [.ItemChannelLinkAddedEvent] - Link 'BotjeAqua_Temperature-seneye:monitor:3a5e1334:temperature' has been added.
2019-04-03 17:32:28.181 [vent.ItemStateChangedEvent] - BotjeAqua_Temperature changed from NULL to 24.6
2019-04-03 17:32:29.749 [vent.ItemStateChangedEvent] - BotjeVijver_Temperature changed from NULL to 14.4
2019-04-03 17:42:29.240 [vent.ItemStateChangedEvent] - BotjeAqua_Temperature changed from 24.6 to 24.5
2019-04-03 18:12:32.266 [vent.ItemStateChangedEvent] - BotjeAqua_Temperature changed from 24.5 to 24.6
2019-04-03 18:42:37.175 [vent.ItemStateChangedEvent] - BotjeAqua_Temperature changed from 24.6 to 24.5
A bit odd is that it only gets the data every 30 mintues?
And in PaperUI, I’ve got 5 minute pol interval?
Or is this linked with the update in the seneye app itself?
My Pond sensor only gets the data in the beginning?
Maybe linked because I don’t have an active slide in it?
Slide will be for the upcoming weeks, first I need to put some cables in place for it.
But when I check the site https://api.seneye.com/v1/devices/?IncludeState=1&user=XXX&pwd=YYYY , I’m getting the temperature value? So strange that it wouldn’t be imported in openHAB?
I believe the problem both you and scratch009 are having is being caused by the original design of the binding.
I believe that the binding is trying to pull values that don’t exist on the Koi/pond sensor and the binding is not able to read/handle the Null value.
I have tried to re-write the Binding but have struggled to work out some of its original design.
I am therefore writing this again from scratch, however progress is very slow at the moment due to other commitments.
I will try to get something to test as soon as possible.
I believe the 30min data updates is caused by the Sensor uploading every 30 mins.
You could try forcing the sensor to carry out an extra update to see what happens but I think this is down to the sensor itself.
Let me know if you want some help with testing.
Or if you want my login for seneye (with reef and pond SUD), no prob to give this.
ps would be nice to have the values pulled without an active slide. This way, we can have some rules ourself to get us warned (water loss, temperature high…)
I believe the problem is the binding is looking for a nh4 channel, but this is not supported by the pond sensor.
I have tried to just edit the binding so that channel is optional but this isn’t working.
I looks like this issue is they way the Binding was designed to carry out the error checking.
I am currently rewriting the binding (this should also include some other tweaks) unfortunately this is a very slow progress.
Finally an update,
I am having some problems uploading this to the main build, so have dropped it on my old website for testing.
Feel free to download and test (please feed back results both good and bad) Seneye Binding
To test please delete current Seneye things and uninstall the Seneye binding.
Download the new binding and drop it into the addons folder.
Re-add your Seneye devices
Good Luck!
Many thanks for testing it, glad it appears to be working better.
The real only change to this version is that it looks at the type of sensor (pond, Reef or Home) then just processes the required fields.
Previous it always tried to return every reading, even if the sensor did not support it.
This isn’t a perfect fix as I’m not sure what will happen if a sensor is upgraded, etc.
Also the coding for this is a bit rough and ready!
I was hoping to do a lot more but just couldn’t get it all working.
If you see anything that needs correcting or adding please let me know.
I probably won’t try another big refresh until we have OpenHAB 3.0 but will bug fix and try little upgrades if needed before then.
hmm, Guess I yelled to soon.
After removing my things (I missed this part), and rebuilding them, it seems that it’s not been automaticlly refreshed? Or at least the 5 minutes don’t do much during the last 20 minutes.
When I restart the binding manually, some items are refreshed, but not all?
All my items are linked properly (when I check this in paperUI).
leave it running for 30 mins and post the results, the debug results normally appear in the openhab.logs file.
Can you also post the associated events.log
By default the seneye sensor only uploads data to the internet every 30 mins. I’m not sure if this is something that can be changed, as this has been set by Seneye.
The binding will pull data from the cloud at whatever rate you configure at setup but the data will be the same until the sensor next upload, I hope this makes sense.
That’s looking good at the moment, you are right it will only report the reading has updated, if the reading is different.
Then you will see what the reading changed from and to.
Keep an eye on it and see what happens.
Might be worth giving it a day or so and comparing it to the official Seneye dashboard but I think it is updated correctly.
Maybe one remark? Seems that the slide serial isn’t coming in at this point.
In a week I need to change the slides, so propably he’ll then pick it up? But maybe you could push it that he pulls the data fe once a day?
And not sure if it’s possible. But maybe you can only show the channels that are really used?
fe I believe that with the pond, you can only read NH3? And you need to buy an upgrade to have the LUX/PAR/Kelvin options.
Thanks for the feedback it’s really helpful.
I believe the update should be Officially included in the next milestone build of OpenHAB.
I have been looking and currently can see a reason for it not pulling the serial number!
I will keep looking and see what I can find.
I would be grateful if you can let me know what happens when you change slides!
I plan to only show the available channels in the OpenHAB 3.0 version as this requires a lot more work.
Keep the feedback and suggestions coming it is very helpful.
Changed my slides today, and after about 30 minutes, the dates have been updated in OH.
But the serial stays empty. So the ‘change’ hasn’t been noticed.
Not a big deal of course, since I don’t see any reason why we would like to remember the serial.
Thanks for the info, can you upload a copy of the logs for the time the date of the slide updated.
This might help me identify the problem with the serial number.
Nevermind. Was an error on my side. Seems I forgot to add the [%s] to my item…
And worse, I was to lazy to check the logs, else I would have noticed it. Sad how much you rely on the sitemap. Like everything will be handled automaticlly by the computer. It’s just not like in the commercials…
log/events.log.7:2020-06-01 17:29:56.079 [vent.ItemStateChangedEvent] - BotjeVijver_slideexpires changed from 2020-06-02T11:39:15.000+0200 to 2020-07-01T17:27:15.000+0200
log/events.log.7:2020-06-01 17:29:56.079 [vent.ItemStateChangedEvent] - BotjeVijver_slideSerial changed from U71SU623PK8 to N34EV366KG4
log/events.log.7:2020-06-01 17:31:15.124 [vent.ItemStateChangedEvent] - BotjeAqua_slideexpires changed from 2020-06-02T11:39:58.000+0200 to 2020-07-01T17:26:43.000+0200
log/events.log.7:2020-06-01 17:31:15.125 [vent.ItemStateChangedEvent] - BotjeAqua_slideSerial changed from L27HS836MX2 to K17KC688EM1
With other words, this binding is working perfectly for me.
Thank you very much !!!
If I can do anything for you to test or so, let me know!
OpenHAB 2.5.6-2 includes the latest version of the Seneye binding, So no need to have a separate copy in the addons folder
For best results delete the current things and uninstall the current binding before upgrading to OpenHAB 2.5.6-2.
Then reinstall and configure.
):
