[tado] Tado Bridge Thing not connecting > Error calling https://auth.tado.com/oauth/token

[oosidhu]

My Tado bridge Thing stopped connecting yesterday. All other external connections from OpenHAB are working. I can ping auth.tado.com on the host machine.

Expected Behavior

It has been working since I upgraded to openHAB 4.3.3. The heating switched on during the morning and I lost the connection midday 21/MAR/25.

Current Behavior

The following error is returned when the bridge Thing tries to connect.

COMMUNICATION_ERROR
Could not connect to server due to Error calling https://auth.tado.com/oauth/token

Possible Solution

This article indicates that there was a change in Tado authentication yesterday. https://community.tado.com/en-gb/discussion/8/tado-api

It could be a coincidence, however I am posted here hoping someone can confirm if an update is needed to the Binding or if I need to investigate my setup locally further.

Steps to Reproduce (for Bugs)

Restart Openhab and check if the Tado binding is connecting

Context

Unable to control Tado devices and receive data

Your Environment

openHAB 4.3.3 running on Raspberry PI4

[andrewfg]

Resolved by #18354 (please check and confirm)

[oosidhu]

hi @andrewfg , this appears to be just what I need, it's a shame Tado do not send out any notifications about changes. I've not applied updates from the Github repo directly before, so lacking some knowledge. Could you point me to the updated JAR file or any guidance of how to update my Tado Add-On using the updated files from the repo. Thank you.

[andrewfg]

The change is quite difficult. The updated Tado binding depends on an update in OH Core. And the core update is only in OH v5.x Snapshot. So that means not only updating the one binding, but actually updating your whole system. Which you may not want to risk. So in order to make it easier for users like you, I will ask OH maintainers if they can Cherry Pick the changes back into OH 4.x

[oosidhu]

My system is fully patched via the openhabian-config to 4.3.3. I agree, there is risk that something else may break moving to 5.0.0-SNAPSHOT. I have a dev instance that I could test the new binding and OH5 on. Will I pick-up your Tado binding changes automatically by moving to this OH build?

[andrewfg]

@oosidhu the fixes to OH Core and the tado binding are being cherry picked (back ported) into OH 4.3.x .. so it will probably be in the next Snapshot release (and subsequent stable patch releases)

EDIT it will be in the next snapshot after PR #18433 will have been merged.

[oosidhu]

@andrewfg that's great, thanks for your work on this. I'll keep an eye on PR #18433 .

[dandjo]

Had the same issue, can confirm it is fixed in Version 5.0.0~S4554-1.

[oosidhu]

@dandjo thanks for confirmation. I was waiting for the 4.3.x patch release, I use openhabain-config to upgrade. Out of interest, where did you download Version 5.0.0~S4554-1 from and did you upgrade the system on command line?

[dandjo]

@oosidhu I use APT with "unstable" Suite for handling versioning of my system. Basically I was upgrading to 5.0.0-M1 from 4.3.x, but that was smooth. Did not have to manually upgrade things, but this only applies to my installation. Since there are some crucial bugfixes since M1 I upgraded to the latest "unstable", which is S4554 in this case.

[andrewfg]

I was upgrading to 5.0.0-M1 from 4.3.x, but that was smooth.

Did you use openhabian? And did you also upgrade Java from v17 to v21 by the sane means?

[dandjo]

@andrewfg Yes. Openhabian with Java 21. The upgrade process:

• Shutdown openhab service
• Upgrade Java
• Upgrade OpenHAB
• Start openhab service

[oosidhu]

@dandjo thanks for the details. If the patch is not available soon, I'll try your method. I've reverted to using the Tado app as a workaround, however it is not adaptive and efficient as the scripted heating controls I have in place via Openhab.