Exposing the Powerwall() function calls as proxy endpoints

[JohnJ9ml]

I'm posting this here even though the proxy appears to be something that generally surfaces as part of the dashboard. That said, it's sitting in the pypowerwall source tree....

I realize I'm off on my own tangent with my PW work, but I've got years of data and years of analysis done with my own similar time series-like data in my own database. As such, I've been using both the Dashboard as well as my own instance of code against pypowerwall to fetch data from my PW3. I'd seen mentions of the proxy, but just hadn't pursued it, and was trying to keep the bicycle wheels spinning on my own deployment.

Now that I'm looking around more, watching firmware updates drive many of us batty, and multiple connectivity points, I realize maybe what Tesla is trying to defend against is me specifically: I've got at least two computers beating on their poor little CPU continually. Perhaps in their eyes, life is just not fair!

As I poked about looking at the proxy endpoints, I found that I could probably make most things work, but what I really wanted to do (and really defined 'make most things work' as 'make most things look exactly as they are now') was end up with the same JSON data structures coming back from endpoints as I was currently getting from the Powerwall() API inside pypowerwall.

Currently, at periodic intervals (probably far too periodic for Tesla's PW CPU), I'm basically doing the following:

    level = pw.level()
    power = pw.power()
    site = pw.site(True)
    solar = pw.solar(True)
    battery = pw.battery(True)
    battery_blocks = pw.battery_blocks()
    load = pw.load(True)
    grid = pw.grid(True)
    home = pw.home(True)
    vitals = pw.vitals()
    temps = pw.temps()
    strings = pw.strings(False, True)
    din = pw.din()
    uptime = pw.uptime()
    version = pw.version()
    status = pw.status()
    system_status = pw.system_status()
    grid_status_str = pw.grid_status(type="json")
    grid_status = json.loads(grid_status_str)

    aggregates = pw.poll('/api/meters/aggregates', False)

Has anybody already extended the proxy such that all of these ended up coming back the same way via proxy endpoints?

I was thinking of something along the lines of mimicking the Powerwall() calls as:

/pw/level /pw/power /pw/site /pw/solar /pw/status /pw/battery_blocks ...etc...

I know some of them are somewhat already present, and in some cases part of the data is there, or in different form. I've not yet figured out what of these I can make full use of, but I figured while I was in town, it was better to start gathering everything I could and then sort it out down the road.

Yes, I know... it's just crying out for me to be a contributor, right? I've written exactly one thing in python, and it's the wrapper I'm using to do this work, and I'm quite convinced it's a terrible hack. (Plus, this damned whitespace meaning something important and nesting is absolutely eating my braces-loving Java-coding lunch!)

I just didn't know if someone had already put a nice little bow on the thing and made it so that convenience endpoints matched up exactly with the Powerwall() API.

I have noticed over time that the proxy connection is more resilient than my own, and maybe it's time to stop abusing that PW CPU and just take advantage of the data already being fetched.

[jasonacox]

Interesting idea @JohnJ9ml ! It would be fairly easy to add this route to the proxy (and mapping to functions).

As you probably guessed, the issue with your script is less about the different calls since pypowerwall will cache the data (instead of calling the PW every time) for a default of 5s, so for your example it will make the minimal number of calls. However, the bigger difference is that pypowerwall will keep the TCP connection open (actually a pool of them) to handle subsequent HTTP requests. That reduces load (and latency).

[JohnJ9ml]

I did figure out how to do this. I've got a copy working locally that I will look over more for completeness and some more testing.

Once I'm confident I've done this right, I'll figure out how to submit it.

[JohnJ9ml]

Still confessing that I still don't know exactly what I'm doing, so I'm doing my best to work through tutorials for hints.

My local changes have been tested in a basic fashion and committed locally. I either don't have permission to push (getting a 403) or don't have my credentials somehow set correctly for the repository. Do I have to be granted permission to make a submission? Did I need to have this issue assigned to me first, or something else?

[jasonacox]

#166