Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX bug: make it clearer that "send config" should happen after flashing firmware #125

Open
d33tah opened this issue Mar 2, 2022 · 0 comments

Comments

@d33tah
Copy link

d33tah commented Mar 2, 2022

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:

  1. after flashing, a reminder to send config now,
  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant