From 1df74e47cc66a96c57c25a68d5c9c0c4a617105f Mon Sep 17 00:00:00 2001 From: tronikos Date: Thu, 5 Jun 2025 23:40:52 -0700 Subject: [PATCH] update --- source/_integrations/solaredge_modules.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_integrations/solaredge_modules.markdown b/source/_integrations/solaredge_modules.markdown index 9248ac7b66d..cdeedc95bb5 100644 --- a/source/_integrations/solaredge_modules.markdown +++ b/source/_integrations/solaredge_modules.markdown @@ -35,6 +35,10 @@ An example of a Statistics graph that shows hourly production per module for the ![Screenshot hourly production Statistics graph](/images/integrations/solaredge_modules/hourly_production.png) +{% note %} +The statistic IDs below are examples. It's recommended to press on **SHOW VISUAL EDITOR** to select the statistics based on their name instead. +{% endnote %} + ```yaml chart_type: line period: hour @@ -74,6 +78,10 @@ days_to_show: 30 To identify problematic modules, you could set up the [`SQL`](/integrations/sql/) integration with the following: +{% note %} +The SQL code contains a couple of TODOs for you to adjust the threshold and to select the proper modules based on your solar installation. In the example the panels on the east side have ` 1.1.` while the ones on the west have ` 1.2.`. +{% endnote %} + Name: SolarEdge low production modules (East) Column: `problematic_modules`