mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Additional wrong Wi-Fi method, Bootloop entry correciton

Michael Ingraham 2019-09-03 09:13:29 -04:00
parent 494ae75de5
commit 7f132c4aae
1 changed files with 27 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
FAQ.md

@ -22,7 +22,7 @@
- [Relay clicks and LED flashes at 1 second intervals](#Relay-clicks-and-LED-flashes-at-1-second-intervals) - [Relay clicks and LED flashes at 1 second intervals](#Relay-clicks-and-LED-flashes-at-1-second-intervals)
- [Status LED blinking](#Status-LED-blinking) - [Status LED blinking](#Status-LED-blinking)
- [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) - [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)
- [Device resets to defaults every minute or so](Button-usage#pressing-the-button-for-over-40-seconds) - [Device resets to defaults every minute or so](#Device-resets-to-defaults-every-minute-or-so)
- [Cannot find my device in Modules](#Cannot-find-my-device-in-Modules) - [Cannot find my device in Modules](#Cannot-find-my-device-in-Modules)
- [Device keeps restarting after changing config over MQTT](#Device-keeps-restarting-after-changing-config-over-MQTT) - [Device keeps restarting after changing config over MQTT](#Device-keeps-restarting-after-changing-config-over-MQTT)
- [Can you add this unsupported sensor to Tasmota](#Can-you-add-this-unsupported-sensor-to-Tasmota) - [Can you add this unsupported sensor to Tasmota](#Can-you-add-this-unsupported-sensor-to-Tasmota)
@ -41,11 +41,9 @@
### [I cannot find an answer to my problem here](#I-cannot-find-an-answer-here) ### [I cannot find an answer to my problem here](#I-cannot-find-an-answer-here)
## Installation ## Installation
<a id="A1"></a>
### Cannot enter flash mode ### Cannot enter flash mode
Be sure to press the button correctly, you must "feel" a click. If your on-device button doesn't allow you to enter flash mode or there is no GPIO0 broken out to the PCB, you can always bridge GND to GPIO0 pin directly on the chip. Search on the Internet for your chip's pinouts and use [the tutorial](https://github.com/arendst/Sonoff-Tasmota/wiki/Hardware-Preparation#bringing-the-module-in-flash-mode). Be sure to keep GPIO0 grounded long enough (3-5 seconds) before disconnecting to ensure the chip has booted completely into programming mode. On devices that do not provide a GPIO0 connected button, it may be easier to leave the wired bridge in place throughout the entire flashing process (erase & upload). Doing so will not create any problems for flashing the device. After the firmware is uploaded successfully, remove the bridge. This allows the device to boot normally. Be sure to press the button correctly, you must "feel" a click. If your on-device button doesn't allow you to enter flash mode or there is no GPIO0 broken out to the PCB, you can always bridge GND to GPIO0 pin directly on the chip. Search on the Internet for your chip's pinouts and use [the tutorial](Hardware-Preparation#bringing-the-module-in-flash-mode). Be sure to keep GPIO0 grounded long enough (3-5 seconds) before disconnecting to ensure the chip has booted completely into programming mode. On devices that do not provide a GPIO0 connected button, it may be easier to leave the wired bridge in place throughout the entire flashing process (erase & upload). Doing so will not create any problems for flashing the device. After the firmware is uploaded successfully, remove the bridge. This allows the device to boot normally.
<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. 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.
@ -63,7 +61,6 @@ If the flash completes successfully, but you get a hash mismatch (esptool.py err
If esptool.py stops at "Uploading stub...", use --no-stub 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
Remember - **NEVER EVER FLASH WITH 5V!**? Remember - **NEVER EVER FLASH WITH 5V!**?
@ -75,24 +72,21 @@ Yes, you've released the fabled "white smoke", the mysterious substance all elec
In the immortal words of Doctor Bones: **It's dead Jim!** In the immortal words of Doctor Bones: **It's dead Jim!**
<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. 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. 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). Related to issue [#957](../issues/957#issuecomment-338779258).
Solution: Solution:
1. Install the VCP drivers for Mac from the FTDI website : http://www.ftdichip.com/Drivers/VCP.htm 1. Install the VCP drivers for Mac from the [FTDI website](http://www.ftdichip.com/Drivers/VCP.htm)
2. After install, reboot (it does not work if you do not reboot). 2. After install, reboot (it does not work if you do not reboot).
3. After reboot, plug the FTDI USB/serial converter. Accept the security alert from MacOS. 3. After reboot, plug the FTDI USB/serial converter. Accept the security alert from MacOS.
4. Restart the flash process. It works! 4. Restart the flash process. It works!
## Wi-Fi ## 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. 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.
@ -100,9 +94,8 @@ 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. 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
If you have a device with a button and it is configured as a component in the Tasmota settings, you can try pressing the button to force the device into [Wi-Fi configuration mode](Button-usage) with 4 short presses of the button. If you have a device with a button and it is configured as a component in the Tasmota settings, you can try pressing the button to force the device into [Wi-Fi configuration mode](Button-usage#4-short-presses) 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 it into Wi-Fi configuration mode. 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 it into Wi-Fi configuration mode.
@ -112,7 +105,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. 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.
If these methods don't work, it may still be possible to save the device without opening it to perform a serial flash: If these methods don't work, it may still be possible to save the device without opening it to perform a serial flash. Since Tasmota uses GET request for forms, the password may be in your browser history.
1. Search in your browser history for 192.168.4.1 (or whatever address you used for configuring it) 1. Search in your browser history for 192.168.4.1 (or whatever address you used for configuring it)
2. There should be an entry similar to this: 2. There should be an entry similar to this:
`http://192.168.4.1/wi?s1=<mySSID>&p1=<myPassword>-********&s2=&p2=********&h=hostName&save=` `http://192.168.4.1/wi?s1=<mySSID>&p1=<myPassword>-********&s2=&p2=********&h=hostName&save=`
@ -123,12 +116,11 @@ If these methods don't work, it may still be possible to save the device without
3. After getting the incorrectly entered configuration from this URL, configure an access point with these settings as described above 3. After getting the incorrectly entered configuration from this URL, configure an access point with these settings as described above
4. Access your device and set the correct Wi-Fi credentials 4. Access your device and set the correct Wi-Fi credentials
<a id="B3"></a>
### Device disconnects from Wi-Fi often ### Device disconnects from Wi-Fi often
First thing to try when having Wi-Fi issues: First thing to try when having Wi-Fi issues:
Erase all flash using esptool.py or esptool.exe and flash via serial (as explained [here](Flashing#erase-firmware)) using the latest precompiled bins from http://thehackbox.org/tasmota/. Erase all flash using esptool.py or esptool.exe and flash via serial (as explained [here](Flashing#erase-firmware)) using [the latest precompiled binaries](http://thehackbox.org/tasmota/).
This approach has solved most of the reported issues. Sometimes this is due to a bad flash, a bad OTA or invalid data that remains in the flash where the SDK memory is. This approach has solved most of the reported issues. Sometimes this is due to a bad flash, a bad OTA or invalid data that remains in the flash where the SDK memory is.
@ -140,7 +132,6 @@ 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. 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. There have been many reports of Wi-Fi no longer working after it was working for a while.
@ -153,14 +144,12 @@ We've also seen reports then when a specific LED light bulb was hooked up near o
All you can really do is check the solder joints, move the device closer to your Access Point. If all else fails, replace the device. All you can really do is check the solder joints, move the device closer to your Access Point. If all else fails, replace the device.
## MQTT ## 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. 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 user and password or your ACL settings do not include your device. Most likely problem is your broker doesn't allow logins for your Tasmota configure user and password 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. 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! Most MQTT reconnect messages are linked with Wi-Fi instability first. Resolve any Wi-Fi issue first!
@ -185,42 +174,43 @@ or your mosquitto broker log shows messages like this -
``` ```
You have more than one device connected with the same %topic% defined. Its important that each device has a unique %topic% instead of the default `sonoff`. You have more than one device connected with the same %topic% defined. Its important that each device has a unique %topic% instead of the default `sonoff`.
If that is not the issue, erase all flash using esptool.py or esptool.exe and flash again by wire (as explained [here](#esptool-usage)) using the latest precompiled bins with core v2.3 from http://thehackbox.org/tasmota/020300/. If that is not the issue, erase all flash using esptool.py or esptool.exe and flash again by wire (as explained [here](#esptool-usage)) using [the latest precompiled bins with core v2.3](http://thehackbox.org/tasmota/020300/).
For MQTT disconnections with Arduino core v2.5.2, please try command: For MQTT disconnections with Arduino core v2.5.2, please try command:
`Sleep 0` `Sleep 0`
## Device ## Device
<a id="D2"></a>
### Relay clicks and LED flashes at 1 second intervals ### Relay clicks and LED flashes at 1 second 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. 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. 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: You can disable status LED blinking using:
``` `Backlog LedPower 0; SetOption31 1`
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) 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)
In some cases, adding a switch to a device causes ghost switching. In this case, you may need to add a [low pass filter](https://www.youtube.com/watch?v=aq8_os6g13s&ab_channel=DrZzs) to dampen any spikes on the input. In the case of the Sonoff T1, a modification to [change the filter capacitor](https://github.com/arendst/Sonoff-Tasmota/issues/5449#issuecomment-478471697) on the PCB may be required. In some cases, adding a switch to a device causes ghost switching. In this case, you may need to add a [low pass filter](https://www.youtube.com/watch?v=aq8_os6g13s&ab_channel=DrZzs) to dampen any spikes on the input. In the case of the Sonoff T1, a modification to [change the filter capacitor](../issues/5449#issuecomment-478471697) on the PCB may be required.
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. 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.
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) 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](Expanding-Sonoffs#electrical-considerations)
### Device resets to defaults every minute or so
Your device may be in a boot loop - a restart caused by any exception or watchdog timer within less than `BOOT_LOOP_TIME` (_default 10 seconds_). The number of boot loops allowed before beginning to reset settings is determined by [`SetOption36`](Commands#setoption36). When Tasmota reaches this situation, it will begin restoring default settings as follows:
- 1<sup>st</sup> restart: disable ESP8285 generic GPIOs interfering with flash SPI
- 2<sup>nd</sup> restart: disable rules causing boot loop
- 3<sup>rd</sup> restart: disable all rules
- 4<sup>th</sup> restart: reset user defined GPIOs to disable any attached peripherals
- 5<sup>th</sup> restart: reset module to Sonoff Basic (1)
<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). 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. 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.
@ -229,22 +219,19 @@ The restart is normal if you change something at the device configuration.
You need to clear the retain messages of your HA/Broker/MQTT Server. You need to clear the retain messages of your HA/Broker/MQTT Server.
Read also: Read also:
- [#2140](https://github.com/arendst/Sonoff-Tasmota/issues/2140) - [#2140](../issues/2140)
- [#2658 (comment)](https://github.com/arendst/Sonoff-Tasmota/issues/2658#issuecomment-387112217) - [#2658 (comment)](../issues/2658#issuecomment-387112217)
- [#2716](https://github.com/arendst/Sonoff-Tasmota/issues/2716) - [#2716](../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!** 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. 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. 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 unnecessary stress load on the device. In some cases it might even interfere with normal device operation.
<a id="D10"></a>
### Web Interface Asks for Password ### Web Interface Asks for Password
You modified the Web Admin password (`Configure Other`) and now you 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. You modified the Web Admin password (`Configure Other`) and now you 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,7 +244,7 @@ You modified the Web Admin password (`Configure Other`) and now you cannot acces
2. If the options above are not available: 2. If the options above are not available:
Since Tasmota uses GET request for forms, the password may be in your browser history. Look there for entries with the name you configured for the device. For example, in the following link: Since Tasmota uses GET request for forms, the password may be in your browser history. Look there for entries with the name you configured for the device. For example, in the following link:
```http://[device-ip]/co?t1={"NAME":"Generic"'"GPIO":[23'22'24'17'134'132'0'0'131'52'21'0'0]'"FLAG":0'"BASE":67}&p1=SecretPassword&b1=on&a1=Sonoff&a2=Sonoff2&a3=Sonoff3&a4=Sonoff4&b2=0&save=``` `http://<device-ip>/co?t1={"NAME":"Generic"'"GPIO":[23'22'24'17'134'132'0'0'131'52'21'0'0]'"FLAG":0'"BASE":67}&p1=SecretPassword&b1=on&a1=Sonoff&a2=Sonoff2&a3=Sonoff3&a4=Sonoff4&b2=0&save=`
the `p1` parameter contains the password for the web interface (`SecretPassword` in this case). the `p1` parameter contains the password for the web interface (`SecretPassword` in this case).
@ -265,32 +252,27 @@ You modified the Web Admin password (`Configure Other`) and now you cannot acces
3. If you had set up `WifiConfig 7` as your Wi-Fi fallback method (by previously executing [`WiFiConfig`](Commands#wificonfig) in the Console), you can reset the device by booting it into Wi-Fi Manager mode. If the SSID configured in the device is not available (e.g., turn off the router), the device will fallback to that restricted Wi-Fi Manager Mode. 3. If you had set up `WifiConfig 7` as your Wi-Fi fallback method (by previously executing [`WiFiConfig`](Commands#wificonfig) in the Console), you can reset the device by booting it into Wi-Fi Manager mode. If the SSID configured in the device is not available (e.g., turn off the router), the device will fallback to that restricted Wi-Fi Manager Mode.
4. If your device has a physical push-button, reset the firmware to the default settings as detailed [here](Button-usage#pressing-the-button-for-over-40-seconds). 4. If your device has a physical push-button, reset the firmware to the default settings as detailed [here](Button-usage#long-press).
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. 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). 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. 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. 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. 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 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. 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. 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 configuration not loaded? ### Why is my changed configuration 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. 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.
@ -324,11 +306,9 @@ On every start the device compares the header of FCA with the CFG_HOLDER from yo
- leave CFG_HOLDER as is - leave CFG_HOLDER as is
- start your device and issue command `Reset 1` or `Reset 2` - 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. [`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 an Arduino Core ### What is an 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). 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).
@ -372,7 +352,7 @@ Example: Core-/SDK-Version: **2_3_0**/1.5.3(aec24ac9)
* 2.5.2 (bug fix release of 2.5.0 and 2.5.1): * 2.5.2 (bug fix release of 2.5.0 and 2.5.1):
- All Tasmota features work - All Tasmota features work
- Extend PWM resolution for low brightness lights [(Details)](https://github.com/arendst/Sonoff-Tasmota/pull/5742) - Extend PWM resolution for low brightness lights ([Details](../pull/5742))
- Modem Sleep doesn't work but Tasmota has a CPU dynamic sleep to save energy, so it is not a big issue for this core - Modem Sleep doesn't work but Tasmota has a CPU dynamic sleep to save energy, so it is not a big issue for this core
- Alexa works - Alexa works
- Web UI is fast - Web UI is fast
@ -385,7 +365,6 @@ Example: Core-/SDK-Version: **2_3_0**/1.5.3(aec24ac9)
- Most Routers of brands Ubiquity and Fritzbox don't produces conflicts or disconnections - Most Routers of brands Ubiquity and Fritzbox don't produces conflicts or disconnections
- If the Wi-Fi router has auto channel, channel switching is not reliably managed by this core. Use Fixed Channels in the router instead. - 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>
### Configuration problems ### Configuration problems
Can cause boot loops, items to not appear, wrong config values, etc Can cause boot loops, items to not appear, wrong config values, etc