I seem to be having trouble with the particle-cli again.
I’ve had head banging sessions in the past but for the last year or so its been fine. I have it installed on my windows 7 laptop, and after my last problems I discovered that I had multiple over installations which appead to be the casse of my problems. So I uninstalled it both using the installer and the command line prompt. Installed it via the windows installer and everything seem stable.
Then a few weeks ago, I was using the command line to set up a core, which it had been succesfull at doing when I was prompted that a new version of the cli was available and to update it with npm -g particle-cli upgrade, for something very similar, OK I thought and gave it a go. Which was a mistake becasue then, when ever I ran it it would complain that it needed node 4.4. So I upgraded node to 8 (something) and then the CLI just started messing me around all over again. So I uninstalled the CLI, with the installer, only to find particle still present on the command line, did a command line uninstall and once I thought I had rid of it, reinstalled it with the installer. Everything seemed to go fine, I could run particle without a prompt to undate.
But now I am trying to set up a 1st gen core.
I can use particle setup, to set up the wifi, and strangely it is not asking for the security type, just the SSID and password. It can been seen on the console devices screen going on and offline. its breathing blue, it reacts to the rainbow command. I can not flash to it.
I have tried using particle doctor, but it fails after updating cc3000 firmware, applying update, then doctor didn’t complete sucesfully. this.promptDfd is not a function.
my current particle version is 1.28.2 and Node version 8,10.0