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
Hi! Thanks for creating tasmotizer! I'd like to report a UX bug.
Yesterday I was flashing Tasmota on ESP01 with my friend and we couldn't get it to work - it wouldn't connect to our wifi. After ruling out faulty hardware, we spent some time experimenting and found it by chance that we were supposed to flash the device first, THEN send config. From the hindsight it's obvious, but I still think it's a UX bug that could be easily fixed by adding two messages:
after flashing, a reminder to send config now,
after sending config, maybe a reminder along the lines of "reflashing will wipe the configs"?
Our logic was that "send config" would somehow memorize the configs and write then during the flashing. Since more than one of us made that mistake, I think it's a relatively one to make and probably an easy one to avoid via UX improvements.
The text was updated successfully, but these errors were encountered:
Hi! Thanks for creating tasmotizer! I'd like to report a UX bug.
Yesterday I was flashing Tasmota on ESP01 with my friend and we couldn't get it to work - it wouldn't connect to our wifi. After ruling out faulty hardware, we spent some time experimenting and found it by chance that we were supposed to flash the device first, THEN send config. From the hindsight it's obvious, but I still think it's a UX bug that could be easily fixed by adding two messages:
Our logic was that "send config" would somehow memorize the configs and write then during the flashing. Since more than one of us made that mistake, I think it's a relatively one to make and probably an easy one to avoid via UX improvements.
The text was updated successfully, but these errors were encountered: