Add LG Styler ST_B_E4H01Y_APL - #115
Open
tunarabuuu wants to merge 1 commit into
Open
Conversation
An AA..BB ThinQ2 garment-care unit (deviceType 203). The byte layout was recovered by injecting single-byte-changed state frames through the management API and reading the LG cloud's decode back, one offset per observation. Reads go through the base class's processAABB — the frame arrives with its leading AA/FF and trailing CRC/BB already stripped, so the record offsets are two less than the whole-frame positions the probes recorded. Stray warnings go through the logging utility rather than console. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Third of the per-device-class splits from #111.
ST_B_E4H01Y_APL — an AA..BB ThinQ2 Styler / garment-care unit (deviceType 203). The byte layout was recovered by injecting single-byte-changed state frames through the management API and reading the LG cloud's own decode back, one offset per observation (three of the bytes are bitfields, split bit by bit).
Addressing your review notes from #111:
processAABBinstead of a customprocessData; the frame arrives with its leading AA/FF and trailing CRC/BB stripped, so the record offsets are simply two less than the whole-frame positions.console.warncalls now uselog(...).All labels are English.
npm testpasses;tscclean.