-
Notifications
You must be signed in to change notification settings - Fork 81
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
Selenium blocked by Tesla #149
Comments
With the release of the official API my guess is Tesla has decided to further increase security and prevent non-official access to the API. |
That makes sense, see #150 @Coverttrickster The TeslaFi Tokens iOS app still seems to produce a refresh token. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of yesterday I attempted a login with selenium and TeslaPy and tesla is able to detect the use of the selenium. I attempted to add options that help prevent the detection of selenium such as:
chrome_options.add_argument('--disable-blink-features=AutomationControlled') chrome_options.add_experimental_option("excludeSwitches", ["enable-automation"]) chrome_options.add_experimental_option('useAutomationExtension', False)
I also tried to rotate user agents as such:
driver.execute_cdp_cmd('Network.setUserAgentOverride', {"userAgent": 'TeslaApp/4.10.0 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.53 Safari/537.36'})
but no luck.
Here is the page I get redirected to when I disable headless mode. I attempted to complete all of the tasks by hand but it loops around the challenges with no luck of proving I am human.
![Screenshot 2023-11-08 at 12 59 58 PM](https://private-user-images.githubusercontent.com/20779534/281541781-d9db736e-2f56-49fe-8b54-3dacbe873baf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1NTYyNDksIm5iZiI6MTcyNTU1NTk0OSwicGF0aCI6Ii8yMDc3OTUzNC8yODE1NDE3ODEtZDlkYjczNmUtMmY1Ni00OWZlLThiNTQtM2RhY2JlODczYmFmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA1VDE3MDU0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhNDg3MDA3MGM5MDk4MzQ1YzA3YjQ4MTdmOGQwNzdkZGNjMGY4ZTY3MjllZjdiYWI0NmVjNDcwNTJlOTY2ZDYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.jMcFC1JbKJwkY4K-POjSUuwm4B6Cs3VDkc73K8j-Q8o)
Are there any other methods I could attempt to retrieve the refresh token without having an end user do anything more than type in the login credentials?
The text was updated successfully, but these errors were encountered: