Tasmota/lib/IRremoteESP8266-2.2.1.02

IRremote ESP8266 Library

This library enables you to send and receive infra-red signals on an ESP8266 using Arduino framework (https://github.com/esp8266/Arduino)

v2.2 Now Available

Version 2.2 of the library is now available. This is a significant internal change to existing versions.

Upgrading from versions prior to v2.0

You will need to change your pre-v2.0 code slightly to work with post-v2.0 versions of the library. You can read more about the changes on our wiki page. Please report an issue if you find any problems with the documentation or the library itself.

Troubleshooting

Before reporting an issue or asking for help, please try to follow our Troubleshooting Guide first.

Frequently Asked Questions

Some common answers to common questions and problems can be found on our F.A.Q. wiki page.

History

This library was originally based on Ken Shirriff's work (https://github.com/shirriff/Arduino-IRremote/)

Mark Szabo has updated the IRsend class to work on ESP8266 and Sebastien Warin the receiving & decoding part (IRrecv class).

Installation

1. Click "Download ZIP"
2. Extract the downloaded zip file
3. Rename the extracted folder to "IRremoteESP8266"
4. Move this folder to your libraries directory (under windows: C:\Users\YOURNAME\Documents\Arduino\libraries)
5. Restart your Arduino ide
6. Check out the examples

Using Git to install library ( Linux )

cd ~/Arduino/libraries
git clone https://github.com/markszabo/IRremoteESP8266.git

To Update to the latest version of the library

cd ~/Arduino/libraries/IRremoteESP8266 && git pull

Unit Tests

The Unit Tests under the test/ directory are for a Unix machine, not the micro-controller (ESP8266). This allows execution under Travis and on the developer's machine. We can do this from v2.0 of the library onwards, as everything now uses c98-style type definitions. e.g. uint16_t etc. Any Arduino/ESP8266 specific code needs to be disabled using something similar to the following lines:

#ifndef UNIT_TEST
<Arduino specific code ...>
#endif

This is not a perfect situation as we can not obviously emulate hardware specific features and differences. e.g. Interrupts, GPIOs, CPU instruction timing etc, etc.

If you want to run all the tests yourself, try the following:

$ cd test
$ make run

Contributing

If you want to contribute to this project, consider:

• Report bugs and errors
• Ask for enhancements
• Create issues and pull requests
• Tell other people about this library

Contributors

Available here