search

TheThingsIndustries / lorawan-stack-docs

Documentation for The Things Stack
Apache License 2.0
32 stars 65 forks source link

Improve Device Claiming documentation. #606

Closed ymgupta closed 3 years ago

ymgupta commented 3 years ago

Summary

Why do we need this ?

This helps users to decide where to use the Device Claiming.

What is already there? What do you see now?

Device claiming documentation. Ref: https://www.thethingsindustries.com/docs/devices/device-claiming/ CLI command to configure claiming using the CLI (the claim authentication code). But it returned an error while executing it. Ref: https://www.thethingsindustries.com/docs/devices/device-claiming/make-device-claimable/#claiming-settings

What is missing? What do you want to see?

  1. Add a section mentioning the device claiming possibilities in a tabular format. Ref: https://www.thethingsindustries.com/docs/devices/device-claiming/
  2. Updating the CLI command with the correct command. 
    $ ttn-lw-cli end-device set <app-id> <device-id> --claim-authentication-code.value ABCD \
--claim-authentication-code.valid-from 2021-03-01T00:00:00Z \
--claim-authentication-code.valid-from 2021-03-31T23:59:59Z

    How do you propose to document this?

    ...

    Can you do this yourself and submit a Pull Request?

    No.

nejraselimovic commented 3 years ago

Add a section mentioning where device claiming can be used to transfer devices.

I.e., within a TTSC tenant or between two TTSC tenants is possible. TTSC to TTS CE is not possible. Etc.

@KrishnaIyer I see that docs on device claiming have "Cloud and Enterprise only" tag. I guess since TTS Enterprise is a multi-tenant environment, it goes the same as @ymgupta wrote for TTS Cloud (from one app to another in one tenant, and from one tenant to another)? What about transferring between TTS Cloud and TTS Enterprise?

KrishnaIyer commented 3 years ago

What about transferring between TTS Cloud and TTS Enterprise?

This is not possible currently. Device claiming only works in if the entities are in the same IS.