Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • What is Claiming?
  • What is this for?
  • Set Pincode
  • Activate Claiming
  • Claim Code
  • Claim a Device
  • Security
  • Auto-Deactivation
  • Pin code override
  • Privacy Protection

Was this helpful?

  1. Device

Claiming

Last updated 2 years ago

Was this helpful?

What is Claiming?

You can share your Datacake devices with others using a pin code and serial number without having to invite those persons.These persons only need to register for use on the Datacake Cloud.

If you give the pin code and serial number to these persons, they can "claim" the device by entering both into their workspace.

Pincode claiming is only available for paid devices!

What is this for?

With the help of pin code and serial numbers, devices can be delivered anonymously. The end user can insert the devices you have purchased into his workspace by entering the pin code and serial number. You do not need to know in advance who the person actually is. This is ideal for:

  • Selling or renting products without knowing who the end user will be.

  • Providing the functions of a device.

  • Sharing devices.

  • Involving dealers.

Set Pincode

Open the configuration of your device that you want to share via the claiming.

Under "General Configuration" at the end of the panel you will find the options for claiming. Just scroll down the page a little and you'll find the following options:

Activate Claiming

Activate the checkbox "Device can be claimed by other Workspace" to enable the claiming function for the current device.

The checkbox is checked by default, but the pin code is not set. But don't worry: As long as the pincode is not set, the device cannot be claimed by another user, even if he knows the serial number.

Claim Code

In this text field (marked green) you can enter any pin code. It can consist of numbers, letters or both.

Claim a Device

To understand how claiming works, we will also show you how to insert a device into a workspace using the combination of pin code and serial number.

First of all navigate to your fleet view (Fleet / All Devices) via the sidebar (marked red in the following screenshot).

Now add a new device. To do so, please click on the button "Add Device". Now the following modal will appear:

Select "Pincode claiming" from the collection of available device types. You can also recognize this by the QR Code symbol.

Please enter the serial number and the pin code in the corresponding text fields. To add the device, confirm your entry with either "Add Device" or "Add Device and configure" (the latter will take you directly to the configuration of the device).

If the pin code and serial number have been entered correctly, the claiming was successful. The device is now available in your workspace.

Security

Auto-Deactivation

Once a device has been claimed by a user into another workspace using the claiming function, that function is automatically deactivated. I

If the device is then to be claimed again, the function must be reactivated as described above.

Pin code override

The pin code option is also available to your end customers. This means that the person who added one of your devices to his workspace via claiming can also reactivate the claiming and assign a different pin code.

This pin code is bound to the device itself. This means that you can also see the changed pin code of the end user.

Privacy Protection

For reasons of data protection, there is currently no possibility for you to find out in which workspaces and by which user the respective device was claimed.

So make sure at all times that you make the pin code and serial number available only to selected persons.

Selling Products

If you use the claiming in your sales activities and you sell the products anonymously, you usually do not know who the end customer will be.

If you still want to provide proactive support, then have your customers invite you to their workspace. In this way, your customers will have explicitly agreed to the access and are on the safe side as far as data protection is concerned.