Goal: implement LwM2M protocol in Asset Tracker and show how to do it.
Why: To make implementation of LwM2M easier for customers
How: Using Coiote from AV System, which is a LwM2M server, to send data from a device to a cloud provided already used by Asset Tracker.
| Name | -- | -- | -- | -- | -- | -- |
|---|---|---|---|---|---|---|
| Device Connection | ---> | |||||
| Device Simulator | ---> | |||||
| Coiote Result Transformation | ---> | |||||
| Asset Tracker Connection | ---> | |||||
| End-to-end test | ---> | |||||
| Documentation | ---> |
- Goal: send data from Thingy:91 to a cloud provider through an integration with Coiote
- How: Connect the Thingy:91 with nRF Asset Tracker firmware to Coiote and then, implement integration between Coiote and available cloud providers.
- Link: Connection: Thingy:91 -> Coiote -> Cloud provider
- Goal: Send and upate data from a simulate device to Coiote
- How: Uses LwM2M protocol to connect to Coiote
- Link: LwM2M Device Simulator
- Goal: Take the result from the cloud integration and transform it from Coiote format to Asset Tracker format
- How: Check types and build Asset Tracker expected input object
- Link: Result Transformation
- Goal: Connect the cloud instance with Asset Tracker web application
- How: Implement the transformation process of last step in the cloud provider, this way the data is already transformed before send it to Asset Tracker
- Batch update feature is not supported by LwM2M Asset Tracker. +info
- Roam timestamp is not supported by LwM2M. +info
- Server timestamp is used in case an expected timestamp is missing: + info