Closed nekomona closed 1 year ago
btw is it necessary for it to be blocking? I have no idea if you can just print it when you get the scan data
I've tried the non-blocking one during the first commit, but it always returns as failed. There should be somewhere buggy but can't locate them. The blocking scan will timeout server connection but reconnects once finished, and it won't break WiFi connection. Since we only need to scan during provisioning, imo the blocking one would be enough.
This PR add
GET WIFISCAN
command to initiate a blocking scan, retrieving what hotspot could be seen by the trackers during provisioning. Could avoid connecting to a 5G hotspot, misspelling, and might help future fancy provisioning.The result would be printed in the format below:
In addition, since
CmdParser
couldn't deal with double quotes in SSID / Password, a base64 version for serial provisioning is added (SET BWIFI <B64SSID> <B64PASS>
). Everything is the same except encoded in base64 to avoid double quote in the command.Currently blocked by #256