Kevin Miller

I am seeing this problem too for a few weeks. I didn't notice this issue until now. I updated to beta3 of pypowerwall and will report in if the reset...

Updated to `jasonacox/pypowerwall:0.8.1t52-beta1` today. When I restarted I noticed that the gateway had locked me out again (likely pre update). At the gateway web page I am receiving this error:...

Logging output to a file manually via `docker logs -f pypowerwall > pypowerwall-0401.log` If the password reset problem occurs I'll relay the logs.

I do not. Only Powerwall-Dashboard. My logs from yesterday were filled with this: ``` 04/02/2024 05:15:55 AM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken...

I have a single Powerwall 2 and gateway. I restarted today (it had stopped working again) with debug on and am watching the logs. I thought it was interesting that...

Powerwall had stopped working for my login. I reset the password via the gateway. What is interesting is I noticed that the contents of the cached AuthCookie in the `.auth`...

Running new beta3 with the following .env ``` // ... credentials ... PW_TIMEZONE=America/Chicago PW_STYLE=grafana-dark TZ=America/Chicago PW_DEBUG=yes PW_CACHE_EXPIRE=30 PW_POOL_MAXSIZE=1 ``` I have two timezones in there for some reason. Maybe that...

One day later and we are still good (no forced password reset). I think the lower connections, or the longer expiration may be helping.

It has been running well now for 4 days. Longest I can remember. [Here is a gist of a log sample](https://gist.github.com/KevM/d0b35aa845fccd4f7feaacdf370f87f6).

My guess it maybe a combination. Could be an API limit and the 5 second interval creeps outside of it. Or maybe the concurrent access triggers an internal limit. Of...