OK, I used the custom component and then pointing to my Nabu Casa URL.
I didn’t see that particular error. From memory it went pretty much like the documented instructions once I had everything setup but I did have to clear everything out a couple of times and also archive my Tesla Dev app and create a new one. Not sure which if any bits needed cleaning up but on successful attempt with everything cleaned up it went straight through.
And yep, at step 4 it asked me for the domain.
Thanks mate. I will try cleaning up a few more times and see how I go.
I was able to configure it using an Azure storage account with static hosting, I didn’t have to setup a custom domain, the default one https://<yourstorageaccount>.z13.web.core.windows.net/ worked just fine. ChatGPT proposed this solution and walked me through the steps, it was fairly simple. Hosting the 180 bytes of the pubkey for a month rounds to zero cents: $0.0000023/month (0.0023 cents/month)
@FabioSan Would you mind sharing the steps for people to recreate?
Sorry for dredging up an old thread, I am wondering if anyone here had success in getting their energy site working. Eg Powerwall, wall chargers etc? I keep getting a scope error when trying to send commands. I have definitely given the energy site commands access and both of my Model3’s are working fine. Transitioned from Tesla Custom and the Tesla Http proxy, deal breaker if I can’t access my Powerwalls settings though.
Hey Sean, I setup Model 3 access and then got a PowerWall which didn’t immediately become available. In Tesla’s developer centre I checked and confirmed that I’d allowed all API scopes but apparently, I hadn’t allowed them all on the Home Assistant end. Sorry, I can’t remember if I was able to fix that or if I had to totally remove it and the credentials / certificates and re-set up, but I did get it working in the end.
Ah had a similar problem. Just walked through everywhere scopes can be limited including my actual Tesla account. Found it was in my Tesla account third party access for the Tesla Fleet integration itself!
Added it there and all good, so even if you set it right in developer application scope, you can still be overidden and blocked by your general account settings third party section.
All working now thank you!
