TEDAPI start/stop system

[apach3guy]

In the Tesla One app there is a way to start and stop the system but I don’t see this feature in pypowerwall. Can you explain how to accomplish this with the TEDAPI?

[jasonacox]

Hi @apach3guy ! You are right, there is not a way to do that with pypowerwall. We have only discovered ways to read from the Powerwall via TEDAPI, which is the goal of the project. We have not discovered a way to control it. For control, the preferred (and safer?) path is to use the Tesla cloud (e.g. FleetAPI) or the authorized Tesla One app.

[Nexarian]

I am looking for this, too. My system was installed incorrectly, and the two inverters sometimes interfere with each other with the power line communication to the MCIs on the roof. There is a startup order that, if I could enforce using the start/stop commands, I'd be able to prevent these errors from occurring.

The other useful one for me would be PVInverterPowerStatus, which in Tesla One is "Disabled," "DC Only" and "Enabled."

But how to figure out how to reproduce such commands? The only think I can think of is to try to figure out what commands Tesla One sends and replicate them.

[Nexarian]

Here's what I've been trying:

• Step 1: Download Tesla One APK from Android Phone
• Step 2: Unzip it
• Step 3: Find assets/index.android.bundle (which, as best as I can tell, is the majority of the application)
• Step 4: Use npx js-beautify index.android.bundle --indent-size 2 > pretty.js to clean it up
• Step 5: Discover that most of the app is STILL not in this js bundle, it's in a single-line HTML included at the end in a variable.
• Step 6: Take that single line, copy/paste into VS code and "format"
• Step 7: Ugh, that's STILL not the app. There's a <script> tag at the end.
• Step 8: Copy/paste that into ChatGPT, and say "clean it up." Note this does not always work, it took several tries.
• Step 9: Ask ChatGPT to figure out where the pvi status commands are.

The best answer I can come up with is both start/stop and "enable," "dc only," "disable" commands are now communicated to the inverter(s) through the FileStore API, which appears to send/receive a config.json blob to the inverter and they've moved away from unique commands. The data in that config is what the inverter uses to manage state.

In fact, in the web app from the old Tesla web configuration: https://github.com/jasonacox/pypowerwall/blob/main/proxy/web/viz-static/app.js, there WERE unique APIs, but none appear to work, nor can I find references to them after doing the above manipulations.

Hopefully someone more skilled than I can figure out the exact incantation here.