Grohe Ondus: No automatic refresh

PottiMc · April 29, 2021, 5:56am

Hi,

I’m using the GroheOndus Binding together with my Grohe SenseGuard. I can login to my Grohe account and my binding is pulling the data from the API.

Unfortunately the binding is not pulling the data again in the polling time interval. I have to manually disable and activate the binding to pull the actual values (like you can see in the chart below).

I tried uninsalling and reinstalling the binding, did not help. Refresh token is set and account credentials are given.

All I can see in the log files is the following. The java error messages only show up at the first starting, after that, everything looks fine, bridge is online and SenseGuard too.

==> /var/log/openhab/openhab.log <==

2021-04-29 08:20:01.706 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from UNINITIALIZED (DISABLED) to INITIALIZING

2021-04-29 08:20:01.727 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from INITIALIZING to UNKNOWN

==> /var/log/openhab/openhab.log <==

2021-04-29 08:20:03.072 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:

java.lang.NullPointerException: null

at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.getRoom(GroheOndusBaseHandler.java:135) ~[?:?]

at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.getAppliance(GroheOndusBaseHandler.java:144) ~[?:?]

at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.updateChannels(GroheOndusBaseHandler.java:102) ~[?:?]

at org.openhab.binding.groheondus.internal.handler.GroheOndusAccountHandler.lambda$2(GroheOndusAccountHandler.java:154) ~[?:?]

at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?]

at java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1085) ~[?:?]

at org.openhab.binding.groheondus.internal.handler.GroheOndusAccountHandler.lambda$1(GroheOndusAccountHandler.java:151) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]

at java.lang.Thread.run(Thread.java:834) [?:?]

==> /var/log/openhab/events.log <==

2021-04-29 08:20:03.072 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from UNKNOWN to ONLINE

==> /var/log/openhab/openhab.log <==

2021-04-29 08:30:12.307 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler GroheOndusSenseGuardHandler of thing groheondus:senseguard:8a040c38be:e95c8f14-e75c-4aaa-bec5-a0767544612b tried accessing its bridge although the handler was already disposed.

2021-04-29 08:30:12.309 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler GroheOndusSenseGuardHandler tried updating the thing status although the handler was already disposed.

rockit4 · August 8, 2021, 8:53pm

Hi,

Did you solve this? I also have error messages and that the binding does not update every 15 min.

BR
Daniel

PottiMc · September 9, 2021, 5:13am

Actually no. Was not able to solve this issue.

PottiMc · January 31, 2022, 3:48pm

Hi,
I don’t know if you know it already, but the user seime fixed it really good, as mentioned in my GitHub issue here:

github.com/openhab/openhab-addons

[groheondus] No automatic refresh

opened 06:50AM - 29 Apr 21 UTC

PottiMc

bug

## Expected Behavior The Grohe Ondus Binding should refresh every 15 minutes (9…00s) as polling interval. ## Current Behavior The binding is only refreshing when disabled and enabled again. Values are different from Grohe Sense Android App. I tried uninsalling and reinstalling the binding, did not help. Refresh token is set and account credentials are given. All I can see in the log files is the following. The java error messages only show up at the first starting, after that, everything looks fine, bridge is online and SenseGuard too. > ==> /var/log/openhab/openhab.log <== > > 2021-04-29 08:20:01.706 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from UNINITIALIZED (DISABLED) to INITIALIZING > > 2021-04-29 08:20:01.727 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from INITIALIZING to UNKNOWN > > ==> /var/log/openhab/openhab.log <== > > 2021-04-29 08:20:03.072 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: > > java.lang.NullPointerException: null > > at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.getRoom(GroheOndusBaseHandler.java:135) ~[?:?] > > at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.getAppliance(GroheOndusBaseHandler.java:144) ~[?:?] > > at org.openhab.binding.groheondus.internal.handler.GroheOndusBaseHandler.updateChannels(GroheOndusBaseHandler.java:102) ~[?:?] > > at org.openhab.binding.groheondus.internal.handler.GroheOndusAccountHandler.lambda$2(GroheOndusAccountHandler.java:154) ~[?:?] > > at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?] > > at java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1085) ~[?:?] > > at org.openhab.binding.groheondus.internal.handler.GroheOndusAccountHandler.lambda$1(GroheOndusAccountHandler.java:151) ~[?:?] > > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?] > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] > > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?] > > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] > > at java.lang.Thread.run(Thread.java:834) [?:?] > ==> /var/log/openhab/events.log <== > > 2021-04-29 08:20:03.072 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘groheondus:account:8a040c38be’ changed from UNKNOWN to ONLINE > > ==> /var/log/openhab/openhab.log <== > > 2021-04-29 08:30:12.307 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler GroheOndusSenseGuardHandler of thing groheondus:senseguard:8a040c38be:e95c8f14-e75c-4aaa-bec5-a0767544612b tried accessing its bridge although the handler was already disposed. > > 2021-04-29 08:30:12.309 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler GroheOndusSenseGuardHandler tried updating the thing status although the handler was already disposed. > ## Steps to Reproduce (for Bugs) 1. Fresh install of binding 2. Enter account data 3. Add SenseGuard device ## Your Environment OpenHab 3.0.2 (Issue was in former 3 versions too, didn't test on OH2) RaspberryPi4B

There you can find a pre-release version which works pretty well for me.

ariela · February 25, 2022, 9:52pm

Hello all,

I’m quite interested in purchasing a Grohe Sense Guard, and I would like to know if now it should be correctly integrated in my OH3.

Any suggestion would be appreciated

thanks
Andrea

PottiMc · March 3, 2022, 6:39am

Hi ariela,

yes, it can be correctly integrated. It’s still work in progress since the original programmer of the binding didn’t continue to develop, but the binding works 98% of the time, sometimes you just have to restart it.

The good thing is you can use other water sensors (in my case Homematic) and connect it to your Sense Guard to switch off the valve.

Here is what I see:

ariela · March 3, 2022, 8:48pm

Thank you @PottiMc

What is the issue behind that 2%? is there someone working on it?

PottiMc · March 4, 2022, 7:00am

As I said, it works most of the time, sometimes (and I mean maybe once a week or less) it can crash and then you simply just have to restart the thing.

I have an issue on github mentioned above in this thread and the developer @seime is working on it and is publishing beta versions on his git. I guess the final changes will take place in OH3.3 (but I don’t know that for sure).