Open-source Token

[r151809]

Hi,

Thank you @iainbullock for working for the common good :)

I tried to follow the instructions to my best, but it's quite likely that I have made multiple mistakes. But the first to steps in "Tesla HTTP Proxy setup" -page seem to work, except for the fact that I do not find client_secret from Tesla's page. Client_id is there to copy, but no client_secret. According to Tesla that's the case if you choose open source token. I'd guess that this has changed quite lately in Tesla's api..

Assuming this is not a SUE (Stupid User Error), what would be your recommended way of getting forward?

1. I implent Open source token based authentication. There is a risk that I fail to complete it..
2. Change the registration to non open source
3. Wait for someone else to implement it - do you Iain know if someone has started the work?
4. Discard docker based installation

:)

[iainbullock]

Did you follow @tux43 instructions here https://www.smartmotion.life/2024/04/23/tesla-custom-integration-with-home-assistant-on-docker/?v=6cc98ba2045f

In particular section 4.9 shows where you get Client ID and Client Secret

(Unless something has changed as I haven't had to run this process since my first set up)

Looking at the Tesla documentation, I believe you should be generating a Partner Authentication Token.

Another place to look would be the parent project which has a more active user base (and therefore the same question may have already been asked) compared to my project https://github.com/llamafilm/tesla-http-proxy-addon

Let me know how you get on

[Olen]

I noticed the same thing as the OP. There are now two options you can choose from when creating an App in the Tesla Developer Portal. If you choose "Open Source" there is no Client Secret generated, so you must make sure you say "No" on this question (even if your app is going to be open source, because you will probably not publish your client-id and secret in the source of the app):

I don't know anything about how auth works on the Open Source version, but since you do not have a client secret, the Oauth-dance is probably quite different from the Non Open Source version.

[r151809]

Thank you.
Managed to get further by "requesting" second instance without open source selection.

I still have something with my local dns. At some point tesla_http_proxy did not like my domain (.home) so I tried with .local. Now HA does not resolve .local and .home goes to SSLCertVerificationError. But this is something I will be able to solve somehow - it just takes time.

Luckily it's summer and I do not really need load shredding yet :)

[iainbullock]

I don't believe ESP Bluetooth Proxy will work as Tesla's Go code wants to talk to a BT device directly. Maybe you could write your own Go code, but I haven't looked at it in any detail.

[r151809]

I'm now waiting for my kid in the car, so I had spare time. I tried directly https://github.com/teslamotors/vehicle-command in Mac. It works nicely. So I'm now confident that I will get BLE up and running somehow under HA :) In my case no need for tesla_http_proxy, as tesla_ble_mqtt serves me better :)

Thanks @iainbullock !

[iainbullock]

Good to hear. You might still want tesla_http_proxy if you want more sensors as there's not much with BLE

[r151809]

You are probably right - there is no SOC in the BLE data sets..

[r151809]

Got tesla_http_proxy running finally.

The issue wat that my HA was not able to find the proxy, and after fixing that it was accessing the internet facing https-port of nginx.

Failed ping between docker containers was due to invalid network_mode configs. The default, bridge, should work in most cases - I had a mess of host and bridge so some things did work, but not all..

Now I have separate network called http_proxy in docker-compose. This way I do not have to worry about conflicting ports. In the setup phase external setting must be true, of course.

  tesla_http_proxy:
    networks:
      - http_proxy

  ha:
    networks:
      - http_proxy
      - default

networks:
  http_proxy:
    external: true

With this config HA connects to proxy like this: httos://tesla_http_proxy/

And one note for other who make mistakes in the configs and want to start from the beginning: r

• Removing access_token enables Flask
• Removing key.pem forces selfsigned certificate renewal

Thank you @iainbullock and @Olen :)