Sounds good. Fingers crossed that QC can do it; if not, we still have a reasonable plan. Greg Michael Balzer wrote:
Greg,
this handling is based on the assumption we can have the QC set the initial pass phrase / module password.
It also protects a power user / developer against forgetting to configure a pass phrase after a full reflash of the module.
Normal users will update OTA / by SD card, so will not lose the pass phrase once set.
Let's see if QC can do that. If not, we can fallback to a default password instead.
Regards, Michael
Am 26.02.2018 um 01:46 schrieb Greg D.:
I understand the desire for security, but how does one set the password the first time? Instead, how about about using a default passkey if the module password is not set? That keeps the web interface closed to the casual passerby, but allows initial connection to those with the physical module's accompanying documentation.
We really ought to be making this easier to configure than the v2 module, where it one needed wrestle with SIM cards, accounts, and activation headaches in order use SMS messages. USB serial consoles are better, but they still aren't all that user friendly. We have a wonderful web interface; we should be able to use it out of the box.
Greg
Michael Balzer wrote:
The auto wifi ap mode does a fallback to "OVMS" with the module password if no AP network is configured. It does not start the AP mode if the password is empty. So in order to enable the AP mode for configuration, it's sufficient to set the module password and leave all auto configs to their defaults.
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev