Replies: 2 comments 3 replies
-
Yes that is expected. Why are you even opening an issue? (What is it that you want us to do?) |
Beta Was this translation helpful? Give feedback.
1 reply
-
Yep. Fairly common knowledge. See: https://github.com/crankyoldgit/IRremoteESP8266/wiki/Adding-support-for-a-new-AC-protocol#a-note-on-collecting-data |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I'm not sure if this is common knowledge or not, but perhaps this will help some of you.
For the past two days, I was trying to get the hex code and raw data sent by my IR remote. Unfortunately, the same button (e.g., the temperature up button) kept giving different data each time. This made me think something was wrong with my VS1838B receiver. Here’s what I discovered:
AC remotes are not like other remotes. Typical remotes have a single code assigned to a button, but AC remotes send codes depending on the state of the AC. For example, my AC with cool mode on and temperature set to 25°C has a specific IR signal assigned to it, while cool mode at 26°C has another code. So, if your AC is in cool mode at 24°C and you press the temperature up button, the hex code for 25°C cool mode is sent. If you press the same button again, another hex code is sent, even though you pressed the same button.
Practically, this means you need to capture every hex code for each specific AC state (temperature and mode) you want to implement. Feel free to ask any questions. A big thanks to crankyoldgit for this amazing library!
Beta Was this translation helpful? Give feedback.
All reactions