pypowerwall no longer listening on 8675

[ViktorJp]

For the life of me, something stopped working today right at noon for some crazy reason... I've rebooted my server, tried to restart the containers, tried an upgrade (which went successfully), but grafana is no longer showing current data, and the powerwall flow graph is no longer loading. When I run 'verify.sh', I'm seeing this... the TZ is set across the board for "America/New_York". I don't understand what else could be hanging it up? Any ideas how else to troubleshoot this?

`Checking pypowerwall

• Config File pypowerwall.env: GOOD
• Container (pypowerwall): GOOD
• Service (port 8675): ERROR: Not Listening
• Version: Unknown
• Powerwall State: ERROR: Not Connected - Firmware Version: Unknown
• Cloud Mode: NO
• ERROR: Your pypowerwall settings are missing TZ.

Checking telegraf

• Config File telegraf.conf: GOOD
• Local Config File telegraf.local: GOOD
• Container (telegraf): GOOD
• Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb

• Config File influxdb.conf: GOOD
• Environment File influxdb.env: GOOD
• Container (influxdb): GOOD
• Service (port 8086): GOOD
• Filesystem (./influxdb): GOOD
• Version: InfluxDB shell version: 1.8.10

Checking grafana

• Config File grafana.env: GOOD
• Container (grafana): GOOD
• Service (port 9000): GOOD
• Filesystem (./grafana): GOOD
• Version: Grafana CLI version 9.1.2

Checking weather411

• Skipped: weather411 not set up (missing weather/weather411.conf)

One or more tests failed.
`

[jasonacox]

Hi @ViktorJp

The error means the pypowerwall.env is missing the TZ= setting. That file is created during setup.sh and should look like:

[email protected]
PW_PASSWORD=password
PW_HOST=10.0.1.2
PW_TIMEZONE=America/Los_Angeles
TZ=America/Los_Angeles
PW_DEBUG=no
PW_STYLE=grafana-dark

The TZ line is relatively new but the upgrade.sh script should have added it if it was missing. It is odd that verify.sh is reporting that it is missing. It would be good to check that file to ensure it isn't corrupt. It would also be good to see what pypowerwall says:

docker logs pypowerwall`

That should help explain why the container is not starting. You can also run setup.sh to have it reset the settings.

[ViktorJp]

Thanks for your help, Jason! That may be my problem... in my pypowerwall.env file, everything starts with PW_... including the PW_TIMEZONE... I noticed yours simply is referenced as "TZ="

[email protected]
PW_PASSWORD=PWD
PW_HOST=192.168.86.63
PW_TIMEZONE=America/New_York
PW_DEBUG=no
PW_STYLE=grafana-dark

Would you recommend just manually adding this item TZ=?

So just some background... I'm running ubuntu as a vm on a windows server with hyper-v. From day 1, I have always had major issues with needing to run certain commands with sudo, other times they would work without needing sudo... but it's sometimes real tough to get through an upgrade without it bombing out because of permission issues. Your scripts will exit 1 when sudo is detected, and have to be able to get around that at times. I just don't know enough about Linux in general to get around this issue... one would think that if I install this as a sudo admin that things would just work. I've followed your advice and steps on making sure the current user is a container admin, but in the end, at times have to step through your upgrade/setup scripts line by line, and run commands using sudo to make it through. Not sure what else to try other than perhaps starting a new fresh ubuntu server all over... but needless to say, if the upgrade script was supposed to replace "PW_TIMEZONE=" with "TZ=", then this may have been a cause.

[ViktorJp]

Adding that TZ= seems to have done the trick after a docker restart! Thanks for pointing this out, Jason!

Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): GOOD
 - Service (port 8675): GOOD
 - Version: 0.7.7 Proxy t40
 - Powerwall State: CONNECTED - Firmware Version: 24.4.0
 - Cloud Mode: NO

[SCHibbard]

FYI I had a similar experience yesterday with weather411. At 9:50 Central Time all weather data stopped., however direct calls to api.openweathermap.org worked fine. Powerwall data was doing fine, as were data streams I have added for my provider's hourly energy pricing and data from my microinverters. Before trouble shooting further, thought I should upgrade my sandbox install. Went from 4.0.3 to 4.2.1 and after that all was well with the world so replicated on production install. Assume it was the TZ variable ... ignorance worked in my favor this time.