Cannot re- setup argon due to wifi IP address error

Troubleshooting
1

We unclaimed two xenons and one argon from a previously set up mesh network. When using the particle app to set up the argon again (in listening mode, then progresses to breathing white) we are only able to get past "connecting to the internet via Wi-Fi. Then, the set up fails during the “starting a secure session with the Particle device cloud” phase, and gives the error:

Error:
Your device failed to obtain an IP address. Please make sure your device has internet access.

This is strange because we have previously been able to set up mesh networks and boards on this same wifi (WPA2), and currently have a mesh running on a different account also using this same wifi.

Please advise,
thanks!

2

This means the Argon is running a non-AUTOMATIC system mode and the WiFi module is off hence no WiFi and consequently no cloud connection is possible.
Try Safe Mode or reflash Tinker.

4

When we try to do particle flash --usb tinker -v, this error occurs (this error did not happen in previous days)

o such file or directory: Could not open file undefined for reading
Error writing firmware: No such file or directory: Could not open file undefined for reading

VError: Error writing firmware: No such file or directory: Could not open file undefined for reading

at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\HDGcAdmin\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:212:13)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)

caused by: Error: No such file or directory: Could not open file undefined for reading

at ensureError (C:\Users\HDGcAdmin\AppData\Local\particle\node_modules\particle-cli\dist\lib\utilities.js:670:14)
at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\HDGcAdmin\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:212:24)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
5

Update:
I just found out that CLI v1.43.2 has broken the tinker update. You may need to download the tinker binaries from GitHub and flash that.


(a fix should be released today)

Try removing and reinstalling CLI via the most recent Windows Installer and make sure to tick the "uninstall old drivers" checkbox. Then when running CLI make sure not to do it from a system directory and that you have internet connection.
1 Like