Tado: Device Tracker not working, no entities created

[sakara]

The problem

Device Tracker not working, no entities created.

Environment

• Home Assistant Core release with the issue: 0.118.3
• Last working Home Assistant Core release (if known): not known
• Operating environment (OS/Container/Supervised/Core): HassOS 4.17, Docker Ver 19.03.12, Supervisor Ver 2020.11.0
• Integration causing this issue: tado
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/tado

Problem-relevant configuration.yaml

device_tracker:
  - platform: tado
    username: !secret tado_username
    password: !secret tado_password
    home_id: !secret tado_homeid

Traceback/Error logs

Dettagli registro (WARNING)
Logger: homeassistant.components.tado.device_tracker
Source: components/tado/device_tracker.py:118
Integration: Tado (documentation, issues)
First occurred: 9:42:40 (1 occurrences)
Last logged: 9:42:40

Error 401 on https://my.tado.com/api/v2/homes/{home_id}/mobileDevices?username={username}&password={password}

Additional information

2020-11-26 15:46:50 WARNING (MainThread) [homeassistant.components.tado.device_tracker] Error 401 on https://my.tado.com/api/v2/homes/{home_id}/mobileDevices?username={username}&password={password} 2020-11-26 15:46:50 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform legacy

[probot-home-assistant[bot]]

tado documentation tado source _{^{(message by IssueLinks)}}

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[sakara]

I'm still having problems and device tracking don't work with latest version of HA. It doesn't resolve the issue, so don't close this IMPORTANT issue about an unresolved problem.

[sakara]

No news about tracking?

[gergtreble]

Having the same issue. Just migrated from Smarthings (where this feature worked). Anything that can be done? Looks like a change to the Tado API auth has caused this.

[sakara]

2021.5.0 and still no solutions...

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[sakara]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

As you can see, this is not solved in Home Assistant 2021.7.4... Logger: homeassistant.components.tado.device_tracker Source: components/tado/device_tracker.py:118 Integration: Tado (documentation, issues) First occurred: 3 agosto 2021, 18:32:01 (1 occurrences) Last logged: 3 agosto 2021, 18:32:01

Error 401 on https://my.tado.com/api/v2/homes/{home_id}/mobileDevices?username={username}&password={password}

---

Logger: homeassistant.components.device_tracker Source: components/device_tracker/legacy.py:271 Integration: Localizzatore di dispositivi (documentation, issues) First occurred: 3 agosto 2021, 18:32:01 (1 occurrences) Last logged: 3 agosto 2021, 18:32:01

Error setting up platform legacy tado

[limeryls]

Hi ! Issue still unfixed in core-2021.11.1 my.tado.com API uses an OAuth token for authentication, that's why the credentials does not work anymore in url.

If some guys have the motivation in order to fix this issue, I think it's a good documentation here: https://shkspr.mobi/blog/2019/02/tado-api-guide-updated-for-2019/

[whatdaybob]

I had it working briefly somehow on 2021.12.1 I was messing with unifi device trackers and played with the known_devices.yaml, saw the old non working ones in there and deleted them out. Weirdly on next restart it appeared to be working and populated the known devices again. Unfortunately I restarted a couple of more times and can't emulate what I did before to get it working again and am just seeing the errors everyone else gets.

[Jayksopp]

I have the same problem Error 401 on https://my.tado.com/api/v2/homes/{home_id}/mobileDevices?username={username}&password={password}

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[tigro7]

I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use?

[sakara]

I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use?

let it go... they won't respond... it seems no one cares about bugs about TADO integration.

[tigro7]

Hi Sakara! I resolved it, by changing my password and replacing an ‘&’ character…

