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

Change token #32

Open
seymourd opened this issue Oct 25, 2024 · 2 comments
Open

Change token #32

seymourd opened this issue Oct 25, 2024 · 2 comments

Comments

@seymourd
Copy link

Hello,

I had to generate a new token in order to add a new line as I lost the previous one.
Unfortunately the previous one got revoked, breaking all previous integrations.

How can I update the token in existing components ?

Thanks !

@seymourd
Copy link
Author

Bump :)

@drosoCode
Copy link
Member

Hi,
Sorry about the delay, but I currently have a very limited time to work on my projects.
Your problem could be solved by adding a Reauthentication step to the config flow, but unless someone opens a PR, this is pretty low in my priority list.
(on a sidenote: what I usually do with the websites that only allow generating one token per account is storing them in my password manager, so I can reuse them without having to replace everything that was using it).

A messy workaround would be to edit the system config files of home assistant (in the folder where you have your configuration.yaml file, you should also find a hidden folder: .storage, you could then edit the core.config_entries file in this folder and replace the api_token field for the idfm domains). I strongly recommend doing a full backup before trying this.

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

3 participants
@drosoCode @seymourd and others