Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

not showing Powerwall Vitals #472

Open
silvestrob opened this issue Apr 29, 2024 · 16 comments
Open

not showing Powerwall Vitals #472

silvestrob opened this issue Apr 29, 2024 · 16 comments

Comments

@silvestrob
Copy link

Problem
The Dashboard doesn`t show powerwall vitals. It shows only pw1

Screenshots
image

Host System
image

Thank for the help you cloud give me.
paolo
@jasonacox
Copy link
Owner

jasonacox commented Apr 30, 2024 •
edited
Loading

Hi @silvestrob - A few questions:

  1. Can you tell us what Powerwall Firmware you are running? You can run the ./verify.sh script to get that as well as other important information that may be helpful.
  2. What Dashboard version are you running ( have you run ./upgrade.sh to get latest) - or is this a new installation?
  3. Check the direct API call to see what is rendering: http://localhost:8675/pod (replace localhost with the IP address of the Dashboard host).

@silvestrob
Copy link
Author

silvestrob commented Apr 30, 2024 via email

@jasonacox
Copy link
Owner

./vitals.sh doesn’t work (command not found)

My bad! I mean ./verify.sh

The pod payload show only a single Powerwall is coming back from the Tesla Powerwall Gateway. That is not expected. Is it possible that you have two gateways?

# Have pypowerwall scan for gateways

pip install pypowerwall

python -m pypowerwall scan

@silvestrob
Copy link
Author

silvestrob commented Apr 30, 2024 via email

@jasonacox
Copy link
Owner

Ha! I misunderstood your issue. Bsaed on your srcreenshot, you are seeing what you should see for a single Powerwall (PW1). A few things to note:

  • With the firmware version you are running, Tesla has removed the API data that provides temperature data so that graph will be blank.
  • The rest of the graphs you show are showing the correct data - that is what you should see. It will eventually fill up as time passes:
image

@silvestrob
Copy link
Author

silvestrob commented Apr 30, 2024 via email

@jasonacox
Copy link
Owner

jasonacox commented Apr 30, 2024 •
edited
Loading

Ah! The third phase is hidden - you can unhide it:

image

Scroll down to "C" and click unhide:

image

Click "Apply" and "Save"

Do the same for each of the panels.

@silvestrob
Copy link
Author

silvestrob commented Apr 30, 2024 via email

@silvestrob
Copy link
Author

silvestrob commented Apr 30, 2024 via email

@BuongiornoTexas
Copy link
Contributor

I lost 3 phase frequency reporting with 24.4 - Now I only get frequency data on the phase the powerwall sits on. I haven't checked the API to see if this can be picked up elsewhere.

@jasonacox
Copy link
Owner

Ugh. Thanks @BuongiornoTexas. Another casualty of the Firmware upgrade. The raw data is being sourced from:

(replace localhost with the IP address of your Dashboard host if not local)

@BuongiornoTexas
Copy link
Contributor

It's possible this is due to variations in multi-phase supply between countries - US installations may well continue to get 3 phase data (120V/phase?), while Europe, Australia and others may not (240V/phase).

freq dump:

{
  "PW1_name": null,
  "PW1_PINV_Fout": 50.061,
  "PW1_PINV_VSplit1": null,
  "PW1_PINV_VSplit2": null,
  "PW1_PackagePartNumber": "XXXXX",
  "PW1_PackageSerialNumber": "XXXXXX",
  "PW1_p_out": 0,
  "PW1_q_out": 340,
  "PW1_v_out": 238.8,
  "PW1_f_out": 50.061,
  "PW1_i_out": -0.2,
  "grid_status": 1
}

and pod

{
  "PW1_name": null,
  "PW1_POD_ActiveHeating": null,
  "PW1_POD_ChargeComplete": null,
  "PW1_POD_ChargeRequest": null,
  "PW1_POD_DischargeComplete": null,
  "PW1_POD_PermanentlyFaulted": null,
  "PW1_POD_PersistentlyFaulted": null,
  "PW1_POD_enable_line": null,
  "PW1_POD_available_charge_power": null,
  "PW1_POD_available_dischg_power": null,
  "PW1_POD_nom_energy_remaining": 15127,
  "PW1_POD_nom_energy_to_be_charged": null,
  "PW1_POD_nom_full_pack_energy": 15127,
  "PW1_PackagePartNumber": "XXXXXXXXXX",
  "PW1_PackageSerialNumber": "XXXXXXXXXXX",
  "PW1_pinv_state": "PINV_GridFollowing",
  "PW1_pinv_grid_state": "Grid_Compliant",
  "PW1_p_out": -20,
  "PW1_q_out": 330,
  "PW1_v_out": 238.60000000000002,
  "PW1_f_out": 49.947,
  "PW1_i_out": -0.2,
  "PW1_energy_charged": 3380972,
  "PW1_energy_discharged": 2842412,
  "PW1_off_grid": 0,
  "PW1_vf_mode": 0,
  "PW1_wobble_detected": 0,
  "PW1_charge_power_clamped": 0,
  "PW1_backup_ready": 1,
  "PW1_OpSeqState": "Active",
  "PW1_version": "0fe780c991e052",
  "time_remaining_hours": 36.9176327028676,
  "backup_reserve_percent": 20,
  "nominal_full_pack_energy": 15127,
  "nominal_energy_remaining": 15127
}

@silvestrob
Copy link
Author

silvestrob commented May 1, 2024 via email

@jasonacox
Copy link
Owner

@BuongiornoTexas and @silvestrob - Do you see the same data at http://localhost:8675/api/solar_powerwall ? If you get more data on that call, we may be able to capture that.

With the new Firmware, in the US we no longer get the two phases (VSplit, each 120V) but get the aggregate (240v) only:

{
"PW1_name": null,
"PW1_PINV_Fout": 60.021,
"PW1_PINV_VSplit1": null,
"PW1_PINV_VSplit2": null,
"PW1_PackagePartNumber": "2012170-25-E",
"PW1_PackageSerialNumber": "XXXXXXXXXXX",
"PW1_p_out": 590,
"PW1_q_out": -10,
"PW1_v_out": 240.20000000000002,
"PW1_f_out": 60.021,
"PW1_i_out": -12.700000000000001,
"PW2_name": null,
"PW2_PINV_Fout": 60.021,
"PW2_PINV_VSplit1": null,
"PW2_PINV_VSplit2": null,
"PW2_PackagePartNumber": "3012170-05-B",
"PW2_PackageSerialNumber": "XXXXXXXXXXX",
"PW2_p_out": 560,
"PW2_q_out": 0,
"PW2_v_out": 240.4,
"PW2_f_out": 60.021,
"PW2_i_out": -12.3,
"grid_status": 1
}

@BuongiornoTexas
Copy link
Contributor

Unfortunately, that's a no go for people with non-Telsa solar (me and many others!). If this solar_powerwall does offer additional data, then we may want to offer an either/or for users. While I'd like to get more frequency info, I definitely don't want to lose the limited data I get at the moment!

@silvestrob
Copy link
Author

silvestrob commented May 2, 2024 via email

This was referenced Jun 2, 2024
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jasonacox @BuongiornoTexas @silvestrob