wifi ssid and password change end in a not reachable device

[no-Legend]

Hi,

at the moment i want to switch all my tasmota devices into an seperated smarthome network.
There for i setted up my unifi device with special ssid and also a vlan.
The switch and aps are work like the should.

The problem:
I logged in the webinterface and changed there the ssid and the password
After saving the device is rebooting and not reachable anymore.
The ssid and password is correct.
I'm not sure but i think the problem is coming from my wifi password.
Because there is a ";" letter at the end and tasmota is using this letter as a seperator for the console commands.

But and here is the strange behavior, if im going to change the password of the wifimanger there is no problem.
This workaround is only useable my esp8266 devices. (Gosund and NOUS A1T)
If you run the command "WifiConfig 2" on a esp32 device (here it is a esp32c3 athom PG 01V3 EU) the captive portal isn't showing up.
The captiveprotal is not coming up, also if you are entering the 192.168.4.1 to reache the portal the wifimanager is not showing.

Question:
Did i do anything wrong?
I know my wifi password is not optimal with ";" at the end but the letter is allowed according to the norm.

Cheers Robert

[adamsthws]

This is a late reply but for anyone else who might this discover this thread, I hope it helps...

- Edit -
Tasmota's docs ask for passwords without special characters, so using this method to sneak a semicolon into a WiFi password is experimental and unsupported
- /Edit -

The Wi-Fi page saves all its fields as one Backlog, and Backlog takes a ; as the end of a command. A password like abc; is saved as abc, and anything after the ; runs as a command of its own. The WifiManager page saves the password directly, which is why it worked there. The same happens with a ; in the web admin or MQTT password. A fix is up for review in #25184.

The WifiManager not appearing after WifiConfig 2 on your ESP32-C3 is a second bug, fixed in #25183.

Until they're released, sending the commands one at a time from the console should work, since a single command keeps the ;:

Ssid1 <your SSID>
Password1 <your password>

- Edit -
As sfromis points out below, each of these commands restarts the device, so instead put the new network in the second slot (so you don't lock yourself out):

Ssid2 <new SSID>
Password2 <new password>

After the first, it can't join the new network yet and falls back to the one it's on. After the second, it joins the new network, or falls back again if the details are wrong.
- /Edit -

[sfromis]

Using semicolon in a password is not simply "not optimal", but against the requirements. Whatever you might be able to do the "sneak" this through would still be experimental and unsupported.

Note that separate commands Ssid1 and Password1 will result in Tasmota rebooting after one of the commands, unless you're really quick, meaning access trouble unless combinations are valid too.

[adamsthws]

Thanks for noticing this, I've edited with the correction. Well spotted!

[BenkhiraAhmedBaderEddine1]

Hi Robert,

I don't think you're necessarily doing anything wrong. According to the Tasmota documentation, WifiConfig 2 should start the Wi-Fi Manager, with its web interface available at http://192.168.4.1 for approximately 3 minutes.

The semicolon may be worth investigating, but I wouldn't assume it's the only cause. Tasmota's documentation does advise avoiding special characters and spaces in Wi-Fi passwords, even if those characters are valid under Wi-Fi standards.

A few things I'd check:

• Try opening http://192.168.4.1 explicitly, rather than relying on iOS's automatic captive-portal detection.
• Confirm that you're connected to the ESP32-C3's Tasmota access point and that your phone hasn't switched back to another network.
• Check whether the same behavior occurs with another browser or a different client device.
• If possible, test with a temporary Wi-Fi password that contains only letters and numbers. This could help determine whether the semicolon is involved.
• If the problem persists, share the exact Tasmota build information and any serial or console logs available when WifiConfig 2 is executed.

Since you can reach the standard device landing page at 192.168.4.1 but not the Wi-Fi Manager, that behavior is worth investigating separately from the password issue. It would be useful to determine whether this is an ESP32-C3-specific issue, a firmware issue, or a captive-portal/browser interaction.

I hope this helps narrow it down!