-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Description
Is your feature request related to a problem? Please describe.
We switched ESP modules and therefore restored all configs from the old controller. A OTA Update password was set on the old module, so the ota.lock key was set to true in the config. When restoring the config, the lock is set but seemingly no option to turn it off again afterwards (did not think of any default password as I tried to update at a later point the first time and just noted down the last set password). But didn't notice right away, as the device was on 0.15.0 and only when 0.15.1 came out, tried to unlock it again but with no luck.
Did a complete factory reset / restore three times, before noticing, that the lock is set via the cfg and changed it manually in the json to false. Probably could have used wledota in the first place, if I've noticed the restore using the default password on OTA lock.
Somehow more a heads up to myself and other users, but might be helpful to have some advisory like a notice, that there is a default password, that might be used. We switched the devices so flawlessly with backup/restore and the config seemed to be all correct, so didn't think of setting or rather changing the OTA password to the password stored in Keepass and used on the previous device.
Describe the solution you'd like
A simple javascript alert() will probably be sufficient, to notify the users, that the default passwords will be used, if not previously set otherwise. Maybe check if the locks were set upon upload client sided?