Updated FAQ (markdown)

FAQ.md

@@ -40,11 +40,11 @@
 ### [I cannot find an answer to my problem here](#I-cannot-find-an-answer-here)
 ## Installation
 <a id="A1"></a>
-#### Cannot enter flash mode
+### Cannot enter flash mode
 If your on device button doesn't allow you to enter flash mode or there is none, you can always connect GPIO0 and GND pins directly on the chip. Search on the internet for your chip pinouts and use [the tutorial](https://github.com/arendst/Sonoff-Tasmota/wiki/Hardware-Preparation#bringing-the-module-in-flash-mode).
 
 <a id="A2"></a>
-#### Flashing issues
+### Flashing issues
 Double check if you wired the device the serial-to-USB adapter correctly. Almost every device needs RX and TX pins switched to TX and RX. See [Hardware Preparation](Hardware-preparation) for more.
 
 Another common problem are the jumper cables used. Try another cable if you keep getting connection errors or check the cables for connectivity. Most of them are made cheaply and it happens quite often that those cables do not offer a good connection because of bad crimping or broken copper lines in them.
@@ -62,20 +62,20 @@ If the flash completes successfully, but you get a hash mismatch (esptool.py err
 If esptool.py stops at "Uploading stub...", use --no-stub 
 
 <a id="A4"></a>
-#### Device is hot to the touch
+### Device is hot to the touch
 Do you remember the **NEVER EVER FLASH WITH 5V!**?
 
 Better unpower your device and check if the wiring is correct and the voltage is on your FTDI is set to 3.3V. 
 If you've connected VCC to the wrong pin it might cause your device to overheat and destroy it.
 
 <a id="A5"></a>
-#### Sonoff 4CH V2 / Sonoff Dual V2 won't flash
+### Sonoff 4CH V2 / Sonoff Dual V2 won't flash
 Testing with two different (fairly new) FTDI boards and two Sonoff 4CH v2.0 and the Sonoff Dual v2.0 boards I found that I was getting errors uploading sketches i.e. "warning: espcomm_sync failed" basically a lack of communication between the two devices.
 
 I found that the problem in both Sonoff's was that instead of the FTDI Sonoff cross-over TX->RX and RX->TX I had to do TX->TX RX->RX this then allowed me to upload the sketch.
 
 <a id="A6"></a>
-#### Flashing fails on MacOS High Sierra
+### Flashing fails on MacOS High Sierra
 Related to issue [#957](https://github.com/arendst/Sonoff-Tasmota/issues/957#issuecomment-338779258).
 
 Solution:
@@ -84,14 +84,14 @@ Solution:
 3. After reboot, plug the FTDI USB/serial converter. Accept the security alert from MacOS.
 4. Restart the flash process. It works!
 
-#### There was white smoke and the device doesn't work anymore!
+### There was white smoke and the device doesn't work anymore!
 Yes, you've released the fabled "white smoke", the mysterious substance all electronic devices work on. 
 
 In the immortal words of Doctor Bones: **It's dead Jim!**
 
 ## Wi-Fi
 <a id="B1"></a>
-#### Cannot connect to Wi-Fi 
+### Cannot connect to Wi-Fi 
 If your device does not connect to your Wi-Fi and you've made sure the Wi-Fi credentials are correct, it is caused by using special chars or white spaces in your SSID or Password of your Wi-Fi. Remove them and try again. Other reason can be using an SSID longer than the allowed 32 characters.
 
 With some Wi-Fi routers (i.e. Linksys with DD-WRT), you may have conflicts with the 5GHz radio. Don't choose _"Mixed"_ option. Select _"AC/N-Mixed"_ instead. Moreover, you probably should disconnect 5GHz radio during the configuration process.
@@ -99,7 +99,7 @@ With some Wi-Fi routers (i.e. Linksys with DD-WRT), you may have conflicts with
 DD-WRT also has Wi-Fi Multi-Media (WMM) enabled by default.  Disabling WMM can resolve connectivity issues.
 
 <a id="B2"></a>
-#### I entered the wrong Wi-Fi information
+### I entered the wrong Wi-Fi information
 Every device with a button can initiate Wi-Fi AP configuration mode with 4 short presses of the button. 
 
 If you flashed a light bulb or any device without a built-in button and entered wrong Wi-Fi password you now have a device that won't connect to your Wi-Fi and you have no button to force [Wi-Fi Configuration](Button-usage).
@@ -111,7 +111,7 @@ Now simply connect to the same AP and open the web UI, triple check your ssid an
 If you are unsure what SSID you have entered, you can try to find that with special Wi-Fi sniffing tools. For example [Nirsoft WifiChannelMonitor](https://www.nirsoft.net/utils/wifi_channel_monitor.html) can show your mistakenly configured SSID name.
 
 <a id="B3"></a>
-#### Wi-Fi reconnects
+### Wi-Fi reconnects
 
 First thing to try when having Wi-Fi issues:
 
@@ -128,7 +128,7 @@ If you still have issues, you should look into your Wi-Fi network:
    The same Mesh may be stable in one area and lead to unwanted Tasmota reconnects in other areas, presumably when the signals of access points overlap with similar strength. If disabling Mesh Networks is not an option, then keeping the network busy, e.g. by issuing a Ping from another host every 20 seconds has helped to avoid the reconnects.
 
 <a id="B4"></a>
-#### Wi-Fi Stops Working
+### Wi-Fi Stops Working
 There have been many reports of Wi-Fi no longer working after it was working for a while.
 
 Every time this has been reported, it's ended up being a hardware or signal interference problem.
@@ -141,14 +141,14 @@ All you can really do is check the solder joints, move the device closer to your
 
 ## MQTT
 <a id="C1"></a>
-#### Cannot connect to my MQTT broker
+### Cannot connect to my MQTT broker
 Make sure you've [configured MQTT](MQTT) correctly. If that didn't solve the issue check your MQTT broker logs. 
 Most likely problem is your broker doesn't allow logins for your Tasmota configure used or your ACL settings do not include your device.
 
 In some very specific cases the MQTT broker code clashes with the Arduino Core and doesn't allow a connection. In that case create a different user for your device, try another core binary or a different MQTT broker.
 
 <a id="C2"></a>
-#### Frequent MQTT reconnects
+### Frequent MQTT reconnects
 Most MQTT reconnect messages are linked with Wi-Fi instability first. Resolve any Wi-Fi issue first!
 
 If the console shows repeated messages like:
@@ -180,10 +180,10 @@ For MQTT disconnections with Arduino core v2.5.0, please try command:
 
 ## Device
 <a id="D2"></a>
-#### Relay clicks and LED flashes at 1 sec intervals
+### Relay clicks and LED flashes at 1 sec intervals
 This indicates that your device did not get flashed properly. In this case it will toggle all it's pins at 1 sec intervals. A flash erase and a new flash is required.
 <a id="D3"></a>
-#### Status LED blinking
+### Status LED blinking
 Your device status LED blinks repeatedly when Wi-Fi and/or MQTT is not connected. If you're not using MQTT and did not configure it the status LED will still keep blinking.
 
 You can disable status LED blinking using:
@@ -193,7 +193,7 @@ Backlog LedPower 0; SetOption31 1
 
 
 <a id="D4"></a>
-#### My device randomly switches on and off. Do I have ghosts in my house?
+### My device randomly switches on and off. Do I have ghosts in my house?
 Most of the issues with random, or "ghost", switching are related to MQTT retain settings. In short, your MQTT broker is retaining a message with the POWER status of the device which gets applied on reboots. [Solution here](PowerOnState-Configuration#side-effects-with-using-mqtt-messages) 
 
 This short [10 minute video by TheHookUp](https://www.youtube.com/watch?v=31IyfM1gygo&t=15s) nicely explains what it is and how to prevent it. 
@@ -201,12 +201,12 @@ This short [10 minute video by TheHookUp](https://www.youtube.com/watch?v=31IyfM
 Other cause can be of electrical nature. Ff you have connected an external switch using long wires they can pick up stray signals and cause the voltage on the GPIO to vary. [Solution here](https://github.com/arendst/Sonoff-Tasmota/wiki/Expanding-Sonoffs#electrical-considerations) 
 
 <a id="D6"></a>
-#### Cannot find my device in Modules
+### Cannot find my device in Modules
 
 If you flashed a device which is not listed in the Modules list, use [Templates](Templates) to configure your device. Try looking for it first in the [Templates Repository](http://blakadder.github.io/templates).
 
 <a id="D7"></a>
-#### Device keeps restarting after changing config over MQTT
+### Device keeps restarting after changing config over MQTT
 If you changed configurations over MQTT, the command can fail due to a bug and the command is repeatedly sent, causing the device to restart.
 
 The restart is normal if you change something at the device configuration.
@@ -219,18 +219,18 @@ Read also:
 - [#2716](https://github.com/arendst/Sonoff-Tasmota/issues/2716)
 
 <a id="D8"></a>
-#### Can you add this unsupported sensor to Tasmota
+### Can you add this unsupported sensor to Tasmota
 
 Short answer: **NO!**
 
 Long answer: There is not enough time in our coders lives to take requests, if you can code a driver for that sensor and submit a PR it will be considered, otherwise you can only wait for someone else to do it.
 
 <a id="D9"></a>
-#### Tasmota is sending a lengthy status update (`STATUS` - `STATUS11`) every 5 seconds. What's going on?
+### Tasmota is sending a lengthy status update (`STATUS` - `STATUS11`) every 5 seconds. What's going on?
 Turn off [TasmoAdmin](TasmoAdmin)! It is polling your device with `STATUS 0` command with a HTTP request every 5 seconds which causes the status updates and unneccessary stress load on the device. In some cases it might even interfere with normal device operation.
 
 <a id="D10"></a>
-#### I modified the Web Admin password (`Configure Other`) and now I cannot access the web interface.
+### I modified the Web Admin password (`Configure Other`) and now I cannot access the web interface.
 You have set up a password for the web interface. You can login with the username `admin` and the password you entered.
 
 However, if you don't remember that password there are a few options you can try to gain access to the web interface again.
@@ -257,28 +257,28 @@ However, if you don't remember that password there are a few options you can try
 5. If nothing helps, then you have to [flash the firmware](Flashing) again using the serial interface. Be sure to erase the flash memory before uploading the binary.
 
 <a id="D11"></a>
-#### Power monitoring shows wrong values
+### Power monitoring shows wrong values
 If the values shown in the Web UI don't seem right and you're using a Supported Module you need to [calibrate the power monitoring sensor](Power-Monitoring-Calibration).
 
 In case you're using a template you created yourself or found in our Templates Repository try the calibration method first. If the values are still wrong or unrealistic the power monitoring sensors' GPIOs are not configured correctly and you will need to find the correct GPIO assignments before proceeding.
 
 <a id="D13"></a>
-#### Sensors don't show values
+### Sensors don't show values
 Make sure your sensor is properly wired and the GPIOs assigned. 
 Your vanilla `sonoff.bin` doesn't have complete sensor support. Make sure you've installed sonoff-sensors.bin that support the largest number of sensors. Some sensors require enabling in the code and compiling your own binary. See [Builds](Builds) for a comprehensive list of supported components.
 
 <a id="D14"></a>
-#### Timers trigger at wrong time
+### Timers trigger at wrong time
 Check if Tasmota is updating its device time over the preconfigured NTP servers and that the time matches your local time. If not, adjust your [`TimeZone`](Commands#timezone) or Daylight Saving Time 
 
 <a id="D15"></a>
-#### Autodiscovery in Home Assistant doesn't work
+### Autodiscovery in Home Assistant doesn't work
 Binary sonoff-basic.bin (which comes packaged with Tuya Convert) does not support autodiscovery. Please upgrade to sonoff.bin or similar release that supports this feature.
 
 Make sure its enabled in Tasmota it with `SetOption19 1` and you configured the  Home Assistant MQTT integration with Discovery enabled.
 
 <a id="D16"></a>
-#### Why is my changed config not loaded?
+### Why is my changed config not loaded?
 If you have flashed a precompiled binary, be aware that all the configuration made after the flash (Wi-Fi, MQTT, topics, names, rules, etc) will be lost in a factory firmware reset.
 
 **In short**: The CFG_HOLDER is the place where the config is stored on your device. The device checks if a config is saved in this CFG_HOLDER (value from the my_user_config.h) and always loads this if exists.
@@ -312,11 +312,11 @@ On every start the device compares the header of FCA with the CFG_HOLDER from yo
   - start your device and issue command `Reset 1` or `Reset 2`
 
 <a id="D17"></a>
-#### How do I invert the output of the green LED on the Sonoff basic so the LED is on when the relay is off?
+### How do I invert the output of the green LED on the Sonoff basic so the LED is on when the relay is off?
 [`LedState`](Commands#ledstate) default value is `1` (on) - Show power state on LED. The LED can be disabled completely with `LedState 0` (off).  However, there is no option to invert the output of the green LED on the Sonoff basic.
 
 <a id="D18"></a>
-#### What is this Arduino Core
+### What is this Arduino Core
 
 Arduino Core (open source) are the core libraries for ESP8266/ESP8285 chips to make them Arduino Framework Compatible. This Core is programmed on top of the Espressif SDK (closed source). 
 
@@ -370,7 +370,7 @@ Example: Core-/SDK-Version: **2_3_0**/1.5.3(aec24ac9)
   - If the Wi-Fi router has auto channel, channel switching is not reliably  managed by this core. Use Fixed Channels in the router instead.
 
 <a id="D19"></a>
-#### Config problems 
+### Config problems 
 
 Can cause boot loops, items to not appear, wrong config values, etc