Only reading string data from single PW3 in 2xPW3 setup.

[jbdiablo]

I noticed that my dashboard has not been working for the past month. I saw the new update that includes the new VR1 authentication setup and decided to rebuild my rPI from scratch. My old Pi was setup as a wifi relay connected to the lead PW3 and i was able to get string/ capacity data from both PW3.

Got everything all set up and history imported but my string data only shows data from the leader PW3, that is the one i put in the IP for during setup. I have 2 PW3, both are connected to the wifi and ethernet. Is there a method to monitor both PW3 like before using the new local method?

[rick-davis-39]

you need to also connect to the PW3 wifi access point to get follower metrics

PW_HOST=10.42.1.101
PW_RSA_KEY_PATH=/app/.auth/tedapi_rsa_private.pem
PW_GW_PWD=XXXXXXXXXX
PW_WIFI_HOST=192.168.91.1

[jasonacox-sam]

To add to @rick-davis-39's suggestion — the reason your old WiFi relay setup saw both PW3 units is that it was connected to the TeslaPW_****** mesh, which bridges the leader and follower internally. The new VR1 wired LAN mode connects through the Gateway, which routes TEDAPI to the leader but may not expose the follower's string data the same way.

Worth trying the PW_WIFI_HOST approach @rick-davis-39 described — that tells pyPowerwall to pull extended metrics (strings, temps, voltages) via the PW3's WiFi AP instead of relying on the VR1 path alone.

If that doesn't close the gap, Tesla Cloud / FleetAPI mode is another option — it pulls from Tesla's cloud side, which sees the complete site including all PW3 units. You'd lose some real-time granularity (cloud polling is slower), but it should see both units' data.

The broader feature request for multi-gateway / multi-PW3 support is tracked in #148 (still open). That's the one to 👍 if you want to push it up the priority list.

— Sam 🌊