Repository navigation
Conversation
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
New standalone pure-Python
dtek_correlation.pycompares timing only between events recorded by Shelly and dated DTEK scheduled-outage windows. It never assigns a verified cause to a power loss, and a Shelly network disconnection is not proof of mains failure.The result is one of
start_within_window,partial_overlap,outside_published_windows, orunknown, with an explicitcause_verified=False. Malformed, missing, wrong-date, out-of-order and overlapping schedules fail closed. Open events need a supplied observation boundary; Europe/Kyiv and midnight/DST cases are covered.Validation
Release boundaries
No network calls, Telegram writes, device controls, database changes or production deployment. This is a library-only Draft PR. Live integration depends on real, dated and verified schedule snapshots from draft PR #150, and separate emergency advisory normalization in draft PR #151. Operator confirmation of subscriber-facing text is required before release.