I am not sure why this is happening but spark core is connecting automatically to two different networks without me having to provide it with SSID and password again. Its like the core is saving the WiFi credentials of the two different networks and connecting automatically.
Do you have any idea whats going on with the spark?
Do you know whether weāll be able to āhard-linkā our Sparks to specific wifi networks in a future firmware? E.g. I only want it to work in 1 or 2 places and not let anyone else add extra networks.
So I guess this is 2 questions: will we be able to lock our Sparks to a small number of networks, and will we be able to lock our Sparks so nobody can take them and re-flash them out of our control?
Thereās no way additional Profiles can be added without them putting it in Listening mode. So you can configure the 2 Wifi profile beforehand and give it to them.
You can modify the bootloader or firmware to prevent OTA or Listening mode but that doesnāt stop them from flashing over DFU
I have an issue on fresh firmware with connecting to Wifi. Older firmware worked fine on same board. Is firmware reset resets ALL wifi profiles or something additional is needed?
Both. Iāve replaced factory reset firmware so it would work with spark.cli
Spark.cli is not checking if core asks for security code therefore is not working with older cores.
Sequence:
0. Pre-condition: old reset firmware
Flash something from WEB ide: WiFi setup & connection works after that
Flash āspark flash ā¦ cc3000ā: WiFi setup & connection works after that
Factory reset: : WiFi setup & connection works after that
Flash new factory reset firmware: : WiFi setup works, connection DOES NOT WORK
Flash any new user firmware: WiFi setup works, connection DOES NOT WORK
Flash cc3000 patch with dfu, run firmware reset: WiFi setup works, connection DOES NOT WORK
Flash back reset firmware backup and reset: WiFi setup & connection works after that
I think what youāre seeing there might be the cc3000 patch corrupting the saved wifi profilesā¦ The factory reset causes those profiles to be erased, so they should work when you re-load the firmware. The ānobuttonsā branch, and the deep_update versions should either clear, or backup/restore the profiles after finishing the patch.
Iāll also add a bug to the spark-cli for that configuring wifi issue on older firmware:
I have recently used WiFi.setCredentials() and WiFi.clearCredentials() to great effect with over the air upgrade of WiFi credentials. My Spark Cores are being field trialled on a 6m mounting post 50m from the access point with a Cantenna. To save āgoing up the poleā - quite literally - it has allowed me to change Wifi profiles to test out the best access point. To prevent unauthorised change of profiles I have included a password facility.