<p>For sending messages, look at the <aclass="el"href="classIRsend.html"title="Class for sending all basic IR protocols.">IRsend</a> class.</p>
<p>For receiving messages, look at the <aclass="el"href="classIRrecv.html"title="Class for receiving IR messages.">IRrecv</a>&<aclass="el"href="classdecode__results.html"title="Results returned from the decoder.">decode_results</a> classes.</p>
<p>For <em>generic</em> Air Conditioner control, look at the <aclass="el"href="classIRac.html"title="A universal/common/generic interface for controling supported A/Cs.">IRac</a> class & the <aclass="el"href="structstdAc_1_1state__t.html"title="Structure to hold a common A/C state.">stdAc::state_t</a> structure.</p>
<p>For <em>detailed</em> Air Conditioner control, you need to determine what protocol the library detects your remote/Air Conditioner to be, look into the appropriate <code>src/ir_Protocol.[h|cpp]</code> files and use the appropriate class object. e.g. if <code>IRrecvDumpV2</code> (or better) detects the protocol as <code>KELVINATOR</code>, open the <code>src/ir_Kelvinator.*</code> files, and examine the <aclass="el"href="classIRKelvinatorAC.html"title="Class for handling detailed Kelvinator A/C messages.">IRKelvinatorAC</a> class the methods available to create/decode/send <code>KELVINATOR</code> messages with all the abilities the library offers. You can also select it from the <ahref="annotated.html">Classes</a> menu above.</p>
<p>Various native constants & options for a given Protocol's class object can be found in the associated header file for that protocol.</p>
<h1><aclass="anchor"id="autotoc_md14"></a>
Examples</h1>
<p>Most of the common uses of this library's APIs have demonstration code available under the <ahref="https://github.com/crankyoldgit/IRremoteESP8266/tree/master/examples">examples</a> directory. It ranges from trivial examples to complex real-world project code.</p>
<h1><aclass="anchor"id="autotoc_md15"></a>
Tuning</h1>
<p>The most commonly used & needed knobs for controlling aspects of this library are available via run-time class methods or at class-object instantiation. Again, you are referred to the <aclass="el"href="classIRsend.html"title="Class for sending all basic IR protocols.">IRsend</a>&<aclass="el"href="classIRrecv.html"title="Class for receiving IR messages.">IRrecv</a> classes.</p>
<h2><aclass="anchor"id="autotoc_md16"></a>
Advanced</h2>
<p>Certain addition constants and options are available as compile-time tweaks. You should inspect <ahref="https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/IRremoteESP8266.h">IRremoteESP8266.h</a>, <ahref="https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/IRsend.h">IRsend.h</a>, &<ahref="https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/IRrecv.h">IRrecv.h</a> for General, Sending, & Receiving tweaks respectively.</p>
<h3><aclass="anchor"id="autotoc_md17"></a>
Protocol timings</h3>
<p>Generally you should never need to adjust the timing parameters for a given protocol or device. However, occasionally some individual devices just want to be special. If you are having problems decoding/receiving a message, look into the <code>tolerance</code>, <code>kTolerance</code>, or <aclass="el"href="classIRrecv.html#aa091c449db70c65fd0221669df7438ea"title="Set the base tolerance percentage for matching incoming IR messages.">IRrecv::setTolerance</a> constants/methods etc first. However, if your problems is sending, or adjusting the tolerance doesn't work you may need to tweak per-protocol timing values. These are stored as constants in the <code>ir_ProtocolName.cpp</code> file for the given protocol. This is typically a step of last resort.</p>
<h3><aclass="anchor"id="autotoc_md18"></a>
Reducing code size & flash usage.</h3>
<p>You can disable most protocols by either modifying the appropriate <code>#‍define</code>s in <ahref="https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/IRremoteESP8266.h">IRremoteESP8266.h</a> or passing the appropriate compile-time flags, as documented in the same file.</p>
<p>Avoid using the A/C classes, especially the <aclass="el"href="classIRac.html"title="A universal/common/generic interface for controling supported A/Cs.">IRac</a> class as they will force the compiler to include large amounts of code you may not need. </p>