Tasmota: tasmota reset without button

[elzershark]

tasmota reset without button.
a led Bulb (Tuya) have not a Button.
can the software reset without button? by bulbs reset is 5x
without electricity by tuya.
can you install that?

by wrong password in wifi, and the lamp can no longer be used. ore wrong ssid. ore wrong password in web interface

wrong password wifi.. = in router delete the wlan password. bulb is ok
wrong ssid = not to use lamp
wrong web password interface = not to use lamp

[netpok]

I don't really understand your message sorry, but:

• wrong wifi ssid and/or password: if you know the ssid or password you entered just set that temporarily in router
• wrong admin password: if you have mqtt configured you can reset it via that

Last chance:
Also since tasmota uses GET request for forms you should check your history, maybe it's there look for entries with name of Sonoff - Save configuration where Sonoff is the configured name of the device.

for example the following link
http://sp10/co?t1=%7B%22NAME%22%3A%22Generic%22%2C%22GPIO%22%3A%5B23%2C22%2C24%2C17%2C134%2C132%2C0%2C0%2C131%2C52%2C21%2C0%2C0%5D%2C%22FLAG%22%3A0%2C%22BASE%22%3A67%7D&p1=SecretPassword&b1=on&a1=Sonoff&a2=Sonoff2&a3=Sonoff3&a4=Sonoff4&b2=0&save=
contains the password (SecretPassword in this case) for web interface in the p1 parameter.

Any other cases you are out of luck and you probably have to open the case (or find a bug in the code, but then please report it).

[elzershark]

no, you can not send a mqtt command, when you not have the password, ssid, wlan ore what ever 😊
For lamps, there should be a possibility that reset over "de-energized". for example Switch 5x (de-energized)

[ascillato]

Hi

At this moment, Tasmota has a bootloop protection routine that if Tasmota starts and resets (or loose power) in less than 2 seconds, and this happens several times in a row, Tasmota will start changing settings to default, one by one. I think that 10 cycles in a row put mostly settings to default. But wifi and mqtt settings will remain.

May be, can be added an extra configuration key at compiling time to make Tasmota full reset if it is performed 11 cycles of less than 2 seconds of power ON for each cycle.

What do you think?

[netpok]

Actually no, there really shouldn't be an option for this as it is a huge security hole, if you want you can (but really shouldn't) set WifiMode to 2 then if you start the device and it can't connect to wifi it starts up in AP mode, but that doesn't solve the wrong web password.

You're better off writing down your passwords, of course only in a secure way like using pass.

If you still want it against all my explanation, all I can do for you is implement WifiMode 6 as WifiManager without web password since it would take up probably less then 10byte of code space and there are enough already reserved eeprom for it. But no one should really use anything other than WifiMode 0, 4 or 5 in production environment.

[netpok]

@ascillato I haven't checked that code, but will later today as it should do a full reset on all eeprom pages because of security reasons.

Edit: checked it and it clears all settings pages, so no security hole there.

Reset count is stored in the RTC eeprom as far as I know and that's not retained after a power loss, also most devices cannot be resetted with that frequency, because of power supply capacitors.

[ascillato]

That was just an idea to be reviewed. Just simple as 11 power on/off of the bulb energy in less than 2 seconds each ON (as some original firmware do for these type of devices) and just perform a reset 1 command after that.

[netpok]

After checking the code it is possible in a secure way without exposing the config.

Also this wasn't meant against your idea I wrote the first comment without seeing yours.

[ascillato]

Also this wasn't meant against your idea I wrote the first comment without seeing yours.

Hehehe, don't worry about that. An idea polished by several people is always a better idea.

[andrethomas]

I have reset devices this way... sometimes intentionally and other times unintentionally :)

[netpok]

I tried it with the SP10 smart socket I couldn't get it to remember the boot count after power loss, so I'm thinking this could be done only by saving the fast reset count to eeprom, so waiting for owners opinion.

Also there is no option to reset the device this way since the last case is:

      if (RtcReboot.fast_reboot_count > Settings.param[P_BOOT_LOOP_OFFSET] +4) {  // Restarted 6 times
        Settings.module = SONOFF_BASIC;             // Reset module to Sonoff Basic
  //      Settings.last_module = SONOFF_BASIC;
      }

@andrethomas is it possible that you were talking about the buttonpress reset method?

[andrethomas]

Yes, the button method.

