-
Notifications
You must be signed in to change notification settings - Fork 72
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
Settings are not saved #127
Comments
Try format filesystem by browse to If it doesn't work, check your system status by click the "BM" on the web page. You might also check the file on file system by browsing to There might be something wrong with the flash, but I don't know what. |
Followed this link, asked for a username and password. After entering, it shows: "FileNotFound"
Also doesn't show any files |
Tried flashing through BrewFlasher - BrewPiLess, everything worked, connected my access point, after rebooting it did not disappear. It works. The file system size is not zero either. So either I'm flashing Brewmaniac somehow wrong or something else. I flashed through NodeMcu PyFlasher, put the option wipes all data. I also tried flashing through NodeMcu flasher. |
Help me, I bought another type of board - a new board wemos d1 mini. I uploaded firmware.bin through NodeMCU Pyflasher (attached screenshot), everything flashed. I go to 192.168.4.1, click on BM and again I see File System Size = 0. I tried to change the value in automation - it says that it is impossible to save. |
I have the following problem - no settings made via menu or web-interface are saved. I define sensors, set what and where to use, after that everything works and shows, but when I turn off the controller again goes to the initial screen, sensors are absent, my wi-fi point is also absent. I have to do it all over again.
I tried the following versions 0.5.1, 0.5.2, 0.5.3. My network finds, connects, ip is assigned - everything works, but as soon as you turn off - everything forgets.
Also noticed that after connecting to my access point, the network bm continues to be visible in the list of access points and you can connect to it.
I also failed to save the mashing settings via web-interface - it wrote failed to save.
The text was updated successfully, but these errors were encountered: