Skip to content

Add CST_570004_WW cassette AC support - #129

Open
BluSyn wants to merge 1 commit into
anszom:masterfrom
BluSyn:pr/ac-cst-cassette
Open

Add CST_570004_WW cassette AC support#129
BluSyn wants to merge 1 commit into
anszom:masterfrom
BluSyn:pr/ac-cst-cassette

Conversation

@BluSyn

@BluSyn BluSyn commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Map cassette model CST_570004_WW to the RAC TLV handler and accept 0xA7 fromDevice framing in tlv_device (required for this platform). Explicitly power on with non-off climate mode writes; unlock autodry, air purify, energy save, timers, and swing from state tags when caps bits are missing; expose 0x336 humidity sensor. Decode 0xA7 in packet-codec; autodry is a writable switch.

LG AC Cassette models tested: ARNU36GTNA4 and ARNU18GTQA4. Internal model CST_570004_WW reported. These models don't have built-in wifi; was connected using wifi module accessory PWFMDD200 through wifi module port on main board.

This has one unique feature: humidity reporting. All other features are generic to other devices as well.

This did require some refactoring due to difference in behavior vs base device. Tested base device on other compatible units without issue; no regressions found.

Map cassette model CST_570004_WW to the RAC TLV handler and accept 0xA7
fromDevice framing in tlv_device (required for this platform). Explicitly
power on with non-off climate mode writes; unlock autodry, air purify,
energy save, timers, and swing from state tags when caps bits are missing;
expose 0x336 humidity as tenths of a percent. Decode 0xA7 in packet-codec;
autodry is a writable optimistic switch.
@anszom

anszom commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Thank you for the PR. I've just returned from vacation and I'm slowly working through the PR & issue backlog. I'd appreciate your patience :)


/**
* Optional features are unlocked by caps feature-words when present.
* Some models (e.g. CST_570004_WW cassette) omit or use different caps bits

@maciejsszmigiero maciejsszmigiero Aug 22, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should enable features supported by the official ThinQ API and app just based on presence of particular tag - for example many (all?) RAC_056905_WW models have air purifier tag but only some models actually have an air purifier module inside.

Usually these features can be auto-detected from caps - that's how app knows whether to display particular feature widget and so should we.

Most likely CST_570004_WW simply has different cap bits than RAC_056905_WW - what does its model JSON file say?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants