Currently, every scheduled start there is a login (and since October a logout) of the ryd user account.
This PR adds the ability to reuse the authentication token.
when the authToken is not present, login is triggered
every next schedule, the auth token is used for the session
if the authToken gets invalid, login is triggered again in the next schedule
In general it mimics the apps behaviour way more, as the session stays the same with all requests
Currently this PR runs in my installation with a schedule of 3 minutes, none of my phone sessions have been terminated yet. I also tested invalidating the auth token (injecting in https://rydpay.thinxcloud.de/ and logging out), relogin also works.
I'd let it run some more days before eventually merging, just wanted you to have a look at it.
Currently, every scheduled start there is a login (and since October a logout) of the ryd user account. This PR adds the ability to reuse the authentication token.
In general it mimics the apps behaviour way more, as the session stays the same with all requests
Currently this PR runs in my installation with a schedule of 3 minutes, none of my phone sessions have been terminated yet. I also tested invalidating the auth token (injecting in https://rydpay.thinxcloud.de/ and logging out), relogin also works.
I'd let it run some more days before eventually merging, just wanted you to have a look at it.
Best, Leo