Skip to content

docs(sunsynk): recommend single timer slot configuration - #5064

Open
carig-rob wants to merge 3 commits into
springfall2008:mainfrom
carig-rob:patch-1
Open

carig-rob wants to merge 3 commits into
springfall2008:mainfrom
carig-rob:patch-1

Conversation

@carig-rob

Copy link
Copy Markdown

Simplifies the Sunsynk setup instructions to recommend direct single timer slot control, which requires no Sunsynk-specific Home Assistant automations or template sensors.

This approach has been running reliably since March 2026, including charge windows that cross midnight, and avoids the timer overlap issues encountered with the six-slot configuration.

The six-slot method and the previous automation-based approach remain documented as alternatives.

The standard utility_meter block is still required, as it is for every Predbat installation — it is not Sunsynk-specific.

Requested by @gcoan in discussion #4609.

Simplifies the Sunsynk setup instructions to recommend direct single timer slot control, which requires no Sunsynk-specific Home Assistant automations or template sensors.

This approach has been running reliably since March 2026, including charge windows that cross midnight, and avoids the timer overlap issues encountered with the six-slot configuration.

The six-slot method and the previous automation-based approach remain documented as alternatives.

The standard utility_meter block is still required, as it is for every
Predbat installation — it is not Sunsynk-specific.

Requested by @gcoan in discussion springfall2008#4609.
@carig-rob

Copy link
Copy Markdown
Author

"Hi @gcoan, just a gentle bump on this one. It's the Sunsynk documentation update you suggested in #4609. The automated checks passed, so I just wanted to make sure it hadn't been missed. Thanks!"

Clarify Predbat's control over Timer 1 and its charging parameters.
@carig-rob

Copy link
Copy Markdown
Author

From v9.3.7, Predbat respects user-configured time entities in apps.yaml rather than replacing them with internal dummies. For Sunsynk inverters, map charge_start_time and charge_end_time to Predbat's own sensors (sensor.predbat_sk_0_charge_start_time / _end_time) — these accept the full HH:MM:SS format Predbat uses. Mapping directly to the Sunsynk select entity will fail because it only accepts HH:MM."

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant