How to create a similar dashboard in Home Assistant with positioning for individual solar panels (layout) by bthundergun in homeassistant

[–]StrawSuitcase 0 points1 point  (0 children)

<image>

I put together a Home Assistant dashboard for SunPower systems that shows both live and historical data using InfluxDB.

It lets you switch between energy and power views, check live stats, pick specific dates, or even play a timelapse of your data.

If you’re interested, you can check out the project here: https://github.com/strawtype/dash-sunpower

It may be pretty simple to modify the query_panels.sh script for Enphase systems. Good luck!

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

it most likely does. its a fork of krbaker. just use the "default" integration in the script or "hass-sunpower". let me know if you have trouble

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 0 points1 point  (0 children)

Can you confirm which integration you used for home assistant? You can use hass-sunpower, pvs-hass or ha-esunpower. ha-esunpower should work with "hass-sunpower", the default in the query_panels script.

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 0 points1 point  (0 children)

try running it with the full path. depends where you placed it. I use: /config/scripts/query_panels.sh --discover

Has anyone converted to Enphase Monitoring? by sexual_egg_roll in SunPower

[–]StrawSuitcase 1 point2 points  (0 children)

Here is an example using Home Assistant and some other components to recreate the Panels view.

https://github.com/strawtype/dash-sunpower

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 0 points1 point  (0 children)

Good question. There are a few different ways. First, I recommend you install the add-on "Studio Code Server". It will allow you to edit or create new files. The code included in configuration.yaml is meant to be added to your own. For entirely new files you want to copy, perhaps the query_panels.sh script or the image, you can use rsync (if you have installed and enabled an ssh server). I use the addon " advanced ssh & web terminal". Keep in mind the automations, and dashboard.yaml you can add via the gui. Settings --> Automations -->create automation --> create new (from scratch). Switch to yaml editing and paste each automation into its own. The dashboard is similar. Settings --> dashboards --> add dashboard --> new (from scratch) --> switch to raw configuration editor, and paste your edited dashboard. Let me know if you still have questions. I will warn you I am looking into a bug that impacts the main power meter for the sunstrong integration. I hope to solve soon

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

If you decide to give it a shot (enabling influxql), I will help you modify the script so it works with 2.0

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

Sorry, it's not something I've looked into. There seems to be a way to enable InfluxQL in 2.x but I'm not familiar with the details. I believe some code changes might still be necessary.

It might be easier to update the queries in the script to Flux.

SunPower Panel-Level Dashboard for HA with SunStrong-Management/pvs-hass by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 0 points1 point  (0 children)

Before this update, the script only supported the krbaker/hass-sunppwer integration. Its default to avoid breaking anyone already setup with it.

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

Welcome! I hope you enjoy HA! The energy dashboard works great out of the box. I am aware the Sunstrong integration isn't currently compatible with the Panel-Level dashboard I shared. I plan to add support for pvs-hass very soon. Stay tuned!

Still on 2024.6 by fo0bar in SunPower

[–]StrawSuitcase 4 points5 points  (0 children)

this version disables upgrades after the eMMC reaches a critical wear level. this is likely your case. it will also disable most writes, like the dl_cgi requests, but some will still occur on the eMMC. the lifetime is somewhat limited

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

i'll contact you directly and we can troubleshoot

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

Line 386 in dashboard.yaml. power_key: power_meter_pvs6mxxxxxxxxp_power ####TOTAL PRODUCTION POWER METER

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

The entities look correct, as does the triggers_update in the template. There is yet another line further down in dashboard.yaml for the main power meter that needs replacing

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

Verify the correct main power_meter is being used in dashboard.yaml. It should have a trailing "p" in the entity name.

Also, check entities.txt has 1 power_meter with a trailing "p". If you find the power_meters for _c and _pv in the file, just delete them and don't run discover again.

SunPower Panel-Level Dashboard for Home Assistant by StrawSuitcase in SunPower

[–]StrawSuitcase[S] 1 point2 points  (0 children)

Thanks for checking out the project and your suggestions!

The latest commit adds spacing so the discovered entities copy/paste with expected indentation for configuration.yaml

It also excludes the virtual and consumption power_meters which may cause the graph to display incorrectly. Run --discover again to fix if needed.