sk
Comments
Recent activity by sk
-
@Leslie: Yes, problem solved. :o)
- View comment
- 1 vote
-
It's strange, but sometimes just 7 hours of sleep help: without having changed anything in the code, everything is now working smoothly again. The problem where authentication on one device cancell...
- View comment
- 0 votes
-
Also, when refreshing the token manually, I have been asked to re-authorize the app each time, which I'm not sure is the way it behaved in the past. I am also seeing this behavior. Once you try t...
- View comment
- 0 votes
-
I am also doing it like that and it works fine on one device, but once another device requests authorization, the first one gets unauthorized and the access_token is invalidated. And the other way ...
- View comment
- 0 votes
-
Yes, it's maddening, that is for sure. I spent 10 hours today on debugging this, no solution so far.
- View comment
- 0 votes
-
I think this is the cause of the problem: the authorisation is only ever valid on one device and expires as soon as a second device uses the same app with the same netatmo account. So here we now h...
- View comment
- 0 votes
-
@David: can you confirm that the access_token expires as soon as you run your programme with an authorisation for one and the same netatmo account on more than one device? My guess is: not only wit...
- View comment
- 0 votes
-
I carried out further tests and found that if an app is running on two devices, the access_token on one device invalidates that of the other device. Since both devices are not necessarily connected...
- View comment
- 0 votes
-
Have sent you a message. I doubt I am the only one with this issue, see messages above by 'David': "Each time I refresh the token manually, it asks me to reauthorize the app. This, also, is unusual."
- View comment
- 1 vote
-
I ran some more tests and found that the access_token always expires about 10 to 20 minutes after refresh or generation, not 3 hours. During that period no token refresh has been initiated by my co...
- View comment
- 1 vote