Health release for pypowerwall?

[JohnJ9ml]

Is there a new release for the pypowerwall changes needed for the health endpoint? I didn't see one accompanying the dashboard release.

[jasonacox]

That's a good point and I can cut one, but also it wasn't a library change, just the proxy: jasonacox/pypowerwall:0.13.1t76

[JohnJ9ml]

I picked up the new build, and now I'm not getting the data back that drives the animation on the dashboard.

`jjames@crewchief:powerwall$ curl http://powerwall:8675/csv
0.00,0.00,0.00,0.00,41.44
jjames@crewchief:powerwall$ time !!
time curl http://powerwall:8675/csv
0.00,0.00,0.00,0.00,41.44

real 0m54.553s
user 0m0.011s
sys 0m0.016s
`

I'm still looking about for other changes that have taken place.

I did get moved to PW version 25.18.1-g, but that was a couple days ago.

[JohnJ9ml]

Perhaps knowing which calls were resulting in failure would be something good to add to the health data:

{ "cache_ttl_seconds": 30, "graceful_degradation": true, "fail_fast_mode": false, "health_check_enabled": true, "startup_time": "2025-07-10T09:54:26", "current_time": "2025-07-10T11:50:50.293953", "connection_health": { "consecutive_failures": 0, "total_failures": 14541, "total_successes": 16018, "is_degraded": false, "last_success_time": 1752173450.0075507, "last_success_age_seconds": 0.28641390800476074 }, "cached_data": { "cache_size": 1, "endpoints": { "/soe": { "age_seconds": 0.28641247749328613, "is_expired": false } } } }

A lot of failures, a lot of successes - it would probably be good to know what's succeeding, what's failing.

[JohnJ9ml]

Attached is a 20 second or so dump of the debug logs from the proxy while all of this is going on.
proxydebug.txt

[JohnJ9ml]

And then, later on it seemingly healed itself:

{ "cache_ttl_seconds": 30, "graceful_degradation": true, "fail_fast_mode": false, "health_check_enabled": true, "startup_time": "2025-07-10T09:54:26", "current_time": "2025-07-10T14:03:05.036225", "connection_health": { "consecutive_failures": 0, "total_failures": 25964, "total_successes": 46685, "is_degraded": false, "last_success_time": 1752181385.0065017, "last_success_age_seconds": 0.029733896255493164 }, "cached_data": { "cache_size": 3, "endpoints": { "/soe": { "age_seconds": 0.029995441436767578, "is_expired": false }, "/strings": { "age_seconds": 4.401860475540161, "is_expired": false }, "/aggregates": { "age_seconds": 1.3289411067962646, "is_expired": false } } } }

pyproxy.txt

[JohnJ9ml]

The blasted thing just heals itself. I even restarted my primary PW3 - first time ever - and treated it like a Windows device - what's a good reboot among friends? The problems continued on through the PW restart. Almost by surprise, the data suddenly started flowing again with no intervention at all from myself.

[jasonacox]

Here is a new one to try: jasonacox/pypowerwall:0.13.2t77-beta

I added endpoint statistics. I will need to load test it to ensure it doesn't create too much overhead, but should help with your troubleshooting efforts. Also, I incorporated some optimization from v0.13.2.

{
  "cache_ttl_seconds": 30,
  "graceful_degradation": true,
  "fail_fast_mode": false,
  "health_check_enabled": true,
  "startup_time": "2025-07-11T23:10:34",
  "current_time": "2025-07-11T23:13:01.210777",
  "proxy_stats": {
    "total_gets": 411,
    "total_posts": 0,
    "total_errors": 0,
    "total_timeouts": 0
  },
  "connection_health": {
    "consecutive_failures": 0,
    "total_failures": 0,
    "total_successes": 531,
    "is_degraded": false,
    "last_success_time": 1752300780.027656,
    "last_success_age_seconds": 1.1831517219543457
  },
  "cached_data": {
    "cache_size": 4,
    "endpoints": {
      "/aggregates": {
        "age_seconds": 1.2027292251586914,
        "is_expired": false
      },
      "/soe": {
        "age_seconds": 1.1908392906188965,
        "is_expired": false
      },
      "/strings": {
        "age_seconds": 1.1831464767456055,
        "is_expired": false
      },
      "/vitals": {
        "age_seconds": 119.38730812072754,
        "is_expired": true
      }
    }
  },
  "endpoint_statistics": {
    "/aggregates": {
      "total_calls": 53,
      "successful_calls": 53,
      "failed_calls": 0,
      "success_rate_percent": 100.0,
      "last_success_age_seconds": 1.2027406692504883
    },
    "/soe": {
      "total_calls": 30,
      "successful_calls": 30,
      "failed_calls": 0,
      "success_rate_percent": 100.0,
      "last_success_age_seconds": 1.1908516883850098
    },
    "/strings": {
      "total_calls": 30,
      "successful_calls": 30,
      "failed_calls": 0,
      "success_rate_percent": 100.0,
      "last_success_age_seconds": 1.1831586360931396
    },
    "/vitals": {
      "total_calls": 1,
      "successful_calls": 1,
      "failed_calls": 0,
      "success_rate_percent": 100.0,
      "last_success_age_seconds": 119.38731694221497
    }
  }
}

[JohnJ9ml]

Sorry for not picking this out earlier, but the health output should include the proxy version. It would be good to track historical behavior.

[jasonacox]

Are you thinking about something similar to what we do for /stats?

{
"pypowerwall": "0.13.2 Proxy t79",
...
}

[jasonacox]

If so, you can test: jasonacox/pypowerwall:0.13.2t79-beta

[JohnJ9ml]

yeah, that's what I was thinking about. Just a way to track it and store it and be able to look back and note behavioral changes.