Photon not working: (frustration) options?

I ordered a particle photon because I was fed up of micro-controllers that just don’t work or are DOA. After many 1.99$ plus free shipping china devices, I finally decided to go with something I expected was quality controlled. So I paid 19$ + 17$ of transport for a photon because I thought that I would receive something that will be working of the shelf.

My code is ready, my controls and sensors are ready, I was just missing the photon to finally plug everything together.

I received my photon this week, use the photon app on my Phone and… it failed to verify product ownership. No matter if I install dfu utils, reflash the device with latest firmware, try to correct the bad public key (hitting a Invalid DFU suffix signature error message following a 2015 thread - we are in 2017 and I still have this issue!), I still can’t use my photon.

I try to see if, contrary to what the error message is saying, the photon registered somehow to, and when going to, I get the “We’re sorry, but something went wrong.” error message in my browser. Try the console and get the “Bummer! That’s not the page you’re looking for”.

Trying to contact for help, I am sent to this community forum or FAQs instead of real human support from particle.

Must I say how frustrated I am?

I feel that the entire IoT everybody is talking about is just an utopia and we are still struggling with very basic problems.

Maybe I did something wrong or I am missing something, so I am ready to let go of my frustrations and I am open to suggestions on how to move forward. I just want to control a few activators and get inputs of a few sensors. What are my options since I can’t have my photon working?

Thanks for you help, you have no idea how much it is appreciated!

Ping @rickkas7

What colour is the Photon flashing?

Also, did you managed to claim the Photon yet?

Hey there @eboily – when did you submit your customer support inquiry at I don’t see a ticket logged with the email associated with your community account. If you’d send me your ticket number, I’ll follow up internally to make sure you get a response.

What is the link your getting a 404 error with on the Particle website? I want to make sure you have the right link and correct the link in documentation if you’re being directed to the wrong place.


Thanks for your interest in my issues.

I’ll start with the web issues.

Step 1. I go to ""
The main particle page is displayed in my browser.

Step 2. I click on log in (top right)
I get the following errors in the javascript console

SSO will redirect to
bundle.js? [sm]:42713 The provided value ‘ms-stream’ is not a valid enum value of type XMLHttpRequestResponseType.
bundle.js? [sm]:42713 The provided value ‘moz-chunked-arraybuffer’ is not a valid enum value of type XMLHttpRequestResponseType.
VM636:1 Uncaught ReferenceError: $ is not defined
at :1:1
at gtm.js?id=GTM-P2CPMH&l=dataLayer:75
at Object.Xh (gtm.js?id=GTM-P2CPMH&l=dataLayer:77)
at wf (gtm.js?id=GTM-P2CPMH&l=dataLayer:46)
at yk.D (gtm.js?id=GTM-P2CPMH&l=dataLayer:118)
at Ik (gtm.js?id=GTM-P2CPMH&l=dataLayer:114)
at Vk (gtm.js?id=GTM-P2CPMH&l=dataLayer:118)
at dg (gtm.js?id=GTM-P2CPMH&l=dataLayer:119)
at ng (gtm.js?id=GTM-P2CPMH&l=dataLayer:57)
at og (gtm.js?id=GTM-P2CPMH&l=dataLayer:57)

but I have the login page displayed.

Step 3. I enter my credentials and click on the log in button
I am presented with the main page ( with my email address top right. So far so good.

Step 4. Top right, I click on « IDE »
The Javascript console displays an error:

GET 500 (Internal Server Error)

and I get a page saying "We’re sorry, but something went wrong. »

Step 5. I go back to the main particle page,

Step 6. I click on « CONSOLE »
I get the following errors in the javascript console:

vendor-f415f61….js:22 The provided value ‘ms-stream’ is not a valid enum value of type XMLHttpRequestResponseType.t
vendor-f415f61….js:22 The provided value ‘moz-chunked-arraybuffer’ is not a valid enum value of type XMLHttpRequestResponseType.t
pconsole-3cbc70a….js:7 TypeError: Cannot read property ‘getRecord’ of null
at vendor-f415f61….js:68
raven.js:703 POST 429 (TOO MANY REQUESTS)

and a page is displayed saying

“Bummer! That’s not the page you’re looking for
But as long as you’re here - would you rather fight a shark with bear arms or a bear with sharks for arms?”

This is my reproductible experience using two different browsers (Safari Version 10.1 (12603. and Chrome Version 58.0.3029.110 (64-bit)) on 2 different networks (home and work).

I’ll stop here since I am at work and I don’t have the photon with me. I’ll try to answer by best on the photon issue with lights colors etc another time.

Thanks for your help, it is much appreciated.

  • Ed

BTY, is it possible that I have two accounts with same username but 2 different passwords?

  • When I log in with my username and password 1, I get logged in but I have the above errors.

  • When I log in with the same username bit with password 2, I still get logged in but this time I can go to the console and ide without problems.

It looks like it is SSO related…


That doesn’t sound possible to have two same username with different password.

Also, the error in the javascript console can be ignored.

What happens when you visit
You can try using that to setup your Photon and see how things go…

I’ll try the setup page tonight.

However, two accepted passwords with same username is what I observe.
I log in with password 1, get logged in but get errors on console and ide.
I log in with password 2, get logged in and console and ide work fine.

I’ll also try the second password with the phone setup app tonight…


1 Like

Thanks for reporting this issues – I’m going to have someone from our engineering team look into it. It seems like their might be some weirdness happening with your cookies. If you clear cookies and log in with password 1, what happens?

I cleared the cookies, same behaviour.

However, All the other issues were related to this SSO problem.
Using the second password, I got my photon registered, pushed code from the IDE, the console sees it, everything is fine now. Case closed.

Thanks for your help!