I was going to revive this other thread: Breathing Cyan but device doesn't show up/react [SOLVED] I had a similar experience but I guess I will start anew since that one is very old.
I bought a Spark Core back in 2013, tried to use it once but had some problems, put it aside and am trying again now.
I tried many things, probably close to two days of work now:
- tried to get it set up via an Android 5.1.1 phone (app doesn’t find the Core and I did check network parameters like channel number, 2.4GHz, SSID broadcast, WPA2, on local network with very strong signal from Netgear R7000 router and no other traffic) using the Spark Core app not the Particle one (I tried both)
- tried to set it up via USB from Mac OS El Capitan 10.11.3 (here I ran into npm installation issues on my Mac so couldn’t continue)
- tried to set it up via a Banana Pi (like Raspberry Pi) but again ran into either node or npm compatibility issues with the OS
- tried to set it up via an old iPad but that failed due to the iOS being < 7 and I couldn’t update it (Gen. 1 iPad)
- actually bought a copy of Parallels to try to set up via Linux in a VM. I had a Linux based off of downloading the .iso image and another VM installed automatically by Parallels. After significant problems (e.g. the Mac’s wireless is inaccessible from the VM, only a USB wifi dongle can be seen from the Linux virtual OS) I made some progress here.
One very perfidious, insidious thing was that sometimes after trying something the serial communication would silently get blocked. Like a command would work then sometime later, stop working. I had to restart the VM, cycle power on the Core and once I even had to restart the Mac to get the serial communication working again. This bug was extremely frustrating while testing combinations of parameters or commands to see what worked and what didn’t.
Anyway, “sudo particle setup” never worked. It would either block after asking to scan for wifi, or if it didn’t block sometimes it said no permission. If I told it not to scan and I entered SSID and password manually it would do something, the Core light stopped flashing blue and I think it might have done a restart but then the magenta LED came on solid, which I take to mean no network connection.
I also tried using “sudo particle identify” and “sudo particle serial wifi” to get the device ID, then I went to build.particle.io/ where I could do “Add” to claim the device. I’m not going to go into details here but this also did not work, as far as I could tell. It is listed in the Android App but I guess that’s just because I’m logged in to particle.io and it got the added device from there–it doesn’t mean the device is actually connected via wifi.
I realized part way through this in fact my router is acting like a firewall. I can see how that would prevent me from running the “Flash” command from the build.particle.io web page but I think most of the other problems I had are not related (flaky serial communication, android app not finding Core on local network, etc.).
Any ideas? My idea tank is running dry and my frustration tank overfloweth.
I’m looking at setting up port forwarding on my router; more frustration and time lost. I am for sure not turning off my network’s firewall functionality in order to use a Particle device. Re: port forwarding, can anyone suggest a way of getting the MAC address of a Core through the command line (as there is no wifi)?
(as a comical note: when I click “Create Topic” to post this–I get “503 Service Unavailable: Back-end server is at capacity”…fantastic)