Open nanometrenat opened 7 years ago
Initial investigation suggests that the "servald keyring list" command fails to return anything useful when generating the SSID.
Immediate idea is to have the shell script responsible check for blank keyring list output, and if so, wait a few seconds before retrying.
Sighted again today - a device that had previously been reliably issuing a good SSID then randomly threw a dodgy one. Worked again on reboot.
The wifi SSID is in the format MeshExtender-xxxxxxxxxxxx Prior to this week the SSID bore no relation to the device ID (shown on the "hello I'm..." screen at http://192.168.3.1:4110/) and changed each time the device firmware was flashed.
This week a code fix was made this week to always set the SSID to include the device ID.
HOWEVER this does not always load up correctly - we have had three devices so far that have given themselves an SSID of "MeshExtender-" with no second half. This is an intermittent fault - seems to come back fine when the device is flashed again (or in at least one case it came back fine after only a reboot).
Please investigate how this intermittent fault is occurring. Thanks