Problem with string data in v4.6.7 (2 PW3's)

[heynorm]

I have 2 Powerwall 3's and after upgrading from v4.6.6 to v4.6.7 and I am no longer seeing string data from my second Powerwall. This was working fine with v4.6.6. I run the Dashboard on a Pi that is wirelessly connected directly my primary PW3 (I switched to this setup a few weeks ago after being upgraded to fw 25.10.1). I ran PW3_Strings.py and it appears to me that it is not seeing my second PW3 at all. Output of verify.sh is below. Let me know what additional information would be helpful. Thanks - Earl

Checking pypowerwall

• Config File pypowerwall.env: GOOD
• Container (pypowerwall): GOOD
• Service (port 8675): GOOD
• Version: 0.12.11 Proxy t72
• Powerwall State: CONNECTED - Firmware: 25.10.1
• Site Name: Stahl HH
• Gateway TEDAPI: Available (192.168.91.1)
• TEDAPI Vitals: Connected - Mode: full
• Cloud Mode: NO

Checking telegraf

• Config File telegraf.conf: GOOD
• Local Config File telegraf.local: GOOD
• Container (telegraf): GOOD
• Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

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): GOOD
• Service (port 9000): GOOD
• Filesystem (./grafana): GOOD
• Version: Grafana CLI version 9.1.2

Checking weather411

• Container (weather411): GOOD
• Service (port 8676): GOOD
• Weather: {"temperature": 35.8}
• Version: 0.2.3

All tests succeeded.

[heynorm]

Also - I verified that the String data for my second PW3 is available both in Netzero and Tesla One. Here is the output from PW3_Strings.py. I believe the problem is:

• Fetching ComponentsQuery from Powerwall (1707000-00-J--TG..........FJ Powerwall3Follower)...

• No Components Found

---

Tesla Powerwall 3 Gateway API Decoder

• Testing Connection to Powerwall Gateway...

Enter Powerwall Gateway Password: ..........

• Fetching DIN from Powerwall...
• Connected: Powerwall Gateway DIN: 1707000-00-J--TG..........KX
• Fetching Configuration from Powerwall...
• Config Written to config.json
• Battery Blocks:
  • Battery Block: 1707000-00-J--TG..........KX (Powerwall3)
  • Battery Block: 1707000-00-J--TG1240190001FJ (Powerwall3Follower)
• Fetching /tedapi/v1 PW3 Firmware from Powerwall (1707000-00-J--TG..........KX)...
  Response Code: 200
• Firmware Written to firmware.raw
  Firmware version (len=16): 25.10.1 6bea8bd4
• Fetching /tedapi/v1 PW3 ComponentsQuery from Powerwall (1707000-00-J--TG..........KX)...
  Response Code: 200
  Payload (len=9750): {"components":...}
• Components Written to components.json

• Fetching ComponentsQuery from Powerwall (1707000-00-J--TG...........KX Powerwall3)...
  • Alerts:
    • Alert: PWS_a003_MciSelfTestCD
    • Alert: PWS_a004_MciSelfTestEF
    • Alert: PWS_a008_MciPvIrrationalDEF
  • PW1 Nominal Energy Remaining: 14.08 Nominal Full Pack Energy: 14.42 Energy to be Charged: 0.33999999999999986
  • String A = State: Pv_Active Voltage: 382 Current: 0.3999999999999997 Power: 152.79999999999987
  • String B = State: Pv_Active Voltage: 384 Current: 0.3999999999999997 Power: 153.59999999999988
  • String C = State: Pv_Active Voltage: 320 Current: 0.3999999999999997 Power: 127.9999999999999
  • String D = State: Pv_Active Voltage: 0 Current: 0.04999999999999964 Power: 0.0
  • String E = State: Pv_Active Voltage: 0 Current: -3.608224830031759e-16 Power: -0.0
  • String F = State: Pv_Active_Parallel Voltage: 0 Current: -3.608224830031759e-16 Power: -0.0
• Fetching ComponentsQuery from Powerwall (1707000-00-J--TG..........FJ Powerwall3Follower)...

• No Components Found

Strings Data:
{
"A": {
"Connected": true,
"State": "Pv_Active",
"Voltage": 382,
"Current": 0.3999999999999997,
"Power": 152.79999999999987,
"din": "1707000-00-J--TG..........KX"
},
"B": {
"Connected": true,
"State": "Pv_Active",
"Voltage": 384,
"Current": 0.3999999999999997,
"Power": 153.59999999999988,
"din": "1707000-00-J--TG..........KX"
},
"C": {
"Connected": true,
"State": "Pv_Active",
"Voltage": 320,
"Current": 0.3999999999999997,
"Power": 127.9999999999999,
"din": "1707000-00-J--TG..........KX"
},
"D": {
"Connected": true,
"State": "Pv_Active",
"Voltage": 0,
"Current": 0.04999999999999964,
"Power": 0.0,
"din": "1707000-00-J--TG..........KX"
},
"E": {
"Connected": true,
"State": "Pv_Active",
"Voltage": 0,
"Current": -3.608224830031759e-16,
"Power": -0.0,
"din": "1707000-00-J--TG..........KX"
},
"F": {
"Connected": true,
"State": "Pv_Active_Parallel",
"Voltage": 0,
"Current": -3.608224830031759e-16,
"Power": -0.0,
"din": "1707000-00-J--TG..........KX"
}
}

Alerts:
[
"PWS_a003_MciSelfTestCD",
"PWS_a004_MciSelfTestEF",
"PWS_a008_MciPvIrrationalDEF"
]

POD Data:
{
"PW1_POD_nom_energy_remaining": 14.08,
"PW1_POD_nom_full_pack_energy": 14.42,
"PW1_POD_nom_energy_to_be_charged": 0.33999999999999986
}

[jasonacox]

Hi @heynorm - I rolled back the changes of #169 related to the device API. I wonder if this is the cause of what you are seeing. Can you test by editing your powerwall.yml file and change the pypowerwall image to this:

jasonacox/pypowerwall:0.12.11t72-beta172

Restart with:

./compose-dash.sh up -d

Let me know that helps.

[heynorm]

@jasonacox - I made the change you recommended and it does solve the issue - thanks!. Let me know how I can be of further help.

[jasonacox]

Hi @heynorm - I added logic that should work for single or multiple PW3 installations. Can you test on you system by editing your powerwall.yml file and change the pypowerwall image to this:

jasonacox/pypowerwall:0.12.12t72-beta

Restart with:

./compose-dash.sh up -d

Also @johncuthbertuk could you do the same for your single PW3 installation?

I always get nervous about editing any of the PW3 code because I can't test it on my system. 🤞

[heynorm]

@jasonacox - I make the change to the powerwall.yml file you requested. It all looks good on my system.

Thanks!

[jasonacox]

Thanks @heynorm ! 🙏 I'll proceed with releasing this as the next version.