I have question regarding particle projects and Cloud Key.
After the manufacturing of the custom pcb, we are currently loading the bootloader to a newer version and I was wondering if we need to do load generate new cloud key?
i have noticed with my prototypes, if i ever need to flash bootloader again i sometimes need to run the cloud keys code in CLI to make it connect to the cloud.
Do i need to run this on production products to avoid cloud keys problem for my customers?
I am using Photons and have a number of Products - each has a product bearer security key (Cloud key?).
In production the first thing we do is load the correct version (for the released application) of system part 1 and 2 and bootloader - the device claim is done and the application loaded. Thereafter, the product devices are updated from the product console. Have not had any keys issues for a long time now i.e. post 0.6.4.
We have gone down the route of having a single user account (actually can be claimed by anyone on the team who is authorised) - the device is tested a couple of times before shipping but is connected to a production area WiFi. The device is then set up on a web control app that is used by both production and end users (different access control) and thus end users never need claim devices. If your model is to sell a product and allow the end user to claim the device then you could claim, test and un claim before shipping.
Thanks for the reply, I think I want to use the intended method by particle (which i believe is end users have their own claims) . Not sure what to do now, maybe Particle can have some input here.
I would dispute end-users claiming being the Particle preferred approach. It is one of a number approaches that critically maintains greater control over the devices and data and avoids your customer needing to have a Particle account!