You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which model is the AC unit and remote?
Could it be that your device does it differently compared to what the initial protocol support was written for? If so we need to detect your remote and deal with it differently.
What you might need to do is grab the state and create a spreadsheet and then figure out exactly which bits needs to be used and in what way.
Also do set the timmer, wait a couple of minutes and then send something else, like changing temperature. The timer should probably have counted down.
This is a CLair CLA-KE-WM12MONO 3.5 AC unit. I assume this is a rebranded TCL model. The details for the original TCL112AC protocol support was discovered using this model (see: #619), but without the timer code. The remote controller doesn't have any model number but the brand name. There are some marks on the PCB of it:
Version/revision of the library used
v2.8.4
Describe the bug
The TC112AC timer intervals decoded erroneously by IRrecvDumpV2. Instead on half hours got 20 minutes and after 22 hours got incorrect values.
To Reproduce
Example code used
IRrecvDumpV2
Expected behaviour
Get proper intervals as set on the remote
Output of raw data from IRrecvDumpV2.ino or V3 (if applicable)
There was sent every timer interval supported by remote controller, and the results pasted here.
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?
The timer function was tested first time.
Other useful information
The text was updated successfully, but these errors were encountered: