Docs: Improve LuxPower Freeze Charge Exit Automation: Fix Trigger/Condition Logic to Handle Predbat Restarts#3389
Open
brickatius wants to merge 2 commits intospringfall2008:mainfrom
Open
Conversation
Refactor conditions for Freeze charging cleanup trigger.
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.
This PR updates the LuxPower Freeze Charge Exit automation in the LuxPower section of the Inverter Setup documentation to ensure it correctly disables freeze‑charge automations in an edge case where Predbat is restarted or updated whilst
predbat_statusis Freeze charging.Background
When Predbat enters Freeze charging, the
freeze_charge_guardboolean is set to on.However, if Predbat is restarted or updated while in this state, its next reported status may no longer be “Freeze charging”. In this scenario, the existing automation does not trigger, because it relied on a state transition from “Freeze charging”.
As a result:
Fix
This PR updates the automation to trigger on any Predbat status change, and adds conditions to detect when:
Recommended Update for Existing Users
Users with an existing LuxPower freeze‑charge setup should update their Freeze Charge Exit automation to use the following trigger and conditions:
This ensures the exit automation fires correctly even after a Predbat restart or update.
Note
This change affects only the Home Assistant automation logic.
It does not require any modification to Predbat core, LuxPower integration code, or inverter configuration.