From 3cf61d136a54dcdc097c7f2841917d155d0bfbb8 Mon Sep 17 00:00:00 2001
From: Michael Ingraham <34340210+meingraham@users.noreply.github.com>
Date: Mon, 9 Sep 2019 17:24:12 -0400
Subject: [PATCH] Updated Tasmota IR (markdown)

---
 Tasmota-IR.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/Tasmota-IR.md b/Tasmota-IR.md
index a6720eba..73b451fb 100644
--- a/Tasmota-IR.md
+++ b/Tasmota-IR.md
@@ -1,10 +1,10 @@
 # "Complete" IR Remote Protocols
 
-The default Tasmota firmware variants include support for IR send/receive for a limited set of protocols (see [IR Remote](Commands#irremote)). Tasmota uses the [IRremoteESP8266 library](https://github.com/crankyoldgit/IRremoteESP8266) that supports numerous protocols. Each protocol consumes some program memory, especially air conditioner protocols (up to 81k of Flash size).
+The default Tasmota firmware variants include support for IR send/receive for a limited set of protocols (see [IR Remote](Commands#irremote)). Tasmota uses the [IRremoteESP8266 library](https://github.com/crankyoldgit/IRremoteESP8266) that supports numerous protocols. Each protocol consumes some program memory, especially air conditioner protocols (up to 81k of flash size). Also, every protocol included increases the time to decode the IR signal. 
 
 There are now two additional Tasmota firmware variants that provide almost all IRremoteESP8266 protocols. This requires disabling some other features to keep code size manageable.
 - `sonoff-ir` is pre-packaged for IR blasters, like [Eachen IR Bridge](https://blakadder.github.io/templates/eachen_SANT-IR_01.html) or [YTF IR Bridge](https://blakadder.github.io/templates/ytf_ir_bridge.html). Choose the preconfigured `sonoff-ir` if you are using an IR blaster.  
-- `sonoff-ircustom` is used if you want to customize your own firmware binary. This latter variant is required because it triggers a special compilation flag for IRremoteESP8266.
+- `sonoff-ircustom` is used if you want to customize your own firmware binary. This latter variant is required because it triggers a special compilation flag for IRremoteESP8266. Edit the [`IRremoteESP8266.h`](../tree/development/lib/) header in the `IRremoteESP8266-x.x.x/src` folder to disable (i.e., set to `false`) any unneeded/unwanted protocols and compile your own firmware.
 
 ## Sending IR Commands
 
@@ -24,11 +24,12 @@ IRhvac<a id="IRhvac"></a>|Send HVAC IR remote control code as JSON payload<BR><B
 
 ## Receiving IR Commands
 
-If you have an IR receiver plugged, you will be notified each time an IR message is seen. IRremoteESP8266 will try to decode the message against all supported protocols. If unrecognized, the `"Protocol":"UNKNOWN"` will be shown. In this case, the `"Data"` field contains a hash of the received message. The hash can't be used to send the a message, but the same hash will be produced by the same message.
+If you have an IR receiver, a message will be logged each time an IR message is seen. `IRremoteESP8266` will try to decode the message against all supported protocols. If unrecognized, the `"Protocol":"UNKNOWN"` will be shown. In this case, the `"Data"` field contains a hash of the received message. The hash can't be used to send the a message, but the same hash will be produced by the same message.  
 
 Information on [Receiving Infrared Data](Receiving-Infrared-Remote-Control-Data)
 
-Example: **Pioneer Vol+**
+Example:  
+**Pioneer Vol+**
 
 `20:24:34 MQT: tele/sonoff/IR1/RESULT = {"IrReceived":{"Protocol":"PIONEER","Bits":64,"Data":"0xA55A50AFA55A50AF","DataLSB":"0xA55A0AF5A55A0AF5","Repeat":0}}`