You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two weeks ago successfully migrated several Shelly Plus 1PM and Shelly Plus RGBW PM modules to Tasmota without any problem.
Last weekend (feeling confident about the process) I tried the same with two Shelly Plus Plug S devices (V2 specifically). After performing the safeboot migration the device was not accessible through the web interface anymore, even though it was still connected over wifi.
I left this for about 15 minutes. After rebooting the device by unplugging it, I could access the web interface again. It turned out to be booted in safe mode. It was not possible to get out of this. I tried updating the device, restarting, resetting flash, nothing helped. It seemed to be the same issue as: arendst/Tasmota#19414
If it was one time and I would not have converted any other devices, I would think it would be a random mistake, but it happened for two devices in a row. Is there anyone who has any suggestions on what could have caused this or how to prevent/resolve it?
The text was updated successfully, but these errors were encountered:
Two weeks ago successfully migrated several Shelly Plus 1PM and Shelly Plus RGBW PM modules to Tasmota without any problem.
Last weekend (feeling confident about the process) I tried the same with two Shelly Plus Plug S devices (V2 specifically). After performing the safeboot migration the device was not accessible through the web interface anymore, even though it was still connected over wifi.
I left this for about 15 minutes. After rebooting the device by unplugging it, I could access the web interface again. It turned out to be booted in safe mode. It was not possible to get out of this. I tried updating the device, restarting, resetting flash, nothing helped. It seemed to be the same issue as: arendst/Tasmota#19414
If it was one time and I would not have converted any other devices, I would think it would be a random mistake, but it happened for two devices in a row. Is there anyone who has any suggestions on what could have caused this or how to prevent/resolve it?
The text was updated successfully, but these errors were encountered: