Skip to content

feat!: WIP: support for device code authentication scheme - #232

Draft
easimon wants to merge 1 commit into
masterfrom
feat/device-code-grant
Draft

feat!: WIP: support for device code authentication scheme#232
easimon wants to merge 1 commit into
masterfrom
feat/device-code-grant

Conversation

@easimon

@easimon easimon commented Mar 24, 2025

Copy link
Copy Markdown
Owner

No description provided.

@easimon
easimon force-pushed the feat/device-code-grant branch 2 times, most recently from 8317d9a to aa1e0b2 Compare April 13, 2025 16:13
@easimon
easimon force-pushed the feat/device-code-grant branch from aa1e0b2 to cf32d6f Compare April 13, 2025 16:16
@barcar

barcar commented Jun 21, 2026

Copy link
Copy Markdown

I realise that it's been a while but is this PR a working fix for the authentication issues?

@easimon

easimon commented Jun 21, 2026

Copy link
Copy Markdown
Owner Author

Not really. Never had this working stable for more than a few days, and grabbing the required device code from the logs was very uncomfortable at best.

And meanwhile, Tado also started to impose an API rate limit, which adds another "authentication error" when you hit it, and does not allow for more than one update every 15-30 minutes or so. So I basically gave up for now, not sure if I will revive this effort at some point. Probably not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants