The refreshtoken is stored via the new libraries. To initial connect only the authcode is needed. So it’s not needed to set in in a things file if a textual configuration is used. I removed the refresh token from the thing. If you have a thing created via PaperUI it probably still has this property, but if you would recreate the thing via PaperUI. I did not anticipate the option to configure the refreshtoken as it is all handled by the new library and I assume having an authcode should be sufficient.
So it should work if you set the one time authcode. and then you can remove the code (if you do a textual configuration. for things created with PaperUI with an auth code set, it will be removed after getting a refresh token.)
Thank you for this quick reply - I use textural configuration and it seems to work fine.
The migration from the old binding to the new went quite easy.
If you need further information about the API you can contact me at any time - I have been the contact regarding the Livisi API for @oliver_kuhl and may provide some help/details if needed.
As far as I know innogy drops connection to openhab every 6 hours.
In the logs I can see that there seem to be exceptions occuring. This causes no communication between openhab and innogy for approx 15min. After that the binding fully recovers until it occurs again.
I have seen this only with the new binding for the SHC2.0. The old binding for SHC 1.0 did not show this behaviour.
I have 2 sample trace files and I know the timestamp of the exception.
As I better do not touch source code: Who would be willing to look at this?
I then make the traces available to that user.
Important notice: I’ve created a pull request (PR #6389) of the updated binding. It’s my intention to get this binding in the upcoming openHAB 2.5.0 release. So it should be great to make sure that the binding works correctly. A number of you have already provided feedback. So if you haven’t tried it yet or did try but don’t have the latest version (15/11/2019) yet, you can download the jar of the binding here: https://github.com/Hilbrand/openhab2-addons/releases/tag/innogy It should work on openHAB 2.4 and 2.5
just to let you know: the button-press behavior changed. Now every button press (not only the first) fires two button-pressed events as well as a button press that wasn’t pressed. In this case on the device (dimmer switch) I was controlling with “button1”. If I control another device with no buttons, no additional button pressed event fires.
This is when you press a button on the device, right? Can you log with trace level some time before and after the press and send the log to me via direct message. I’ll have a look and see if Ican find what is going on.
I recognized that the binding uses invertValueIfConfigured for the values of the CHANNEL_ROLLERSHUTTER.
As my home is configured to use 100% as “closed” and 0% as “open” I would really need to use this setting - but I was not able to find the corresponding config for the binding or the Rollershutter-Thing.
Could you provide some information on how to use the invert on ISR2? I know that some other bindings support the invert for shutter devices.
I’ve updated the binding on the location mentioned above (20/11/2019 15:00). I’ve added a channel option invert to the rollershutter channel. If you configure it with true it will work with 100% closed 0% open. Btw ON/OFF is not a valid state for rollershutters so I’ve changed this to UP/DOWN.
this behaviour comes from a change made by me.
before my Change the Event was only fired when different Buttons are pressed. i think there is a bug in the innogy-api because pressing buttons are not handled correct in the innogy-app too.
i have reported a bug at innogy but i have no Feedback from them.
perhaps somebody can do a Workaround…i was not able to…
I will update my binding tomorrow and test the channel option. I assume it needs to be applied like this: Thing ISR2 Shutter_Some "Shutter" @ "Room" [ id="blablablubs", invert=true ]
I did some investigating with Hilbrand. He was able to fix the button-press issue. With the updated binding everything works fine for me. Even long presses. Thank you again for that.
