-
PROBLEM DESCRIPTION:Purple Wemos S2 Mini was supported in some firmware back in the days, I was succesfull to flash firmware by webinstaller. But now after flashing the wifi manager is not present anymore after uploading. REQUESTED INFORMATIONMake sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Configuration output here:
Rules output here:
STATUS 0 output here:
Console output here:
TO REPRODUCESteps to reproduce the behavior: EXPECTED BEHAVIOURA clear and concise description of what you expected to happen. SCREENSHOTSIf applicable, add screenshots to help explain your problem. ADDITIONAL CONTEXTAdd any other context about the problem here. (Please, remember to close the issue when the problem has been addressed) |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 6 replies
-
|
S2 is supported whatever the board and it's colour |
Beta Was this translation helpful? Give feedback.
-
|
Just using the usb-c connector of my MacBook Pro. Uploader by Arduino IDE works flawless. And it was working before, but I don't know the firmware at the time. It was somewhere begin August 2022 because I orders it late September. |
Beta Was this translation helpful? Give feedback.
-
|
I'm running Wemos S2 Mini with current Tasmota without experiencing connection problems. Note that I'm using the original branded board, not some clone, and I've seen at least one case of a user having significant trouble making a clone board work. |
Beta Was this translation helpful? Give feedback.
-
|
I have a clone indeed, from Ali. But I don't understand why it was working before? Did something change? Do you guys are going to support clone esp32 s2 mini or is it just the build of it? The same esp32 s2 mini clone was working before, after using it for an Arduino IDE project I try to flash it again with tasmota without succes anymore. I have the one with ram not the one without. |
Beta Was this translation helpful? Give feedback.
-
|
Tasmota supports the ESP32-S2 chip variant. Whether some arbitrary board works depends on the hardware, not on Tasmota, and Tasmota does not even try to adapt to what your board happens to be. In case of a bad hardware design, things like power issues can screw up things. This is not only about what power you supply, but about the on-board voltage regulator, and also whether there are suitable capacitors where they should be. The user I told about was able to get it on Wifi while hand-holding the board, but not when letting it go. And of course if there are faults on a specific board, but bad China-clones are a pest. Things going from working to not is a complex issue, but may be up to the hardware and "quality". Minor differences in power draw can also throw off borderline designs. Things may also depend a lot on what you have connected to the board. |
Beta Was this translation helpful? Give feedback.
-
|
After install tasmota and reset S2 mini, are you setting the ssid/pass? If not... it's in ap mode (you will find a wifi network on the phone or PC with the name tasmota-xxxxxx-yyyy; Tasmota Redirecting to new device's IP address |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @Lassska Didn't noticed that it created an AP. Was in the assumption that the browser should redirect me to the device to set the wifi credentials like before over the serial port. |
Beta Was this translation helpful? Give feedback.
-
|
I have seen a similar issue, in that some of my older Wemos D1 modules worked fine with firmware 9.3.1 to 12.x, but with 13.x I stated seeing the boards fail to connect to any access point. Moreover, when flashed with 13.x I could not consistently connect to the boards via default AP at 192.168.4.1. My phone would never connect, which I can use under 9.3.1 to 12.x without issue. My PC would sometimes, rarely connect to 192.168.4.1... but it was unstable. If I take the same board, and flash back to 9.3.1 (to 12.x) it is rock solid wifi connection! So something planned or unplanned is impacting the consistency of the wifi on some older modules with 13.x releases. |
Beta Was this translation helpful? Give feedback.
-
|
As already suggested in the other thread, it is plausible that your troubles are a power-related issue, not a Tasmota issue. And Tasmota is likely to draw a bit more power in version 13.2 than in 9.3.1. |
Beta Was this translation helpful? Give feedback.
-
|
Did you try the same board with 13.1 powered by a better 3.3v PSU?
El El lun, 23 de oct. de 2023 a la(s) 16:56, Jibun-no-Kage <
***@***.***> escribió:
… I have seen a similar issue, in that some of my older Wemos D1 modules
worked fine with firmware 9.3.1 to 12.x, but with 13.x I stated seeing the
boards fail to connect to any access point. Moreover, when flashed with
13.x I could not consistently connect to the boards via default AP at
192.168.4.1. My phone would never connect, which I can use under 9.3.1 to
12.x without issue. My PC would sometimes, rarely connect to 192.168.4.1...
but it was unstable. If I take the same board, and flash back to 9.3.1 (to
12.x) it is rock solid wifi connection! So something planned or unplanned
is impacting the consistency of the wifi on some older modules with 13.x
releases.
—
Reply to this email directly, view it on GitHub
<#18314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXBW4POQEGHQKW57WBLRB3YA3DYLAVCNFSM6AAAAAAWPRXMUGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGNRSHEYTK>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah... I was thinking that too... but I was using 5v 4a stepped down to 3.3v for flashing, then used for testing once flashed. Of course, this issue I am seeing, could be the age of the modules as well, they are older, not used much, but older. The break point in firmware versions is 13.x, if I stay below 13.x, no issues, but once I use anything 13.x, I see the issue. I left one module up, letting it loop... 00:00:10.532 WIF: Connect failed as AP cannot be reached I checked my DHCP server... restarted it, etc., so don't think that was a factor. So this may even be an SDK issue? I seem to recall a old thread here, about a similar problem where it was believed the SDK had a quirk or the retained wifi configuration was tripping things up... I just don't recall the thread # at the moment. For now, I can live with 12.x firmware which is stable on these older modules I have. When I can, I will test more. At this point this issue is more 'interesting' then 'frustrating' for me. :) I am tempted to pull out the Arduino IDE or MicroPython and see what happens. As always, thanks for the active support, greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
Better not discuss your troubles here, when you already have a thread about it, and it is off topic in this thread. |
Beta Was this translation helpful? Give feedback.
-
|
Oh... sorry, did not realize. |
Beta Was this translation helpful? Give feedback.
S2 is supported whatever the board and it's colour
You probably used a bad power supply when flashing the device