Powerwall 3 Setup Issues on Win11 #492
Comments
|
Hi @pavandave, thanks for the details! I'm opening an issue here to track the fixes. It appears that your setup is trying to log in using the PW2 credentials instead of sticking with the TEDAPI Please check your If not, remove the email and password, save the file and run As to the failure of the # Function to test an IP to see if it returns a ping
function test_ip() {
local IP=$1
if [ -z "${IP}" ]; then
return 1
fi
if curl -k --head --connect-timeout 1 --silent https://192.168.91.1 > /dev/null 2>&1; then
return 0
else
return 1
fi
}
# Can we reach 192.168.91.1
if test_ip "192.168.91.1"; then
echo "Found Powerwall Gateway"
else
echo "Failed"
fiAnd just for full measure, can you also run: Thanks for your help! I want to get the fixes in to help other PW3 owners. |
|
Updated the env file per your recommendation. I had used the template info but updated to the below and redeployed and that worked. This may just be me, but for PW3 stuff while folks are still figuring it out, maybe a note in docs that PW3 config file differs and should have nothing in for email/pass may be helpful. Example of working env config: Output of the help file url: Screenshot of working dashboard: I re-ran the setup.sh file and it worked but I think having that env file bypasses that check. If you want me to re-run without any credentials I can but when it comes to pinging 192.168.91.1 I found some strange behavior. From the WLS shell, I don't get a response. BUT from Windows terminal, I do,. I'm not sure why this is differing on the same machine. But if option 4 is selected, I would consider getting rid of the ICMP repsonse check check in the PW3 scenario. Maybe run an API call to see if it returns a valid response, if not have the user validate their network or password (depending on the response). Let me know if this helps or you would like me to test any further. I will gladly assist where possible. |
|
Fantastic! Can you try importing Also, on the ping, you are correct. I had a few others mention that ping was bad. It is actually using curl -k --head --connect-timeout 1 https://192.168.91.1 |
|
Interestingly I finally got some ping responses from WLS but I just saw it this morning but it's not something promising. The curl command gives me this: As for the core dashboard, I took the screenshot from the wrong dashboard. It works. I fiddled with something that turned the power flow into a white box for now but that's on me and I do see the main data I want to see.
I plan on migrating the dashboard to another machine soon. Will follow up with any additional feedback from there. |
Added additional information from issue jasonacox#492
|
One interesting note about the power flow animation: If you have another browser window/tab open with that, only one of them will display at a time. I'm not entirely sure why as you can bypass it by using a different browser (e.g. Chrome and Edge) and they will both render. Anyway, thanks for the posting these and your PR. I have some comments but will leave them in the PR. |
I'm not sure when it changed, but I can now open two tabs with both showing the animation in Chrome on my Chromebook. I thought it might be because I'm running Grafana 10.3.1, but I just tried opening the default Grafana 9.1.2 dashboard and it sometimes works depending on the sequence of what I do. I'm not sure exactly what's going on, but in an Incognito window I can reliably open 2 tabs but the third fails to display the animation. A second ago I had the animation showing in one regular tab and two incognito tabs at the same time. I just tried it in Edge under Windows 10 and was able to open the dashboard with animation in two regular and two InPrivate tabs at the same time. A third tab of either type shows a blank animation. |
|
Interesting! Thanks @youzer-name - the same would occur with the example iframe built into pypowerwall: http://localhost:8675/example.html so I don't think this is a Grafana issue. I should look again to see if there is a better way to handle it. |
|
Trying to set up a new PW3.. It is connect via ethernet. It has a local IP address of 192.168.10.100 but in the netzero app is says Active (primary) IP address 192.168.90.2 which address do I put into the pypowerwall.env? my local of the one listed in netzero app? |
|
@farberm Before running setup, assuming 192.168.10.100 is the PW3 LAN address you can ping, you will want to set up a local route to the 192.168.91.1 endpoint using these instructions, which is somehting like this: # Example - Change 192.168.10.100 to the IP address of Powerwall Gateway on your LAN
# Linux / RPi - Add to netplan, /etc/rc.local or /etc/network/if-up.d/static-route for persistence
sudo ip route add 192.168.91.1 via 192.168.10.100
# MacOS
sudo route add -host 192.168.91.1 192.168.10.100 # Temporary
networksetup -setadditionalroutes Wi-Fi 192.168.91.1 255.255.255.255 192.168.10.100 # Persistent
# Windows - Using persistence flag - Administrator Shell
route -p add 192.168.91.1 mask 255.255.255.255 192.168.10.100The IP address you will use in setup will be 192.168.91.1 but sertup should detect that if you set up the route before running setup. Bonus FYI - to scan your network to find the LAN IP address of the Powerwall: python3 -m pypowerwall scan |
|
What if I am running this from synology docker? and should it be using 192.168.90.2 cuz that is what is listed in netzero not 192.168.91.1 as active primary ip address?
I assume it should be editing the etc/rc.network file but that is very long file.. do I just add at the top of the file ......route add 192.168.91.1 via 192.168.10.100 and that is all?
… On Sep 6, 2024, at 10:51 PM, Jason Cox ***@***.***> wrote:
@farberm <https://github.com/farberm> Before running setup, assuming 192.168.10.100 is the PW3 LAN address you can ping, you will want to set up a local route to the 192.168.91.1 endpoint using these instructions <https://github.com/jasonacox/Powerwall-Dashboard?tab=readme-ov-file#extended-device-vitals-metrics-beta>, which is somehting like this:
# Example - Change 192.168.10.100 to the IP address of Powerwall Gateway on your LAN
# Linux / RPi - Add to netplan, /etc/rc.local or /etc/network/if-up.d/static-route for persistence
sudo ip route add 192.168.91.1 via 192.168.10.100
# MacOS
sudo route add -host 192.168.91.1 192.168.10.100 # Temporary
networksetup -setadditionalroutes Wi-Fi 192.168.91.1 255.255.255.255 192.168.10.100 # Persistent
# Windows - Using persistence flag - Administrator Shell
route -p add 192.168.91.1 mask 255.255.255.255 192.168.10.100
The IP address you will use in setup will be 192.168.91.1 but sertup should detect that if you set up the route before running setup.
Bonus FYI - to scan your network to find the LAN IP address of the Powerwall:
python3 -m pypowerwall scan
—
Reply to this email directly, view it on GitHub <#492 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3BWWIFR54FTSUU4KPU6Q3ZVJS3NAVCNFSM6AAAAABJS5TNZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGAYTENZSHE>.
You are receiving this because you were mentioned.
|
Hi @farberm ! I see that you created #514 so I will respond to this over there. TLDR: I believe the IP address from Netzero is coming from |
Hm, not sure why |
|
Yes @zigam it does seem to be specific to PW3. My PW2's work fine. Would it help if you had some of the PW3 owners post their /api/networks payloads, or are you pulling this from another API? |
Thanks, I was able to confirm the issue is specific to PW3 and will hide these internal ips. |
I have a Powerwall3 and finally got time to spin this up. Running this all on W11 with WLS running Ubuntu. My PW3 is hardwired.
My experience is as follows:
Next. The main setup with option 4 didn't work for me. It could not find the gateway. Because the test above worked, I know my machine can get to my PW3. I had to create the pypowerwall.env file and then I re-ran through the setup with option 4 and was able to complete.
Went through rest of the guide but wasn't seeing anything on Grafana. Looked at docker logs and see that I am getting some information:
So we know I'm getting data and able to connect, but then I hit various excedptions and api rate limits:
Let me know if this helps or if you would like some more debugs from anything.
Originally posted by @pavandave in #392 (reply in thread)
The text was updated successfully, but these errors were encountered: