[solved] Photon setup failure - new LED flashing sequence

Troubleshooting
1

I’ve setup several Photons, but I’m having trouble today for some reason. After trying to set it up to our WiFi, the Photon quickly blinks cyan and then a very rapid (burst?) of red and then repeats the same pattern. Although I try to put it into setup mode to join it to WiFi (it seems to work part way), it always reverts to this pattern. I received 3 new Photons today and two of them are doing the very same thing.

Advice?

2

This might help:
https://docs.particle.io/support/troubleshooting/common-issues/photon/#blinking-cyan
And so might this:
https://docs.particle.io/support/troubleshooting/key-management/photon/

The issue you’re describing sounds like a keys issue (cyan with blinking orange). Give that a try and let us know if that worked for you.

3

This is getting frustrating…the first time for me with the Photon. All 3 Photons received today are doing the same thing. I have been working between two different Particle accounts. Could this be contributing to my problems in some fashion?

4

No luck with any of the devices. I feel like I’m missing something, although I also feel as though I’ve gone through the commands carefully

[Toms-MacBook-Pro:~/Documents/Particle/Key files] tom% particle serial identify
Your device id is 1a002d001547353236343033
Your system firmware version is 0.4.9
[Toms-MacBook-Pro:~/Documents/Particle/Key files] tom% particle keys doctor 1a002d001547353236343033
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running openssl genrsa -out 1a002d001547353236343033_rsa_new.pem 1024
running openssl rsa -in 1a002d001547353236343033_rsa_new.pem -pubout -out 1a002d001547353236343033_rsa_new.pub.pem
running openssl rsa -in 1a002d001547353236343033_rsa_new.pem -outform DER -out 1a002d001547353236343033_rsa_new.der
New Key Created!
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -d 2b04:d006 -a 1 -s 34:612 -U backup_rsa_1a002d001547353236343033_rsa_new.der
running openssl rsa -in backup_rsa_1a002d001547353236343033_rsa_new.der -inform DER -pubout -out backup_rsa_1a002d001547353236343033_rsa_new.pub.pem
Saved!
checking file 1a002d001547353236343033_rsa_new.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 34:leave -D 1a002d001547353236343033_rsa_new.der
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "DCT Flash   "
Downloading to address = 0x00000022, size = 610
Download	[=========================] 100%          610 bytes
Download done.
File downloaded successfully
Saved!
running openssl rsa -inform PEM -in 1a002d001547353236343033_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/ll/8dqw1v348xj49k001s7__1tr0000gn/T/116320-3395-hjz5e4.pub.pem
running openssl rsa -pubin -inform PEM -in 1a002d001547353236343033_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/ll/8dqw1v348xj49k001s7__1tr0000gn/T/116320-3395-hjz5e4.pub.pem
attempting to add a new public key for device 1a002d001547353236343033
Error sending public key to server: Permission Denied
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - undefined
[Toms-MacBook-Pro:~/Documents/Particle/Key files] tom%
5

Seriously…3 “bad” Photons all arrived in the same package today? It really seems like something else is wrong.

I believe I’ve gone through both of the steps outlined above, but without any success. I really don’t know if the device(s) should be considered “claimed” or not. They don’t show up under “particle list”, so that makes me think they were never successfully claimed.

Regardless, none of the steps have made a difference. Some additional guidance would be greatly appreciated. You guys have spoiled me!

6

A video of the LED sequence might help diagnose the problem.

Also double check that your photon has connectivity to the internet, specifically port 5683.

7

I had another Photon connected while all this is going on and I’ve never had an issue with all the other Photons I’ve setup here (or anywhere). I just recorded a 10 sec video, but it’s way too large. I’m going to try and downsize it and send it later. Thanks for chiming in!

8

Out of interest, could you tell me the version of system firmware on the problem photons? Determining the version of system firmware on a Photon/P1

In the initial factory run there was a key generation bug that would affect a small percentage of photons which was fixed in 0.4.8 - if this is that same bug, you certainly were unlucky to be bitten 3 times! :anguished: But please bear with us - it’s not a permanent problem and we can get you up and running with these 3 units.

9

I already flashed 0.4.9 to one of the devices without benefit. What’s the easiest way to get a 10MB video to you?

10

Let’s give this a try: https://youtu.be/INEgKRxdxA0

11

By the way, to answer your question about firmware version, here’s the output:

[Toms-MacBook-Pro:~] tom% particle serial identify

Your device id is 1a002d001547353236343033
Your system firmware version is 0.4.9
[Toms-MacBook-Pro:~] tom%
12

By the way, I noticed once again, the following line in the output from running commands such as "particle keys doctor "

Error sending public key to server: Permission Denied
13

For the permissions, could you try logging out/in again, might help(?)

14

When I run particle keys doctor, I get the following files:

1a002d001547353236343033_rsa_new.der
1a002d001547353236343033_rsa_new.pem
1a002d001547353236343033_rsa_new.pub.pem
backup_rsa_1a002d001547353236343033_rsa_new.der
backup_rsa_1a002d001547353236343033_rsa_new.pub.pem

When I run particle keys send, do I include the “_rsa” portion that’s not included in the online docs?

Yes, I’ll logout and back in and try again.

15

With regard to logging out, I always use the default for

Would you like to revoke the current authentication token? (y/N)

Is that the smart thing to do (especially when switching between Particle accounts)? Truthfully, I don’t understand this question.

16

After logging out and back in:

[Toms-MacBook-Pro:~/Documents/Particle/Key files] tom% particle keys send 1a002d001547353236343033 1a002d001547353236343033_rsa_new.pub.pem
running openssl rsa -inform PEM -in 1a002d001547353236343033_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/ll/8dqw1v348xj49k001s7__1tr0000gn/T/116321-868-wv5940.pub.pem
running openssl rsa -pubin -inform PEM -in 1a002d001547353236343033_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/ll/8dqw1v348xj49k001s7__1tr0000gn/T/116321-868-wv5940.pub.pem
attempting to add a new public key for device 1a002d001547353236343033
Error sending public key to server: Permission Denied
[Toms-MacBook-Pro:~/Documents/Particle/Key files] tom%
17

By the way, here’s the output from the “s” command:

{"p":6,"m":[{"s":16384,"l":"m","vc":30,"vv":30,"f":"b","n":"0","v":7,"d":[]},{"s":262144,"l":"m","vc":30,"vv":0,"d":[]},{"s":262144,"l":"m","vc":30,"vv":30,"f":"s","n":"2","v":11,"d":[{"f":"s","n":"1","v":11,"_":""}]},{"s":131072,"l":"m","vc":30,"vv":30,"u":"1951A0526A772E54ADD0CA2EA1D1644761C8EBFD35BDE7B7E363F68B9C248C34","f":"u","n":"1","v":3,"d":[{"f":"s","n":"2","v":11,"_":""}]},{"s":131072,"l":"f","vc":30,"vv":30,"u":"1951A0526A772E54ADD0CA2EA1D1644761C8EBFD35BDE7B7E363F68B9C248C34","f":"u","n":"1","v":3,"d":[{"f":"s","n":"2","v":11,"_":""}]}]}
18

FWIW, I re-checked all 3 devices and they’re all running 0.4.9. I had re-flashed one of them yesterday thinking it might help, but with no benefit.

Gosh, this is really getting frustrating. I have to believe it has something to do with my account.

19

Can you place the device in DFU mode and do particle keys server and see if it helps?

There’s nothing to do with the account. All these are between the cloud and device so no account related stuff are involved.

I guess the device has yet to be claimed, right?

20

OK. Did that. What next? The LED pattern has not changed.

[Toms-MacBook-Pro:~] tom% particle keys server
running dfu-util -l
Found DFU device 2b04:d006
checking file /usr/local/lib/node_modules/particle-cli/keys/rsa.pub.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 2082 -D /usr/local/lib/node_modules/particle-cli/keys/rsa.pub.der
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "DCT Flash   "
Downloading to address = 0x00000822, size = 512
Download	[=========================] 100%          512 bytes
Download done.
File downloaded successfully
Okay!  New keys in place, your device will not restart.
[Toms-MacBook-Pro:~] tom%