Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to change access token via integration reconfiguration #120

Open
3 tasks done
KrzysztofHajdamowicz opened this issue Jul 29, 2024 · 1 comment
Open
3 tasks done

Comments

@KrzysztofHajdamowicz
Copy link

Checklist

  • I have filled out the template to the best of my ability.
  • This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
  • This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

I'm getting errors every few hours that Teslemetry integration failed and access token is invalid: Config entry 'Teslemetry' for teslemetry integration could not authenticate: Invalid access token.
When I click a button to reauth/reload integration, it works for another few hours.

Describe the solution you'd like

I'd like to have a possibility to enter new access token via integration reconfiguration instead of removing current one and adding new integration instance.

Additional context

Logger: custom_components.teslemetry
Source: helpers/update_coordinator.py:365
integration: Teslemetry
First occurred: July 28, 2024 at 07:58:50 (3 occurrences)
Last logged: 13:04:53

    Authentication failed while fetching Teslemetry Vehicle data: Invalid access token.
    Authentication failed while fetching Teslemetry Energy Site Live data: Invalid access token.
@Bre77
Copy link
Member

Bre77 commented Jul 29, 2024

This issue was caused by a server-side issue. You will be given the option to change the authentication token if it is still invalid at the time you perform a re-auth.

⚠️ Between 9:11 AM and 10:52AM UTC the Teslemetry authentication service experienced some short interruptions, which may have cause the Home Assistant integration to trigger re-authentication. I am aware of the cause and will put measures in place that should help avoid this happening in the future.

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

No branches or pull requests

2 participants