Replies: 4 comments 5 replies
-
Blame Tesla, we'd love for it to be simpler but this is a limitation of the way they have implemented the fleet API |
Beta Was this translation helpful? Give feedback.
-
Agreed. You dont need to expose HA to the internet - you just need a DNS domain, SSL cert and host the public key generated on HA. I just registered a cheap domain and use Azure Static Web apps as a low-cost hosting option for the key (it gives you the matching SSL cert for free). PITA compared to the old API, but it works. |
Beta Was this translation helpful? Give feedback.
-
No, there isn't. This is 100% Teslas fault, nothing the author can do about the changes they made. |
Beta Was this translation helpful? Give feedback.
-
After introducing new API, Tesla provided band-aid solution in a form of a proxy which translates old style calls into new API commands. As it is in Go, I believe it won't be possible to reuse code here. However, nothing is stopping us from writing new integration in Python which natively calls new API. Just someone has to start new project and keep writing. I don't hold my breath, however. Seeing as all commercial implementation are stuck with Tesla's proxy, even as paid project no-one want's to take on it. We need to see someone talented and with lots of courage and spare time to start it. It would be more likely if proxy was not provided. |
Beta Was this translation helpful? Give feedback.
-
Is there any easier method on the horizon? I was quite happy with the Tesla Integration so far that just required to generate a token with my phone app.
Now all this exposing HA to the internet, SSL certificates, (reverse) proxy setup … WHY?
😔
Beta Was this translation helpful? Give feedback.
All reactions