Repository navigation
Fix the mFRR automation example in the README - #13
Merged
Merged
Conversation
The example's code block was never closed, so the rest of the README rendered as code. Its state trigger also fired when the event entity became unavailable (failing on the missing start attribute) and again when the restored state came back after a restart or reload. Adding not_from/not_to: unavailable leaves one notification per activation, checked with an automation in Home Assistant 2026.10.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UwYSvzP667Y5pkhzfs8obW
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.
Follow-up to #11.
Unclosed code block: the example's YAML block was never closed, so everything after it in the README rendered as code.
Extra notifications and errors: the example's state trigger also fired in two cases where it should not:
unavailable, where the template failed with'ReadOnlyDict object' has no attribute 'start'The trigger now has
not_from: unavailableandnot_to: unavailable.I tested the example as a real automation in Home Assistant 2026.10.0 with one activation followed by an integration reload:
state(before)not_from: unavailablenot_from+not_to: unavailable(now)The template itself (
as_local(as_datetime(...start))) works both with the live datetime attribute and with the string it is restored as.🤖 Generated with Claude Code
https://claude.ai/code/session_01UwYSvzP667Y5pkhzfs8obW
Generated by Claude Code