Code 403 on getEnergyIQ

[dudz40]

since a couple of days i am getting a 403 on the getEnergyIQ call. Any other reports?

[mattdavis90]

No other issues have been raised. There was mention of Tado changing how authentication works but I rolled out an update that should have fixed that. They removed basic Auth from all endpoints and require JWT, which should now be the case for this library as well.

This isn't an API call I personally use, so it is also possible that Tado changed the API call. Are you still able to access the data in the app and web browser? If you can then we should be able to see the new API call in developer tools.

[mattdavis90]

I misremembered the JWT and Auth fixes were for AirConfort - 03e5a81

[dudz40]

Will have a check as I saw auth related things in the error. Martin Verbeek Op do 11 jan 2024 08:50 schreef Matt Davis ***@***.***>:

…

I misremembered the JWT and Auth fixes were for AirConfort - 03e5a81 <03e5a81> — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APWNYU4L4L7DWIOAVQJ55BLYN6KV5AVCNFSM6AAAAABBWA5F5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWGUZTKOJYGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dhavalsalwala]

I think tado has changed API URL. For me this works via the rest client,

https://energy-insights.tado.com/api/homes/123456/consumptionOverview?month=2024-07&country=IE

[mattdavis90]

That looks like a totally different endpoint - probably worth implementing that as well but it doesn't have the same response as the original endpoint. I don't really use the EnergyIQ stuff in Tado so there isn't much data in my account to test with but as far as I can tell there isn't a direct replacement for the older endpoint. I'll look to include the overview endpoint and remove the old function call.

[mattdavis90]

This is now pushed up into v0.16.0

[mattdavis90]

The API call is getEnergyIQOverview and I've removed the broken API call

[dhavalsalwala]

Thanks @mattdavis90 . I will test the new API.