Skip to content

Commit 1e753f3

Browse files
authored
Merge pull request #1151 from particle-iot/feature/clarify-product-claiming
Clarify that product devices do not need to be online for claiming
2 parents e51836d + 3f72c3a commit 1e753f3

File tree

3 files changed

+2
-10
lines changed

3 files changed

+2
-10
lines changed

src/assets/images/AutoclaimFlow.png

-45.6 KB
Binary file not shown.

src/content/datasheets/certifications/antenna.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ Full certification of a device typically involves three different certifications
132132

133133
3. [PTCRB](https://www.ptcrb.com/). This is a certification for cellular devices in the United States. If you use a similar antenna to the one Particle used during its tests, you may be able to avoid having to perform this certification again.
134134

135-
In the United States [this document from the FCC](https://apps.fcc.gov/kdb/GetAttachment.html?id=zVUUifMY6Doa%2BO3Sg0Nygw%3D%3D&desc=996369%20D04%20Module%20Integration%20Guide%20V01&tracking_number=44637) provides a great deal of information about the various certifications. The process is similar in Canada (IC). In the European Union you will need to have a test lab perform similar tests, but there isn't the equivalent of an FCC or IC identification number for the EU.
135+
In the United States [this document from the FCC](https://apps.fcc.gov/kdb/GetAttachment.html?id=bNCiEdkFEKnHsZF9GHCNdg%3D%3D&desc=996369%20D04%20Module%20Integration%20Guide%20V02&tracking_number=44637) provides a great deal of information about the various certifications. The process is similar in Canada (IC). In the European Union you will need to have a test lab perform similar tests, but there isn't the equivalent of an FCC or IC identification number for the EU.
136136

137137
In order to avoid having to complete steps 2 and 3 again, a substitute antenna must:
138138

src/content/tutorials/product-tools/introduction.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -103,18 +103,10 @@ Note that the device cloud charges begin when the devices comes online the first
103103

104104
In addition to being part of the product, devices typically need to be **claimed** to an account. For cellular products, it is common to create a single account that all devices are claimed to. It's also possible to use [two-legged shadow customers](/tutorials/device-cloud/authentication/#two-legged-authentication), for both cellular and Wi-Fi devices.
105105

106-
Claiming can only be done when the device is online (breathing cyan).
107-
108-
This can be done using the [Particle Cloud API](/reference/device-cloud/api/#claim-a-device) after bringing the device online.
106+
A product device can be claimed to any team member of a product using the [Particle Cloud API](/reference/device-cloud/api/#claim-a-device) after the device has been imported to the product. It does not need to be online for claiming.
109107

110108
![Pre-claim Flow](/assets/images/PreclaimFlow.png)
111109

112-
If you have your own server monitoring product events, you can do this from your server automatically when the device comes online the first time, allowing you to defer billing until the customer first turns on the device and allows it to connect to the cloud.
113-
114-
If you do not have your own server infrastructure, it's possible to auto-claim a device with a [little bit of device firmware and two webhooks](https://github.com/rickkas7/DeviceClaimRK), as well.
115-
116-
![Auto-claim Flow](/assets/images/AutoclaimFlow.png)
117-
118110
If you never need to send an event to your product's devices, it's possible to leave them unclaimed.
119111

120112
For Wi-Fi devices, you will typically need to use a mobile app and the [Photon/P1 Setup Library](/reference/SDKs/ios/) to set the Wi-Fi credentials, and this provides a convenient way to claim devices at the same time.

0 commit comments

Comments
 (0)