New Particle Diagnostics - Mixed Results

All,

I really like the idea of Particle diagnostics so I went ahead and upgraded a Photon to 0.8.0-rc4. I am now getting diagnostic information on the product console but, when I click on the “diagnostics” link, it gets stuck at 50%.


I can refresh the page after a few minutes and the Photon seems to be running fine (not locked up). Any ideas?

Information: Mac, High Sierra, Safari

Thanks,

Chip

Sorry, to reply to my own post but, I also updated an electron to 0.8.0-rc4 OVER THE AIR from 0.7.0-rc7 and it worked! Not only that but, the diagnostics worked as well.

This is a great combination of features - over the air firmware upgrades and remote diagnostics. Great job Particle!.

Thanks,

Chip

P.S. - Still would like some help on the Photon though…

2 Likes

I’m getting the same thing, I’ll watch your post for answers before starting a new one.

I hit the Run Diagnostics for a Photon I have running in Threaded mode.

The actual main loop had locked up before I tried to call the Run Diagnostics via hitting the button but the thread running the communication was still working just fine and allowed the Run Diagnostics query to work quickly.

If your Photon was running a function and you were not running threaded then maybe that was the reason for the query hanging at 50%.

Just a guess. I have no idea really :smile:

But I do agree it’s a nice new feature :spark:

2 Likes

I have noticed a couple other minor issues with the Device Health feature. These are likely just bugs that need to be fixed and I am only pointing them out here so the right folks see them - still love this feature!

  1. WiFi Signal Strength Dialog says to move to a place with stronger Cellular signal:
    29%20AM
    Also, should the dialog also mention the fact that blocking in my code could be causing this especially since Wi-Fi signal is “Fair”?

  2. Cellular Signal Strength includes a variable “{describes}” that is not getting populated.
    52%20AM

Thanks,

Chip

4 Likes

@chipmc good you are finding these things before I get to it (on the road for a couple of weeks). Perhaps these should be opened as issues on github if you have the time.

Edit: nevermind. Thinking now, the cloud side isn’t on github.

Thanks @chipmc, we’d previously logged that second issues you reported, but I’ve not seen the first before. I’ll pass this along to the team, thanks for reporting!

4 Likes