Console.Particle.IO - unable to add devices manually on Growth Plan

Looks like the Particle Console has some sort of bug where I am unable to add devices manually. I think what is happening is it's blowing by the prompt "adding this device will add a new block of service to your Growth plan". The popup appears momentarily (maybe 500 ms tops) and the new device is never added. I suspect it's only an issue for either those on growth accounts and add a device count limit or maybe any limit where a new block is added.

Here's a short video of it. You have to play it really slow to catch the momentary popup and if I search for that serial number it doesn't appear in the list. It seems like it was cancelled automatically.

This isn't a big deal as I just use this page instead (honestly, it's even better functionality than what's on the console:

I mostly wanted to let the fine people at Particle.IO know so it can be fixed and the next person who faces this and doesn't know about the Import Devices tool won't be frustrated.

1 Like

Hi Jeff,

Is this happening on all browsers? Which OS are you using?
@support can take a look.

I did not try different web browsers although I should. Once I found the add devices in bulk tool and now that it accepts a QR code reader I just add devices that way now.

Once I get to my next batch I'll give it a try again from multiple browsers and post here the results.

1 Like

We're running into a similar issue where devices silently fail to be added. I'm not sure if this is the exact same issue or separate.

Symptoms:

  • Our main account cannot add devices when clicking the "Add Devices" button. It fails silently. On the other hand a different account can add devices -- tested using the same devices and the same products. I tried on both Firefox and Chrome, testing with a single device at a time.
  • On "Add Many Devices", uploading a list of 130 devices fails silently, but uploading a list of 99 devices and another list of 31 devices succeeds. I'm curious if there's a limit, and whether your other customers instead use APIs or perhaps the "import devices" cloud tool.

When I successfully add devices, the web page makes a POST to:
https://api.particle.io/v1/products/XXXXXXXXX/devices

When unsuccessful, either a user that can't add devices or a long list of devices, this POST does not occur.

Thanks! @Support

Hi @pingemi regarding the 131 device import operation, do you see any different results while using the standalone import devices tool?

Hi @ericpietrowicz

Hard to say because I've already imported the 131 devices and I'm seeing additional strange behavior from the "import devices tool". What I'm seeing:

  • Removed a single device X from the product
  • Put X into the "Import devices tool"
  • The "Import devices" tool shows the product as "added" but not "claimed" (not sure if that's relevant)
  • Pressed the "Import" button
  • Status line says "Done!"
  • Particle Console does not show this device in the list of devices for the product. Checked across two different users. Refreshed the web page.
  • One of those users can add the device to the product in the console and it will then show up in the device list.

I've done additional testing on the particle console and edited those into my first message.

Okay, this is odd... the DeviceID shown in the import list is different from the one I'm trying to add. This part is using Google Chrome. Before hitting the "add" button:

And after:

The DeviceID listed in "after", 0a...d4, is already in my product, and different from 0a...ac which is not. This appears to happen when the Device has been removed from the product. If the device is already in the product it shows up in the list correctly.

Could you DM me the actual device ID that you are trying to add? The box accepts Device ID, ICCID, or Serial Number and it may be detecting it as the wrong thing.

Fixed a bug in the Import devices tool where it would not import Wi-Fi devices that do not have an ICCID.

3 Likes

Hi @jgskarda we have deployed a bug fix to the issue you first encountered. Thanks for reporting it!

2 Likes