Da: Sakara @.> Data: lunedì, 28 novembre 2022 14:12 A: home-assistant/core @.> Cc: Alberto Tiribelli @.>, Comment @.> Oggetto: Re: [home-assistant/core] Tado: Device Tracker not working, no entities created (#43627)

I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use?

let it go... they won't respond... it seems no one cares about bugs about TADO integration.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/43627#issuecomment-1329069459, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACJRNN2CRAIPIAL4IHJ7FPDWKSVUBANCNFSM4UCGPX3A. You are receiving this because you commented.Message ID: @.***>

[sakara]

Hi Sakara! I resolved it, by changing my password and replacing an ‘&’ character… Da: Sakara @.> Data: lunedì, 28 novembre 2022 14:12 A: home-assistant/core @.> Cc: Alberto Tiribelli @.>, Comment @.> Oggetto: Re: [home-assistant/core] Tado: Device Tracker not working, no entities created (#43627) I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use? let it go... they won't respond... it seems no one cares about bugs about TADO integration. — Reply to this email directly, view it on GitHub<#43627 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACJRNN2CRAIPIAL4IHJ7FPDWKSVUBANCNFSM4UCGPX3A. You are receiving this because you commented.Message ID: @.***>

Oh thank you, i will try to do so. :)

[Jayksopp]

Hi Sakara! I resolved it, by changing my password and replacing an ‘&’ character… Da: Sakara @.> Data: lunedì, 28 novembre 2022 14:12 A: home-assistant/core @.> Cc: Alberto Tiribelli @.>, Comment @.> Oggetto: Re: [home-assistant/core] Tado: Device Tracker not working, no entities created (#43627) I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use? let it go... they won't respond... it seems no one cares about bugs about TADO integration. — Reply to this email directly, view it on GitHub<#43627 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACJRNN2CRAIPIAL4IHJ7FPDWKSVUBANCNFSM4UCGPX3A. You are receiving this because you commented.Message ID: @.***>

Can you provide more details? What do you mean by "replacing an ‘&’ character". Where did you replace it?

[tigro7]

My password contained an '&' character, so i changed my password in order to include only 'non-&' symbols. Changed it on Tado, changed it on Homeassistant and now it works.

Il giorno mar 29 nov 2022 alle ore 09:16 Jayksopp @.***> ha scritto:

Hi Sakara! I resolved it, by changing my password and replacing an ‘&’ character… Da: Sakara @.> Data: lunedì, 28 novembre 2022 14:12 A: home-assistant/core @.> Cc: Alberto Tiribelli @.>, Comment @.> Oggetto: Re: [home-assistant/core] Tado: Device Tracker not working, no entities created (#43627 https://github.com/home-assistant/core/issues/43627) I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use? let it go... they won't respond... it seems no one cares about bugs about TADO integration. — Reply to this email directly, view it on GitHub<#43627 (comment) https://github.com/home-assistant/core/issues/43627#issuecomment-1329069459>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJRNN2CRAIPIAL4IHJ7FPDWKSVUBANCNFSM4UCGPX3A. You are receiving this because you commented.Message ID: @.***>

Can you provide more details? What do you mean by "replacing an ‘&’ character". Where did you replace it?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/43627#issuecomment-1330248080, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJRNNZDYNQDAG4POIIWFZ3WKW3W7ANCNFSM4UCGPX3A . You are receiving this because you commented.Message ID: @.***>

[sakara]

My password contained an '&' character, so i changed my password in order to include only 'non-&' symbols. Changed it on Tado, changed it on Homeassistant and now it works. Il giorno mar 29 nov 2022 alle ore 09:16 Jayksopp @.> ha scritto: … Hi Sakara! I resolved it, by changing my password and replacing an ‘&’ character… Da: Sakara @.> Data: lunedì, 28 novembre 2022 14:12 A: home-assistant/core @.> Cc: Alberto Tiribelli @.>, Comment @.> Oggetto: Re: [home-assistant/core] Tado: Device Tracker not working, no entities created (#43627 <#43627>) I have the same error: It seems like ha doesn't compile the correct information in the URL, but leaves the placeholder as {home_id}, {username}, {password}. Is it there a way to format the data inputs that we didn't use? let it go... they won't respond... it seems no one cares about bugs about TADO integration. — Reply to this email directly, view it on GitHub<#43627 (comment) <#43627 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJRNN2CRAIPIAL4IHJ7FPDWKSVUBANCNFSM4UCGPX3A. You are receiving this because you commented.Message ID: @.> Can you provide more details? What do you mean by "replacing an ‘&’ character". Where did you replace it? — Reply to this email directly, view it on GitHub <#43627 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJRNNZDYNQDAG4POIIWFZ3WKW3W7ANCNFSM4UCGPX3A . You are receiving this because you commented.Message ID: @.*>

It worked! Thank you! 😄

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.