The fast reboot counter will not work as it requires the rtc memory to be active (powered) so power cycling a device will not cause a revert to factory defaults... it can work if you have a reset pin connected... i.e. being able to reboot the device without it having lost power.

[netpok]

Okay, just the original problem was that the device doesn't have buttons :)

[andrethomas]

Yes, but I'm not totally sure whether this is a question to a current problem or a feature request...

[DavinKD]

Just want to throw my .02 in. It would be nice to be able to reset bulbs with no buttons. The ones I have were able to do so when flashed with the Tuya stuff, so there should be a way to do it. This is not a high priority for me, though, as all my bulbs are working fine.

[netpok]

My best idea currently is to implement a WifiConfig 2 like interface, but only with a big reset button

[andrethomas]

Will need to think about how this can be implemented in flash without wearing the flash out too much...

[netpok]

That's why I suggested the new WifiConfig as it doesn't need flash writes opposed to boot counting.

[andrethomas]

Yes, correct wificonfig will solve it - not sure how the tuya flash thing works yet and how that initial binary is configured.

[elzershark]

The reset without a button should be feasible. There are too many password problems at the moment. There have already been some lights "broken" because
for example in the password "* #" was present and thus had no access to the light bulb.
the symbols * # can not handle tasmota. If you enter these characters a password, that's it with the light bulb

[netpok]

If * was present in the password field, it did not get saved in firmwares before 6.4.17 (it is fixed now), so it should wait for an open network. Please try to set your AP into Open authentication mode and try to connect to the device, it should appear in the DHCP client list of the router.

Also # shouldn't have any effect on the saving of password, but spaces may cause problem when on the edge of the password, I don't know if that affects Tasmota but as rule of thumb you shouldn't start or end a password with spaces because many webpage trims them.

[elzershark]

fact that * causes the lamp to become unusable. It is automatically generated in some browsers at the webpage setting where you can create a password. If somebody presses "save" without first deleting the password, that was the light source. Also, you can then send no mqtt command, so that the bulb can be reset. Therefore, it is urgently advised not to flash bulbs with tasmota. it is too dangerous that the bulb will be unusable

[netpok]

Did you try to recover it with an open network as I mentioned above?

Other thing, but related to password handling, does tasmota supports WEP?

[elzershark]

wenn man ein passwort aus versehen vergibt bei der webseiten passwort erstellung., hat man kein zugriff mehr auf die lampe. weder per mqtt noch sonstwie. ich rede nicht vom wlan passwort :)

if you assign a password you forgave the webpage password creation, you have no access to the lamp. neither by mqtt nor otherwise. I'm not talking about the wireless password

(contains the password (SecretPassword in this case) for web interface in the p1 parameter.=)
SecretPassword for web interface. = ** =
that was it. The lamp is no longer controllable

the 8x * comes automatically from tasmota in the setting. who clicked on "save" has made his lamp useless

[netpok]

In older firmwares it was handled with:
if(strchr(p1,'*')) p1=""; => if p1 contains *
So it looks for an open network like this:

If you set that up on your router you will be able to recover it, also we are looking into possible solutions to implement device reset as you requested.

[elzershark]

https://www.youtube.com/watch?v=cNdgpF3N8Ao

[elzershark]

is synonymous only 1 * in the password, it was that. tasmota can not recognize * in the password

If you set that up on your router you will be able to recover it, also we are looking into possible solutions to implement device reset as you requested....

ok 👍

[netpok]

With web password I don't know what you can do, but if the wifi password was bad you should try the open network because it checked with strchr(p1,'*'), so it was a contains check instead of an equality check. (Sorry, I wrote a wrong example, now corrected)

Also, you can't loose anything by trying it out (I made that mistake in the past too, and this solved it).

[elzershark]

ich hoffe mein problem hat man verstanden. Die lampe hat ein passwort bekommen, was nicht bekannt ist, für die web- oberfäche. Die lampe ist im wlan. aber man kann nicht über mqtt oder sonstwie zugriff zu ihr bekommen. die lampe hat mqtt einstellungen. aber weil das ein passwort für die web oberfläche vorhanden ist, kann man keine befehle über mqtt senden. man kann auch nicht über mqtt befehl die lampe resetten. weils das resetten nur über ein button funktioniert, ist diese lampe unbrauchbar geworden. das nur zum verständnis. deshalb muss es für lampen eine möglichkeit geben sie zu resetten ohne ein button.
😁

I hope my problem has understood. The lamp received a password that is not known, for a web interface. The lamp is in the wifi. but you can not get access to it via mqtt or otherwise. The lamp has mqtt settings. but because there is a password for the web interface, you can not send commands via mqtt. you can not reset the lamp via mqtt command. because the reset works only with a button, this lamp has become unusable. that only for understanding. therefore there must be a way for lamps to reset them without a button.
😁

[andrethomas]

If the device is reachable via mqtt you can send a reset 1 via mqtt to the device.

[elzershark]

ich gebe es auf. man versteht es nicht. Wenn ein web-passwort existiert.. egal ob es bekannt ist oder nicht, hat man kein zugriff über mqtt auf die lampe. Wenn das web-passwort nicht bekannt ist, kann man mit der lampe nie wieder etwas steuern. ausser man macht die lampe kaputt und flasht sie neu über die hardware. unbekanntest web- passwort = kein mqtt = kein sonstwas. es ist dann eine tote lampe..

[netpok]

Yes, if you haven't set up the mqtt, the only options are flashing via serial connection, or looking for the password in your history. I made an implamentation for what you want, but that will be only available in future versions (if it is accepted). So you're probably out of luck wit those lights.

[andrethomas]

Have you tried to get it to glitch by powering on and off in 1-second intervals?

[elzershark]

das web-passwort wurde nicht "vergessen". es wird IMMER von tasmota selber erstellt. wie im video zu sehen ist. wer aus versehen, einfach nur auf "speichern" klickt, hat damit seine lampe zerstört. es wird dadurch das passwort **.. Also 8x der Stern, Sternchen wird gespeichert. Diese Sternchen kann aber Tasmota nicht verarbeiten. Wenn man als passwort danach 8x *`eingibt, wird es nicht anerkannt. weil Tasmota keine * verarbeiten kann. es wird nicht als passwort anerkannt. Also.. wer auf "speichern" klickt, ohne vorher das Feld "Passwort" zu löschen, zerstört seine Lampe
Und man kann keine mqtt befehle versenden wenn ein passwort in der weboberfläche existiert. das hat noch nie funktioniert. also kann man auch keine mqtt befehle senden, empfangen oder was auch immer. in der lampe ist das wlan passwort und ssid vorhanden. auch sind alle mqtt einstellungen vorhanden. es gibt aber das web-passwort was aus 8x * besteht. dadurch hat man kein zu griff mehr auf mqtt. weder senden noch empfangen.

[andrethomas]

If you did not specify a password (i.e. leaving it as **) then remove the password from your router so that it is an open network without a password - then the device should connect.

[netpok]

His problem is the web admin password, but at least for the last 4 months it is handled with the following line:

strlcpy(Settings.web_password, (!strlen(tmp)) ? "" : (strchr(tmp,'*')) ? Settings.web_password : tmp, sizeof(Settings.web_password));

If the password contains a *, it keeps the old password.

[netpok]

If you have setup an mqtt connection just send it in with a client, like
mosquitto_pub -h <broker> -t cmnd/<device-topic>/reset -m 1

[elzershark]

If you have setup an mqtt connection just send it in with a client, like
mosquitto_pub -h <broker> -t cmnd/<device-topic>/reset -m 1

NO

[andrethomas]

which version of Tasmota is on the device?

[elzershark]

Das hat nichts mit der version zu tun... egal.. ich gebe es auf..

[andrethomas]

Das hat nichts mit der version zu tun... egal.. ich gebe es auf..

Does it not occur to you that I ask this question intentionally?

[netpok]

A specific version could have a bug which you can use to access your device.

[elzershark]

i have all versionen.. the new version an 7 before. in all versionen is "standard "***"

[andrethomas]

Ok, I'm out :)

[elzershark]

und ein anderes problem. aber das muss ich erst noch richtig testen. 1 lampe kann man flashen. da funktioniert alles so wie es sein soll. in iobroker, Sonoff Adapter. Aber sobald man mehrere lampen geflasht hat, fangen alle nach einer gewissen zeit an zu blinken, weil sie sich gegenseitig die IP Adressen austauschen. aber das wird noch dauern. daher kann ich nur jeden rate, wer lampen in iobroker oder mit mqtt bedienen möchte, das erst mal zu lassen. aber das ist eine andere geschichte..

[netpok]

If you have a star in the password field it will not be saved no matter if its 1 or 11.

Also I don't get your last message, IP addresses shouldn't matter, as each device should have a different topic.

[elzershark]

If you have a star in the password field it will not be saved no matter if its 1 or 11.

Also I don't get your last message, IP addresses shouldn't matter, as each device should have a different topic.

Doch, wird gespeichert. im Flash sind die 8 sterne vorhanden.. (Google Chrome) in firefox nicht

[netpok]

No it doesn't you will always get 8*-s as its masking out the password.

Also I'm following andrethomas too...

[elzershark]

https://www.youtube.com/watch?v=cNdgpF3N8Ao

Wenn ich da speichern drücken würde, würde ich das gerät kaputt machen

[netpok]

Yes and that won't be saved because the code above prevents it, feel free to check out the code.

[elzershark]

*

[meingraham]

Ich denke, @netpok bedeutet "check out the code" nicht darin zu suchen, was der browser rendert, um das eigentliche passwort zu maskieren, sondern vielmehr, was das programmmodul im GitHub-Code-Repository zum Speichern und Verwenden des tatsächlichen macht Kennwort übertragen, aber nicht übertragen oder auf einer Remote-Schnittstelle anzeigen, was die Sicherheit beeinträchtigen könnte, die Sie zu gewährleisten versuchen.

I was hoping that replying (as provided by Google Translate) in Deutsche, a language that is not used by those providing support on this forum but rather using the your native language which you insist on using will help convey to you what I mean. After all, a dialog using languages which we don't mutually share will surely enhance communication manifestly; yes?

[netpok]

@elzershark This just got merged into development, you can test it. You
just need to activate it with WifiConfig 7 in the console.

[elzershark]

👍

[ascillato2]

Closing this issue as the feature has been added.

Thanks everyone for sharing theirs ideas. :+1:

[RyanEwen]

Hey guys I have some Globe RGB bulbs which I flashed with 6.4.1 (and one with 6.5.0) that I am needing to reset after updating the hostnames caused them to drop off the network and never come back.

The firmware had my SSID and MQTT settings hardcoded, so resetting them should get them back online.

However I can't figure out how to reset them. Stock f/w is 6 power cycles quickly. I see in here the idea of doing it 10 or 11 times. The light is just flashing white/green/white/green indefinitely.

Is this reset feature in 6.4.1 or 6.5.0 and how exactly does it work? Didn't see it in the wiki anywhere.

[meingraham]

Booting and then booting again within 10 seconds each time for six consecutive cycles should successively reset settings on the device. This reset scheme was implemented in the 6.2.1 timeframe.

[RyanEwen]

I tried that but it wasn't working for me.

However I noticed on a working device that when I was changing hostnames, my Wifi SSID was being changed. My SSID has an apostrophe in it. It was being cutoff from that point on.

So I setup my phone as a hotspot with the truncated name and all my messed up bulbs connected to it and I was able to reconfigure them :)

[meingraham]

Ah... special characters - https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#ssid

... do not use special characters or white spaces in the SSID...

[RyanEwen]

Ah... special characters - https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#ssid

... do not use special characters or white spaces in the SSID...

Fair enough although I've been using these for over a year with this SSID, but I have never changed the hostname in the UI before now to see any issues.

The apostrophe seems to be supported just fine however the UI doesn't show the full SSD from that point on. If I just finish it off (edit "The Three R" to "The Three R's" and hit save, it seems to work fine though.

I was able to recover 5 of the 6 bulbs I buggered up by using my phone as a hotspot with the truncated SSID. The 6th bulb must have something else going on with it and I can't seem to reset it.

I made sure to update all my working bulbs to v6.5.0 and set Wificonfig 7 to prevent this from happening again. If I want to build that value into my firmware. what do I use in the file? I was using WIFI_CONFIG_TOOL WIFI_WAIT before..

[meingraham]

Good to hear.

FYI - the special character issue is not so much a Tasmota limitation as the Arduino SDK for the espressif ESP82xx chips which Tasmota builds on top of.

WIFI_MANAGER_RESET_ONLY == 7

[stepanov1975]

So how can I put device without a button in AP mode? I didn't find a good explanation. Tried to turn on and then turn off after 7 seconds 6 times. Not helping. v6.5.0

[bramschats]

Same problem here, is there a workaround?

[bramschats]

I flashed my Tuya Smart plug with Tuya-convert and installed Tasmota. In the Tasmota AP mode I gave the plug the wrong SSID or password and I don't know which mistake I have made. The button on the plug doesn't initially work with Tasmota software so it is not available.

Is there a workaround to get the plug up and running again?

[netpok]

After checking the code currently the WIFI_RETRY mode is configured as active no connection method, meaning, there is no way to reset the device when it cannot connect to the network. This is the only viable solution in security terms, because you don't want anybody to be able to reset your device (e.g. a smart bulb with easily accessible switch).

On the other hand this is the worst solution when you made a mistake in configuration, but there is a possibility to save the device without opening it:

• Search in your browser history for 192.168.4.1 (or whatever address you used for configuring it)
• There should be an address like this: http://192.168.4.1/wi?s1=SARAH&p1=secret-password&s2=&p2=**&h=wasser&save=
• In this you see s1: this is your first ap ssid (here: SARAH), p1: the first ap password (here: secret-password), s2 and p2 the same for the second ap, h: the configured hostname for the device (here: wasser)
• After getting the wrong config from this string, just configure an access point with these settings, now you can access your device and reset it (or just correct these settings)
• Restore your original access point configuration and be a happy owner of your devices and don't forget to take more care next time

[bramschats]

Thnx for the reply. It is not possible to find the URL since it was a popup for configuring Tasmota AP (Mac). Is it possible to reset the device with soldering some pins together?

[netpok]

Option 1:
There is a chance that tuya-convert uses a modified firmware so first try, that you unplug your ap, connect the device to power and wait some time for a new network to pop up.

Option 2:
If you haven't, try holding the button for 40 seconds first.

Option 3:
There is a possibility to reset it via shorting GPIO0 to GND for at least 40 seconds (as described here https://github.com/arendst/Sonoff-Tasmota/wiki/Button-usage) because GPIO0 is the default Button 0.

The problem here is that it needs to be connected after boot because it's also used by the esp to enter flash mode on boot, so when you connect while it is shorted it won't start the firmware and as result it can't reset the device.

Be careful there is a 99% chance that the plug/bulb whatever the device is using an unisolated power supply, meaning there is a chance based on what orientation* you plugged in the device, that the GND is directly connected either to the live or the neutral. The safest way is to provide external power from a 3.3v power source, but as long as you carefully handle it (like using insulated wire and not touching any metal) you can do it while plugged in.

*: Yes, I recognized this only applies to the european schuko plug.

[bramschats]

Going to try this: https://github.com/arendst/Sonoff-Tasmota/wiki/Gosund-SP1?fbclid=IwAR3gV_vVQIgwVPrwXxH3m7fEh2clBPFDiDuMJ20MZ5_z95HX9FNKswANlm4

[bramschats]

I was able to reflash the device using this howto! thnx... 👍

[hg42]

just to add some info for those who find this thread, because they have a similar problem (like I did).

My first two devices failed.
Each had two misconfigurations at once:

• a wrong wifi password (one simply mistyped and another had stars, which I could see in the browser history)
• the model was unconfigured, so the button didn't work

I could revive the first, by guessing the wrong password and using it temporarily in the wifi access point.

At the end I also managed to fix the other, after reading this thread. I would never have tried that without a hint (I simply cannot think "wifi" without "password").
In short, if you used the wrong wifi password in your configuration, simply disable security on the wifi access point.

My initial sequence of configuration was to do wifi first. Unfortunately the device boots (which was unexpected).
So, I think it's more secure to configure the model first, because you get a working button (in case it's not on the default IO pin).

Btw. I would prefer to first configure everything and then save it all at once. This would prevent problems with the sequence of configuration pages and I think it would also reduce the number of writes to the flash.

Thanks especially to @netpok for all the hints.

[meingraham]

@hg42

I would prefer to first configure everything and then save it all at once.
If you use a Backlog command with all of your settings, it will accomplish what you want.

Removing the password from the AP is suggested here as one of the means of recovering from incorrect Wi-Fi credentials - https://github.com/arendst/Sonoff-Tasmota/wiki/FAQ#i-entered-the-wrong-wi-fi-information

Mike

[hg42]

@meingraham thanks for mentioning the backlog, I guess I should have a look at the console...
The documentation is much better than expected.
When searching, I first found this issue/thread, because of the words I used. Afterwards I found a lot more info. May be too much... :-)