Dashboard Upgrade left me in odd state

[JohnJ9ml]

I decided things had gone on long enough that I'd do an upgrade on Dashboard. I'm pretty sure I was on 4.8.1 previously.

I ran the upgrade.sh script, and right now I have lost access to port 9000. It seems that somehow I have grafana running without docker opening up the port:

jjames@pidock:/space/github/Powerwall-Dashboard $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e66064a5e157 telegraf:1.28.2 "/entrypoint.sh tele…" 18 hours ago Created telegraf 1af6091c8271 jasonacox/weather411:0.2.3 "python3 server.py" 18 hours ago Created weather411 0e7dcd08534a grafana/grafana:9.1.2-ubuntu "/run.sh" 18 hours ago Created grafana c1d522943439 influxdb:1.8 "/entrypoint.sh infl…" 18 hours ago Up 18 hours (healthy) 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp influxdb 4e8df61b2f57 jasonacox/pypowerwall:0.14.0t80 "python3 server.py" 18 hours ago Created pypowerwall 2aa7a1bd7f35 nginx:stable "/docker-entrypoint.…" 6 weeks ago Up 18 hours 80/tcp, 0.0.0.0:8675->8675/tcp, :::8675->8675/tcp pypowerwall-proxy 4301ebcaeee5 hello-world "/hello" 8 months ago Exited (0) 8 months ago infallible_lalande 7cb30d16870e hello-world "/hello" 8 months ago Exited (0) 8 months ago romantic_galois 23d83a954ccb hello-world "/hello" 8 months ago Exited (0) 8 months ago charming_cray

The other thing that went ill for me took me a bit to recall how to correct: I have pypowerwall running on a separate box out in the garage, so I had to remember how to change my telegraf.conf file to point there instead of running locally. That change wasn't preserved, and it's on me to not have kept notes on this, but right now I still have a running pypowerwall on the grafana box.

I'm feeling I should have taken different steps that would survive a tree refresh, but I'm really thinking that somehow I'm in a mode where the grafana docker image is not being configured to expose port 9000.

`jjames@pidock:/space/github/Powerwall-Dashboard $ ./verify.sh
Verify Powerwall-Dashboard 4.8.4 on Linux - Timezone: America/Los_Angeles

This script will attempt to verify all the services needed to run
Powerwall-Dashboard. Use this output when you open an issue for help:
https://github.com/jasonacox/Powerwall-Dashboard/issues/new

Tip: If colors are hard to read, try: ./verify.sh --no-color, --lightbg, or --darkbg

Checking pypowerwall

• Config File pypowerwall.env: GOOD
• Container (pypowerwall): ERROR: Stopped
• Version: Unknown
• Powerwall State: ERROR: Not Connected - Firmware: Unknown
• Powerwall Gateway TEDAPI: Not Available (192.168.91.1)
• Cloud Mode: NO

Checking telegraf

• Config File telegraf.conf: GOOD
• Local Config File telegraf.local: GOOD
• Container (telegraf): ERROR: Stopped
• Version: Unknown

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): ERROR: Stopped
• Version: Unknown

Checking weather411

• Container (weather411): ERROR: Stopped
• Version: Unknown

One or more tests failed.
`

I"m sure I could eventually work my way through this, but wanted to post this in case there is either a better way to configure things locally for the fact pypowerwall is not local to the dashboard box, or there's a better way to upgrade that I've missed. We're all playing around with antennae close to the gateway, so my configuration is probably becoming more normal than it likely was.

[jasonacox]

Yes, the setup.sh and upgrade.sh scripts are very opinionated. They weren't designed for customized installs like yours so I suspect your docker networking is a bit messed up. You can try ./compose-dash.sh down and then ./compose-dash.sh up -d to have it try to rebuild everything.

As to adding a "remote pypowerwall" option to the setup, that's not a bad idea. I'll add that to our wish list to investigate.

[JohnJ9ml]

Okay, I gave that a try, and it's just odd that the grafana container does not start with port 9000 defined. I'm not sure what I could have somehow done that has perturbed that little bit.

[jasonacox]

Puzzling to me to! Let us know if you figure it out.