I have a Python program collecting data from api.sense.com via Sensible. As of about 2pm PT, the calls to API.SENSE.COM are all timing out with no response. I see this same thing when I ping api.sense.com from my cell phone or home network. But, the Sense App is working to see my current usage. Did the address of api.sense.com change lately? status.sense.com also doesn’t show an outage.
Any ideas?
kevin1
January 17, 2023, 11:36pm
2
I’m guessing this might be the issue ?
On November 28th, we will be updating our authentication practices to align with industry standards by removing historical support for non-expiring access tokens. Any existing tokens will be given 30 days before they expire at which point Sense will only issue a temporary access token along with a refresh token. Official Sense clients including the mobile and web apps will be unaffected, but unofficial community-developed scripts and clients may be affected.
The guys developing the information Sense API have fixed but it might require a small change to your code.
ps: I had some of my code time out as well, but I really haven’t looked carefully to see how to keep my auth tokens fresh.
It’s probably the API is just down. Happens sometimes.
The auth changes this month result in an unauthorized response (after 1 hour) not a timeout
1 Like
kevin1
January 18, 2023, 5:43pm
4
Good call - It looks like there was some kind of Authorization incident yesterday.
Thanks, all it started working an hour or so after I reported.
1 Like
system
Closed
January 18, 2024, 6:11pm
6
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.