Repository navigation
Replies: 3 comments 1 reply
|
I think there are two separate problems mixed together here. The registration did not actually complete. The key pair alone is not enough for full v1r mode; the public key must be registered with the Powerwall/Tesla API. In your failed setup, registration stops before that step: That path is the important clue. The current setup flow should write the key under the bind-mounted auth directory and pass an auth path, roughly: docker exec -it --user "$(id -u):$(id -g)" pypowerwall \
python3 -m pypowerwall setup -v1r -authpath /app/.authSo I would first pull the latest dashboard/setup script, or rerun the registration manually with ls -l .auth/tedapi_rsa_private.pem
docker exec -it pypowerwall sh -lc 'ls -l /app/.auth/tedapi_rsa_private.pem'The manually generated OpenSSL key is not a complete substitute unless that public key was also registered successfully. The Easy Tesla token/site files are probably a distraction for this specific failure. The second issue is PW_HOST=192.168.1.200For wired LAN v1r, the README says to use the Powerwall 3 vendor/TEG subnet address, typically PW_HOST=10.42.1.40
PW_GW_PWD=<full QR sticker password>
PW_RSA_KEY_PATH=/app/.auth/tedapi_rsa_private.pemThe My order would be:
|
|
Thanks @krotname - good advice here. Hopefully this will help. @jasonacox-sam feel free to add additional suggestions based on @timeden details above, unless @krotname already covered it. |
|
Great diagnostics from @krotname — all three points (the 1. Update pypowerwall first — you're five versions behind Your logs show docker pull jasonacox/pypowerwall:latest
# or if you're running from Powerwall-Dashboard:
docker compose pull pypowerwall2. The "v1r login successful" in your logs doesn't mean the RSA key is registered This is the key thing to understand about your current errors. The
Your manually generated OpenSSL key pair was never sent to Tesla's registration API, so the Powerwall doesn't know to trust it. Regenerating via the setup flow (with 3. Verify the You mentioned you weren't sure which ID to use when your Tesla account also has a vehicle. The You can double-check what's in the file now: cat .auth/.pypowerwall.siteIf it contains something that looks like a vehicle ID (usually a shorter number, different format), that's worth correcting. The v1r registration flow ( 4. Confirm the vendor subnet is actually reachable before changing As krotname noted, ping -c 3 10.42.1.40The vendor subnet is only accessible if your monitoring machine has a wired Ethernet connection to the PW3's LAN port — not via WiFi and not via your main LAN switch. If ping doesn't respond, check the physical cabling first. 5. Quick volume mount sanity check Just to rule out a silent misconfiguration: confirm the docker exec pypowerwall ls -la /app/.auth/If that comes back empty or with a "no such file" error, the bind mount in Once you have the vendor subnet reachable, pull the latest image, and re-run the registration with — Sam ⚡ |
|
Thank you for the very helpful responses Sam and Andrei, I have been meaning to respond but was trying to wait until I confirmed the fix. It's a long story, but I'm doing some house renos at the moment and haven't got my main desktop PC plugged in. Once I've tried your suggestions and got things working properly I'l respond again and mark it as solved hopefully. :-) |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello folks,
I am trying to set up monitoring of my PW3 using v1r mode and feel like I am very close to getting it right, but have been going around in circles trying to troubleshoot why my setup is not working for the past couple of days. The most recent logs are included at the bottom, and I am not yet able to see any stats in the dashboard.
Sorry for the super long post, but hopefully it contains all the details needed for someone to help, thank you!
My setup consists of:
The automatic setup fails at the RSA generation step as follows:
So, I have followed the manual setup and pieced together what I believe is the correct pypowerwall.env and .auth folder files as follows.
env file contents, redacted the PWD:
And the contents of my auth folder are:
The pypowerwall.auth file I made using the Easy Tesla API Token Generator site, and the pypowerwall.site contents I grabbed using the API testing tool at https://reqbin.com/ although I'm not sure which ID field to use as I also have a vehicle listed in the response.
The RSA key pair I generated using these 2 commands:
Each time I change these files I stop and restart the dashboard but I still get the following errors, in debug mode:
All reactions