It doesn’t need cloud API access for most things - only for filling in data gaps iirc.
Can you point me to more info on what changed?
EDIT: NVM, I found the repo - looks like the big change is TLS v1.3 is now enforced.
I’ve put in a feature request - as it currently stands, Hubitat can’t talk to the Tesla API, even if I update the app.
TLS v 1.3 was the first suspect, but then there was something about http/2 in the latest fix. That’s about the extent of my knowledge.
1 Like
Yep, after pointing it at the TeslaMate repo, Claude identified that too. Honestly, my Claude sub has been the best value sub I’ve bought in many years. So many projects I couldn’t do with out it as I can’t code to save myself. eg
https://github.com/dJOS1475/FluidDial-CYD/tree/main
Wait - I think this thread has gone off-topic! Powerwall Manager is a different app and @snell ‘s driver is for local network access to the Powerwall. @bobbyD - can we split this off into a different thread (from message 375)? Hopefully, it will be less confusing to someone down the road….
1 Like
I was just checking if @snell was using the owner-api - turns out he isn’t. It’s all related to the Powerwall ecosystem.
No worries on my side. As for the “owner-api”, nope. Purely just checking directly with the Powerwall themselves. It was easiest early on when it was an integrated Neurio system and code… but that has changed over time.
3 Likes
Yah, me too. The token says validated in blue but does not work for changing modes.