Setting up 2 photons result in not connected to Particle Cloud

Troubleshooting
1

I am setting up a bunch (11) Photons today and I have two which will not complete the setup. They both get stuck at the point of connecting to the cloud, where the CLI keeps asking, “What would you like to do?” Check again, or change WiFi settings.

Steps taken
Connect Photon, put in listening mode
Run $ particle setup
Go through steps, setup WiFi details
The Photon restarts and connects to WiFi (blue cyan breathing)
Though it seems the Photon doesn’t connect to the Particle cloud. As it is stuck at:

 It doesn't look like your Photon has made it to the cloud yet.

? What would you like to do? (Use arrow keys)
❯ Check again to see if the Photon has connected
  Reconfigure the Wi-Fi settings of the Photon

I wrote tinker back on just in case
$ photon flash --usb tinker

I have tried updating the Photon:
Put in DTU mode, run $ Particle update

These are the only two of the 25 units I have setup which are doing this, so I will assume my network/firewall/etc. are good.

Any other ideas on why these units are not connecting?

Thank you!

Brett

2

This would suggest it in fact is connected to the cloud.
I'd not pay too much attention to the CLI message - it may just be a misinterpretation.
Or have you got any other symptoms that would explain the discrepancy between the device "thinking" it is connected (breathing cyan) an you not being able to confirm that?
It could be that the device is connected but just not claimed to your account - you can do that either via particle device add <deviceID> or via Web IDE.

In order to check whether your particle update worked as expected you can put the device in Listening Mode and post the output of particle serial inspect

1 Like
3

Thank you for the quick reply.

I honestly don’t know what I am looking for from the output of $ particle serial inspect. I don’t know which versions are which in those different modules

I used $ particle identify to get the device id (also noticed firmware is at 1.1.0)
I used that id in the command for $ particle device add <id>
This was successful and the device was added to my account!
This worked for both devices :slight_smile:

Thanks again for the assist!
Brett

4

That's why is said

It may provide a clue which theory to follow and which to dismiss :wink:

If you got 1.1.0 after particle update I'd suspect your CLI version isn't the most recent.

5

I guess I need to learn to read instructions closer. I glossed right over that part.

just in case still helpful:

Platform: 6 - Photon
Modules
  Bootloader module #0 - version 301, main location, 16384 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  System module #1 - version 1102, main location, 262144 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #2 - version 204
  System module #2 - version 1102, main location, 262144 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #1 - version 1102
      Bootloader module #0 - version 7
  User module #1 - version 3, main location, 131072 bytes max size
    UUID: B3A6DCD529BE70FBE24EE959C7305D58E3BC9A04ACDCE8F093C7A1F759097D09
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #2 - version 6
  User module #1 - version 5, factory location, 131072 bytes max size
    UUID: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #2 - version 23

cli version at 1.41.0, so yeah, a couple minor versions back (1.43.2)

6

Strange. So I updated my cli to latest version, 1.43.2, and now when I try to run $ particle flash --usb tinker I receive the following error:
Error writing firmware: dfu-util: Could not open file undefined for reading: No such file or directory

Brett

1 Like
7

Huh? This is the second time I hear this.
Maybe there was a regression between 1.43.1 and 1.43.2 - I’ll have to check.

Update:
Yup, that is a regression - I’ll make them aware.


(a fix should be released today)

Update: 1.43.3 is out and has fixed the issue

1 Like