Connection refused to port 8675, RPi

[maxEntropyProd]

Hi
setup.sh seemed to work fine while installing PD on a RPi4; however, when I pull up Powerwall Power Flow dashboard, the Power Flow window shows "Unable to connect" to localhost:8675. If I point a browser to that port, I get a similar message about site can't be reached.
Any suggestions? Note, my powerwall+ and solar was just installed, but the inverter has some issues and so the system is in standby as they try to troubleshoot that. However, if I log into the gateway it shows the Tesla graphic with power being supplied by the grid. So that's working.
Thanks!

[jasonacox]

A few things to try:

1. Ensure you do not have another browser window/tab open that is showing the animation. Chrome and other browsers prevent the iframe from rendering if it opened more than once (I would like someone to explain this to me at some point :)
2. Several of the browsers do not like iframes on "localhost" so try to use the IP address instead (e.g. http://10.0.1.2:9000/).
3. Try to view the animation directly from the pyPowerwall proxy by going to this: http://10.0.1.2:8675/ - also make sure the latest pypowerwall was installed (e.g. v0.5.1): http://10.0.1.2:8675/stats (of course replace the IP address with your RPi)

[maxEntropyProd]

hi @jasonacox, thanks for the fast reply! I did post this under discussion Q&A, but will keep it here. Interesting, 10.0.1.2 didn't work (I thought that was the same as localhost); however, if I use the IP of the machine on the local network (192.168...), I still get the same response. Likewise, http://192.168.0.80:8675/stats also shows Unable to Connect. I've closed other open tabs first. It's like there is a firewall on port 8675, but I'm not running any firewall on the RPi

I see you've move this here (discussion) now, so will respond here.

[jasonacox]

Thank you, Joe! I'm sorry this isn't as easy as it should be but your feedback is golden. By running the alternative, I see that the real issue is indeed docker and not just the Alpine container. That means we need to address the fundamental issue of getting the libseccomp2 bug fixed.

Apt-Key Fix?

I don't know why the apt-key command failed. Are you behind a firewall that blocks outbound ports? If so, you can try this instead:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 04EE7237B7D453EC 648ACFD622F3D138

# if it works, the rest
# Add the Buster backport repository to apt sources.list
echo 'deb http://httpredir.debian.org/debian buster-backports main contrib non-free' | sudo tee -a /etc/apt/sources.list.d/debian-backports.list

sudo apt update
sudo apt install libseccomp2 -t buster-backports

# I recommend you restart and see if that corrects the problem

Manual libseccomp2 Upgrade

If the above didn't work, there is a brute force way to get the libseccomp upgrade from debian.

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.4.4-1~bpo10+1_armhf.deb
sudo dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb

Manual Test of Proxy?

In case the above didn't work. I am going to give you a way to run pypowerwall proxy directly. This is for testing or temporary setup as it won't have any restart or start-on-boot function that docker enables. However, it may be useful so you can at least see the end goal. :)

In the pypowerwall/proxy directory, create a start.sh file (or any name you want to use) that contains this (make sure you update the Password, Email and Host):

export PW_PASSWORD="password"
export PW_EMAIL="email@example.com"
export PW_HOST="x.x.x.x"  # IP Address of your Powerwall Gateway
export PW_TIMEZONE="America/LosAngeles"
export PW_DEBUG="no"
export PW_HTTPS="no"
export PW_PORT="8675"
export PW_CACHE_EXPIRE="10"

echo "Starting proxy at http://localhost:8675..."
python3 server.py

Run it with bash start.sh

You should now be able to go to these URLs to see pypowerwall running:

• http://localhost:8675/stats
• http://localhost:8675/ <- This should show the animation by itself
• http://localhost:8675/soe <- battery
• http://localhost:8675/aggregates <- all system metrics
• http://localhost:8675/vitals <- all device vitals

There is a chance that telegraf will see this and start pulling in the metrics. Speaking of which, we should verify the rest of the containers:

docker logs telegraf
docker logs influxdb
docker logs grafana

[maxEntropyProd]

Good news @jasonacox the second attempt at the Apt-key fixed worked! My router doesn't block outbound traffic, but the hkp:// url worked (not sure what that url is).

I did not bother to reboot, so I just reopened Powerwall Power Flow and I'm now seeing live connection to the Tesla gateway! I'm not seeing much other data, but I'm guessing that's because the powerwalls are off and the system is in standby (I'm still waiting for Tesla to fix the inverter problem...argh, but that's a different problem :)

Thank you so much for your help, as there is no way I would have been able to figure that out. Very cool!

cheers,
-joe

update: I am seeing most of the data (sting voltage, powerwall temps, home and line freq., etc, it just took a bit to start populating the graphs)

[jasonacox]

That's great news, Joe! Good job!!! Thanks for the update. 👏

I'm going to add a note to the instructions (or perhaps even some code in setup.sh) to help better handle installations on the Raspbian GNU/Linux 10 (buster) systems like yours. I am surprised that this hasn't come up sooner. Buster is legacy, but not that old. Thanks for helping me work through the problem and come up with a solution.

If you are interested, grab a screenshot of your dashboard and paste it here so we can celebrate with you. 🎉

PS - Since you have system troubles right now, you might check out the alerts that your Powerwall systems is publishing. It sounds like Tesla knows about it, but you mind find it interesting: http://localhost:8675/alerts

[maxEntropyProd]

Great. Ya, it seems I set up the RPi4 not that long ago (but time can run slow), so hopefully your good sleuthing will help others.

The graphics are great! here's the top bit, but so much more

Didn't see the alerts, just,
[
"SystemConnectedToGrid",
"SystemShutdown",
"FWUpdateSucceeded",
"SiteMaxPowerLimited",
"PanelMaxCurrentLimited",
"GridCodesWriteError",
"GridCodesWriteError",
"DeviceShutdownRequested",
"PVAC_a014_PVS_disabled_relay",
"PVS_a021_RapidShutdown"
]

but it's in standby. Latest new is that it's the backup switch, as they are sending a replacement for that.
Again, thanks for your help!

[jasonacox]

It looks great, Joe. Thanks for pasting those alerts! There are several I haven't seen before. I log all the alerts here: https://github.com/jasonacox/pypowerwall#devices-and-alerts

Since your system is in SystemShutdown you could also check the device vitals: http://localhost:8675/vitals - It contains your serial numbers so you probably don't want to paste it but you might find it interesting.