jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-27 03:07:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update solaredge_modules.markdown

Browse Source
This commit is contained in:
tronikos 2025-07-20 21:34:22 -07:00 committed by GitHub
parent b4b056e0c8
commit 4dbdc6d568
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
source/_integrations/solaredge_modules.markdown
View File

@ -3,11 +3,10 @@ title: SolarEdge Modules
description: Instructions on how to integrate SolarEdge Modules within Home Assistant. description: Instructions on how to integrate SolarEdge Modules within Home Assistant.
ha_category: ha_category:
- Energy - Energy
ha_release: '2025.7' ha_release: '2025.8'
ha_iot_class: Cloud Polling ha_iot_class: Cloud Polling
ha_config_flow: true ha_config_flow: true
ha_domain: solaredge_modules ha_domain: solaredge_modules
ha_dhcp: true
ha_codeowners: ha_codeowners:
- '@tronikos' - '@tronikos'
ha_integration_type: service ha_integration_type: service
@ -25,8 +24,9 @@ The main use case is to track your solar production per module to identify any f
## Prerequisites ## Prerequisites
- To set up the integration, you need a username and password with access to the [SolarEdge web portal](https://monitoring.solaredge.com/). To set up the integration, you need:
- You also need the site ID, which you can get from the URL once you log in (for example, `1234` from `https://monitoring.solaredge.com/solaredge-web/p/site/1234/`). - a username and password with access to the [SolarEdge web portal](https://monitoring.solaredge.com/) and the **Layout** tab there. If not, you will have to ask your installer to grant you access.
- site ID, which you can get from the URL once you log in (for example, `1234` from `https://monitoring.solaredge.com/solaredge-web/p/site/1234/`).
{% include integrations/config_flow.md %} {% include integrations/config_flow.md %}
@ -197,7 +197,7 @@ mode: single
## Known limitations ## Known limitations
- The integration intentionally doesn't create any sensors. All data is only available in statistics. This is because data is often delayed by a couple of hours. - The integration intentionally doesn't create any entities/sensors. All data is only available in statistics. This is because data is often delayed by a couple of hours.
- The statistics are intentionally updated infrequently. If you want more frequent updates, you can call the [`homeassistant.reload_config_entry`](/integrations/homeassistant/#action-homeassistantreload_config_entry) action from an automation. - The statistics are intentionally updated infrequently. If you want more frequent updates, you can call the [`homeassistant.reload_config_entry`](/integrations/homeassistant/#action-homeassistantreload_config_entry) action from an automation.
- The API provides data at a 15-minute interval, but Home Assistant long-term statistics are limited to a 1-hour interval. - The API provides data at a 15-minute interval, but Home Assistant long-term statistics are limited to a 1-hour interval.