mirror of https://github.com/arendst/Tasmota.git
Revert 85d947a705313e63e3c0615955c060eda385caee...f57ca71096a9f497a021e3a140075c79a7acb8a0 on FAQ
parent
f57ca71096
commit
0fd10bcd1f
30
FAQ.md
30
FAQ.md
|
@ -1,9 +1,9 @@
|
|||
## Device not in the Module Type list on the Device Configuration page of Tasmota WebUI
|
||||
|
||||
If you flashed a device which is not listed in the module type list, use [Templates](../Templates) to configure GPIOs.
|
||||
If you flashed a device which is not listed in the module type list, use [Templates](Templates) to configure GPIOs.
|
||||
|
||||
## I entered the wrong Wi-Fi password and I have no button to reset config
|
||||
If you flashed a light bulb with [Tuya OTA](../Tuya-OTA) flash and entered wrong Wi-Fi password you now have a device that won't connect to your AP and you have no button to force [Wi-Fi Manager](../Button-usage).
|
||||
If you flashed a light bulb with [Tuya OTA](Tuya-OTA) flash and entered wrong Wi-Fi password you now have a device that won't connect to your AP and you have no button to force [Wi-Fi Manager](Button-usage).
|
||||
|
||||
To solve this you can try creating a new Wi-Fi AP with the same SSID and no (none) authentication. Use an old router, a mobile phone or, if you're desperate, change the settings on your main router (but remember to turn authentication back on when you're done. Depending on the router/phone it will ignore the wrong Wi-Fi password since authentication is set to none and let your Tasmota flashed device connect to it.
|
||||
|
||||
|
@ -12,29 +12,32 @@ 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 wifi sniffing tools. For example [Nirsoft WifiChannelMonitor](https://www.nirsoft.net/utils/wifi_channel_monitor.html) can show your wrongly configured SSID name.
|
||||
|
||||
## 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 every 5 seconds which causes the status updates.
|
||||
Turn off [TasmoAdmin](TasmoAdmin)! It is polling your device with `STATUS 0` command every 5 seconds which causes the status updates.
|
||||
|
||||
## 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](../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](PowerOnState-Configuration#side-effects-with-using-mqtt-messages)
|
||||
|
||||
This short [10 minute video by TheHookUp](https://www.youtube.com/watch?v=31IyfM1gygo&t=15s) explains what it is and how to prevent it.
|
||||
|
||||
## What is the CFG_HOLDER or Why is my changed config not loaded?
|
||||
The CFG_HOLDER is explained [here](../Troubleshooting#cfg_holder-explained)
|
||||
The CFG_HOLDER is explained [here](Troubleshooting#cfg_holder-explained)
|
||||
|
||||
## Alexa says "Device does not respond" after Update to FW > 5.12.0
|
||||
Use this [Workaround](https://github.com/arendst/Sonoff-Tasmota/issues/1639#issuecomment-360218536) or go back to [ExpressIf library 2.3.0](Troubleshooting#wifi-issues-fw--512x-expressif-versions)
|
||||
|
||||
## 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 according to the Sonoff-Tasmota [wiki](../).
|
||||
[`LedState`](Commands#ledtate) 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 according to the Sonoff-Tasmota [wiki](./).
|
||||
|
||||
## I modified the Web Admin password (`Configure Other`) and now I cannot access the web interface.
|
||||
You set up a password for the web interface, you can login with the username `admin` and the password you entered.
|
||||
|
||||
If you don't remember that password, There are a few options you can try to gain access to the web interface again.
|
||||
|
||||
1. Reset the password using the [`WebPassword`](../Commands#webpassword) command.
|
||||
1. Reset the password using the [`WebPassword`](Commands#webpassword) command.
|
||||
|
||||
- If you have serial connection to the device: Execute `WebPassword 0` using a serial terminal interface.
|
||||
|
||||
- If you have configured MQTT: Send `0` to `cmnd/<device-topic>/WebPassword`. You can send it from any [MQTT client](http://www.hivemq.com/blog/seven-best-mqtt-client-tools). You can also use another Tasmota device using the [`Publish`](../Commands#publish) command - Execute `Publish cmnd/<device-topic>/WebPassword 0` from that device's Console.
|
||||
- If you have configured MQTT: Send `0` to `cmnd/<device-topic>/WebPassword`. You can send it from any [MQTT client](http://www.hivemq.com/blog/seven-best-mqtt-client-tools). You can also use another Tasmota device using the [`Publish`](Commands#publish) command - Execute `Publish cmnd/<device-topic>/WebPassword 0` from that device's Console.
|
||||
|
||||
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:
|
||||
|
@ -45,14 +48,11 @@ If you don't remember that password, There are a few options you can try to gain
|
|||
|
||||
_Note: special characters may be appear as the characters' corresponding ASCII hexadecimal codes (e.g., "\{" = '\%7B', etc.)_
|
||||
|
||||
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 pushbutton, 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 pushbutton, reset the firmware to the default settings as detailed [here](Button-usage#pressing-the-button-for-over-40-seconds).
|
||||
|
||||
5. If nothing helps, then you have to [upload the firmware](../Flashing) again with a utility such as [ESPtool](../Flashing#esptool) using the serial interface. Be sure to erase the flash memory before uploading the binary.
|
||||
|
||||
## Alexa says "Device does not respond" after Update to Firmware > 5.12.0
|
||||
Use this [Workaround](../../issues/1639#issuecomment-360218536) or go back to [Expressif library 2.3.0](../Troubleshooting#Wi-Fi-issues-arduino-core-versions-and-espressif-sdk)
|
||||
5. If nothing helps, then you have to [upload the firmware](Flashing) again with a utility such as [ESPtool](flashing#esptool) using the serial interface. Be sure to erase the flash memory before uploading the binary.
|
||||
|
||||
## I need help
|
||||
Check the [Troubleshooting](../Troubleshooting) Section.
|
||||
Check the [Troubleshooting](Troubleshooting) Section.
|
Loading…
Reference in New Issue