FAQ

LoRaWAN_Payload_Codec_API_FAQ

Issue link: https://read.uberflip.com/i/1493503

Contents of this Issue

Navigation

Page 2 of 3

5177 Brandi n Court, Frem ont, CA94538 | Tel : +1 51 0 -4 9 2 -4044 | Fax : +1 510 -4 9 2 -4001 | www.l o ra -al l i anc e.org Payload Codec API FAQ 10. Is the codec to be delivered is only composed from two files: JavaScript code, and metadata? Yes, these are the only required compositions. However, there are optional and recommended data that can be provided besides the mandatory ones. Payload examples: To help the user / application to use the codec, the developer can provide a list of examples. These examples will be leveraged by LoRaWAN platforms to suggest some payloads to the user when testing it. Data Description: The codec developers are exposing the decoded "view" of LoRaWAN payloads in a JavaScript object which is by construction a JSON object. This object is completely open, but to ease the integration with LoRaWAN platforms, a description of its structure is recommended to be provided using a JSON Schema. 11. Is there a codec repository available at the alliance website? There are several public device repositories created by solution providers and some of them support already the LoRa Alliance codec API (Actility's GitHub Device Catalog, TTN GitHub Device Repository, etc.). However, there is no Lora Alliance public global codec repository, but the codec IDs will be defined like the vendor IDs currently. Then, the codec can be easily recognized. 12. The specification recommends using NPM and that would expose my decoder code to the public. What if I do not want to expose it? You can use NPM only for packaging and delivering the codec to the application server vendors that you choose, it is not mandatory to publish it on the public NPM repository. That way, your codec stays private. 13. Is there a standard for decoder output on the horizon? Example temperature is always "temperature", and unit is "Celsius". The concept of sensors/ontology was not defined in version 1 of the specification; however, the discussion is open in the LoRa Alliance technical committee, and this can be defined either in an updated version, or in a new dedicated specification.

Articles in this issue

Links on this page

view archives of FAQ - LoRaWAN_Payload_Codec_API_FAQ