-
-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Unable to add Tesla integration #46397
Comments
I had the same issue after the .3 patch - disabled 2fA on my Tesla account and was able to add the integration no problem. fwiw and fyi. |
Yes, I am using 2FA. Maybe there should be a warning that the integration doesn’t work if you utilize 2FA. |
Yes, MFA is unsupported. Feel free to update the documentation to indicate that. I'm working on a separate fix but it may not arrive for a while. The workaround others have been using is creating a separate account for HA to use itself without MFA. I'll probably put in a short term fix to make it an appropriate error message. |
Thanks for the update! Unfortunately the workaround is not possible for me because one of my cars is just an invite. I have updated the documentation. |
I get this error even without MFA. Tried 2 accounts already. |
Hi My Tesla integration was not working anymore, I've deleted the integration but I'm not able to add it again. "Failed to connect" |
After deletion and reboot I got it working. Mind the long update time, so you can't expect data to be collected directly if you don't set "wake on start-up". |
I've deleted the integration and can't add it back even after many restarts and 2 different accounts without MFA.
|
FYI I read on another site that Tesla deprecated user login for API access and now requires token generation - could that be related? Edit: v2 Tokens are deprecated as of 29 JAN | reference post on API v3 from teslafi https://support.teslafi.com/en/communities/1/topics/16979-tesla-v3-api-tokens are we using v2? Edit again: Yes @tbeloc that was my issue (sheepish) I was on 2021.2.2
I'm all good now! |
I have a potential fix for MFA that needs testing by advanced users in the linked PR. If you cannot figure out how to apply it yourself safely, please consider waiting till it's released. I will be fixing any bugs discovered but not to be too harsh, I won't be responding to questions on how to apply it. |
I had the same problem, I upgraded to the latest version and it works. |
Any update on releasing this ? |
For those who want to have help installing pending PRs for testing, I just released a custom component that helps simplify it. I am currently using that to use my PR in my production system because I enabled 2FA and apparently I can't figure out how to remove it from my account. |
Appears the error is back - was working fine with 2FA disabled, began receiving 'tuple index errors', uninstalled the integration and can't add it back (won't accept credentials). I think my error is the same as @oscfor:
|
+1 was working fine then 'tuple index error' removed and can't add it back (same error as above) |
+1 Core 2021.4.5. Used an earlier snapshot with Tesla integration installed. Same log messages and all data "unavailable". |
+1 Core 2021.4.5 seeing this issue as well |
+1, same here, tesla integration stopped working after upgrade to 2021.4.5. Tried removing it and re-adding it, "unknown error occured". |
Stopped working today 😥 |
Also stopped working today - no MFA. For me it may have been co-incident with an upgrade to 2021.4.6 from 2021.4.5, but in fairness I hadn't checked for this before the upgrade, so it could have just been waiting to fail on the next restart. |
2021.4.6 still has this error, re-adding integration won't help/work
|
I rolled back to 2021.4.3 from 2021.4.6 via snapshot restore and the issue went away. Going to hang here for a bit. I have a separate Tesla account I use for HA and 2fa is not enabled. My config has been solid since early January. EDIT...take that back. It worked for a few minutes and then stopped working. |
Debug log attached. Captured this right after restarting HA. Hoping someone can make some sense of it. |
Another debug log attached. I captured this one after removing the integration, restarting HA and then attempting to add again from the UI. Within the UI, I got an "Unknown error occurred" message when adding my email and password. Attached are the corresponding debug logs. HATeslaDebugLog - Attempt to add integration after removal-04-20-2021.txt |
yeah I'm running CORE 2021.2.3 and the integration stopped working w/o any updates |
Could this be related to that v2 Tokens are deprecated as of 29 JAN? here are the details on this https://support.teslafi.com/en/communities/1/topics/16979-tesla-v3-api-tokens |
@skynet01 I don't think that's the problem. See cdd7831, where support for v3 tokens was introduced (by updating |
I'm on Home Assistant 2021.4.6, same issue: Removed Tesla integration, restarted HA and tried to reinstall Tesla integration: |
Same exact situation for myself. |
You are correct. We already have oauth v3 tokens in teslajsonpy. We also have an explicit check on the tuple error people are seeing so updates will get a different error. However, that check won't necessarily help because Tesla is returning a 403 forbidden on the auth page. I'm stumped and so are others on why because it's random on which systems see it. You can try the closed PR and it may work for you. Or it might not. |
I subscribe cause I have same error. |
I'm getting the same errors as others - 'unknown error occurred'. |
I have nothing more to add apart from what's already been stated, the exact same problem here. |
Same problem overhere, will follow this thread for a solution |
Following for updates |
FFS. You don't need to comment in order to follow. And we know everyone has the same problem. I don't need to receive an email every time someone realizes their integration doesn't work. Comments are for contributions to a solution. If you don't have any new debug info. Use the subscribe button and the reaction emojis. |
resolved and being repackaged in the next days. Kudos to @alandtse |
Custom component is out. I may have to change the name since it conflicts with core. Use HACS to install. If you're replacing core, you will need to remove your existing core integration and add the custom component. This will force a new login using the new method. If you're using my Alexa Media Player component, make sure you've signed in recently to AMP as the login will be broken in AMP until the next release. |
Does it work with MFA also? /Nicklas |
Yes! Just set it up. Works like a charm. |
Is this going to be fixed in core as well? Or do we need to migrate to the custom component? |
AFAIK the workaround for authentication will not be accepted in HA Core. See #46558 (comment) |
There are 2 issues. One affects all auth and has been integrated into 2021.5 (#49939). The other affects only MFA and it looks like that won't be integrated because of the web scraping. So, if you aren't using MFA, things should be fixed with this month's release. |
Correct, we just merged in #49939 which will allow regular logins without MFA. However, MFA will not work unless you go to the custom component until someone implements it. I do not plan on doing that. |
The problem
When trying to add the new, fixed, Tesla integration I get: "Unknown error occurred". I have removed the old Tesla integration and restarted HA, but still the same error.
What is version of Home Assistant Core has the issue?
core-2021.2.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
tesla
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tesla/
Example YAML snippet
# Put your YAML below this line
Anything in the logs that might be useful for us?
The text was updated successfully, but these errors were encountered: