Skip to content

TWC 1.3.2, python 3.10 (on armbian pine64) Hass issue [solved with python 3.12], Tesla API ok on 2018 tesla #613

@revoneor

Description

@revoneor

@revoneor When using docker-compose you are running a prebuilt docker image (check your docker-compose.yml to see which version) and the python version that comes with it. When using pyenv you run TWCManager locally. You cannot combine the two methods. Please open a new issue/discussion. This one is about a specific problem with from a year ago.

Originally posted by @RichieB2B in #557

Hi Rich
Docker compose now on v1.3.2

sudo docker compose -f docker-compose.yml up -d
my .venv lists python 3.12.9
TWC to and from Hass works fine now.
I retried on my system Python 3.10 (so without .venv) and again Hass failed to report input, so that seems like some strange quirck.

I struggled to get my Tesla API connected, there are so many topics I didn't know what actually is required for a 2018 tesla.
Low and behold after doing that click in the top tesla api banner and posting the error page url into twc it started working.
(I can not re issue the link, the http://registration.teslatasks.com/generateTokens from the manual settings page is different, also generates not found though) (also in the git html I can not find the link yet)
Not sure if that is affected by my tesla fleet certificates hosting and tesla user and dev account with 2FA I was logged in already, I got a client ID and code but have not added that in config.json

Question, is there a way to get the SoC and Target exported?

Image
My compliments on this great tool to get balanced net using Tesla as storage

Image
Self use solar power!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions