same here:-(
1 Like
Hello,
I had the same problem. In my configuration.yaml i had setup my internal and external address. I disabled it with # in front, restart home assistant and now i got the login mask. I hope it helps you.
best regards
Peer
1 Like
What, exactly, did you remark out? What did you put the # in front of?
i marked i out in my config.yaml like this:
# external_url: "https://xxxxxxxxxxxx.net:xxxxx"
# internal_url: "https://192.xxx.xxx.101:8123"
After login and authentification i removed the #.
external_url: "https://xxxxxxxxxxx.net:xxxxx"
internal_url: "https://192.xxx.xxx.101:8123"
regards
Peer
Huh. Well, I had removed the integration because it wasn’t working for a while, and now I can’t get it to let me log in. And because I removed the integration I don’t have any lines in my config.yaml file.
Arggh. having issues with this site tonight. Every time I hit the reply button, this post is sent to a different thread, one I haven’t even been browsing lately. Anyway, here’s my 3rd try:
Now that I’ve got the custom integration working, I’ve noticed the overheat protection works for only the first 12 hours the vehicle is parked. There’s some debate about whether it’s always been this way, or if it’s a recent development. In any case, I’ve started a new thread rather than adding more here. Please check it out if you park more than 12 hours at a time and let me know how you’re handling it:
Lost the HA virtual machine using Virtualbox so had to reinstall Tesla_custom. When I try to add the integration, the Tesla login page comes up with a captcha but it says “ERROR for site owner:
Invalid domain for site key”. Refresh doesn’t help. Is this an external_url issue? My configuration.yaml doesn’t have this key in it. I’m using the latest core, HACS etc. Any help is appreciated.
EDIT: The URL for the Tesla login looks like this:
http://192.168.1.105:8123/auth/tesla/proxy?config_flow_id=e25d34f93ce14ea5973981ff912b494b&callback_url=http://192.168.1.105:8123/auth/tesla/callback?flow_id%3De25d34f93ce14ea5973981ff912b494b
@leeson
have you installed addons in your browser like privacy badger, uBlock Origin, diconnect or other like adblocker? Try it with a clean browser without extension and clean your browsercache.
Peer
peerkn:
Thanks for your input.
Been using Chrome. uBlock origin or similar apparently not installed. All extensions seem harmless. Cleared cache. Also tried the same with Firefox (uBlock origin disabled). No difference.
Looks like the official Tesla integration is being removed due to added login security by Tesla: https://github.com/home-assistant/core/pull/55988
Is the custom integration still working?
There was some sort of hiccup this morning, probably on the Tesla side, but working now.
1 Like
Nice, a fork of the official integration. Are there any differences between the different integrations, functionality wise?
I didn’t do a comparison, since i don’t yet use the info (in automations or anything; i currently use it as just information), but afaik they’re pretty similar in what they offer. If you let me know what you at least want to be available, i can probably let you know if it is offered :-).
Thanks! I was planning on using it for coming home/zones, and also charging based on power price level, telling the car to stop charging at peak periods. I will test it myself, just need to wait until things calm down at work 
Hi, I am entering either OWNER API ACCESS TOKER or SSD REFRESH TOKEN
but get invalid token … ?
Only the refresh token works. It is a very long string. How did you enter it? Copy and paste is the only way to go. If you didn’t, you probably made a mistake.
The HACs custom integration is working for me. It took using an Tesla Authentication app to supply a token.