-
Notifications
You must be signed in to change notification settings - Fork 839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GYKQ-52 TCl112AC remote is detected as various model depending on the mode #1896
Comments
Is that an original remote? Or just a clone that works with your AC? |
Yes, this remote model was shipped with both of my AC units. I tested them, and the results same as above. |
Please see #1486 for some history. So, if Can you please look over the Lines 28 to 82 in 71cd956
To see if there is some other bit, bits or pattern we can use to tell the two message formats apart. #1486 #619 & ir_Tcl_test.cpp hopefully contain enough data to compare with. It's all the data we have. |
Version/revision of the library used
v2.8.4
Describe the bug
GYKQ-52 TCl112AC remote (e.g.: https://www.aliexpress.com/item/1005004519422388.html) is detected as various model depending on the mode:
Cool mode: TAC09CHSD
Dry mode: TAC09CHSD
Fan mode: TAC09CHSD
Heat mode: GZ055BE1
Auto mode: GZ055BE1
It seems that the bit 7 of byte 12 is changing mode by mode and fools the
IRTcl112Ac::isTcl
function. It is annoying because some status element in not displayed byIRTcl112Ac::toString
in Heat and Auto modes.To Reproduce
Example code used
IRrecvDumpV2
Expected behaviour
The type of remote does not change
Output of raw data from IRrecvDumpV2.ino or V3 (if applicable)
What brand/model IR demodulator are you using?
TSOP34838
Circuit diagram and hardware used (if applicable)
TSOP34834 on D5 pin of a NodeMCU V2
I have followed the steps in the Troubleshooting Guide & read the FAQ
Yes
Has this library/code previously worked as expected for you?
Not tested before.
Other useful information
It was tested with more remote controllers with same results.
The text was updated successfully, but these errors were encountered: