Extend EmberStatus -> sl_Status mapping
#707
Open
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
Revert `TABLE_ENTRY_ERASED` change
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #707 +/- ##
=======================================
Coverage 99.53% 99.54%
=======================================
Files 58 61 +3
Lines 4128 4147 +19
=======================================
+ Hits 4109 4128 +19
Misses 19 19 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
TheJulianJES
approved these changes
Jan 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A recent Home Assistant issue mentioned a warning regarding
EmberStatus.LIBRARY_NOT_PRESENT, which needed a mapping tosl_Status.NOT_AVAILABLE. I've mapped I think the remaining statuses, allowing us us to usesl_Statusinternally within bellows.I think in the future we can minimize the use of this function by moving code shared between multiple EZSP versions into version-specific handlers.