[EL15] Improve BLE write reliability, CAP setpoint handling, and status decoding#12
Open
[EL15] Improve BLE write reliability, CAP setpoint handling, and status decoding#12
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
This PR improves the EL15 BLE integration in a few focused areas:
Details
Write reliability
EL15 writes now wait for the device notification path instead of racing a poll request. This fixes cases where setpoint or mode changes were unreliable.
CAP mode
CAP mode now uses its dedicated BLE command flow instead of the normal setpoint path:
Fault and cycle handling
Fault decoding is more explicit now:
Runtime / timer display
When the EL15 timer flag is set and load is on, the runtime field is shown as
Timer ...instead ofRuntime ....DCR mode
DCR packets carry a real current field that can be used to compute power. The UI now shows: