Add Sigenergy Cloud apps.yaml template#4265
Merged
Merged
Conversation
Add templates/sigenergy_cloud.yaml, the sample config the docs already link to (inverter-setup.md template table and the Sigenergy Cloud section) but which was missing from the repo. Modelled on solax_cloud.yaml with the Sigenergy Cloud API keys (system_id, app_key/secret, MQTT certs, automatic, enable_controls) and correct EU base_url/mqtt_host defaults. Also add the documented enphase_site_id option (for multi-site Enlighten accounts) to the existing enphase_cloud.yaml template. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing Home Assistant apps.yaml templates referenced by the documentation, restoring previously broken links and improving out-of-the-box configuration for cloud integrations.
Changes:
- Add
templates/sigenergy_cloud.yamlas a full Sigenergy Cloud configuration template (including OpenAPI + MQTT cert configuration and “automatic” wiring). - Update
templates/enphase_cloud.yamlto document the optionalenphase_site_idsetting for multi-site Enlighten accounts.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| templates/sigenergy_cloud.yaml | New Sigenergy Cloud apps.yaml template aligned with config schema and component registration. |
| templates/enphase_cloud.yaml | Adds a commented enphase_site_id option with guidance for multi-site accounts. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
The !secret tag can't be parsed by the check-yaml pre-commit hook (it uses a plain safe loader). Match the convention of the other cloud templates by using plain placeholder values for app_key/app_secret, and present the multi-line PEM MQTT certs as commented !secret examples pointing at secrets.yaml. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
templates/sigenergy_cloud.yaml— the sampleapps.yamlthe documentation already links to (the template table and the Sigenergy Cloud section ofinverter-setup.md) but which was missing from the repo, so those links were broken.solax_cloud.yaml(closest cloud analog) with the Sigenergy Cloud API section fromcomponents.py:sigenergy_system_id,sigenergy_app_key/sigenergy_app_secret, MQTT certs (sigenergy_ca_pem/client_pem/client_key),sigenergy_automatic,sigenergy_enable_controls, plus commentedbase_url/mqtt_hostoverrides with the correct EU defaults. Withautomatic: Truethe component wires all sensors/controls itself, so no manual sensor config is included.enphase_site_idoption (for multi-site Enlighten accounts) to the existingenphase_cloud.yamltemplate.Testing
!secrethandled as Home Assistant does).apps/predbat/components.py.🤖 Generated with Claude Code