In this article:
When considering mobility, Myriota-enabled devices will generally fall into one of the following three categories:
- No movement is expected during the lifetime of deployment
- At minimum, a single GPS position update is required at the point of installation, noting that the Myriota Module will perform more frequent background GPS fixes to maintain accurate time
- Devices may be returned to base prior to end-of-life. It is expected that they will be recommissioned to reset their state prior to redeployment
- Device of this type are attached to a moving asset, and are expected to be largely non-stationary for the lifetime of the deployment
It is expected that a mobile device will manage its own GPS behaviour, to allow a higher frequency of readings in accordance with the required position update rate
- Devices are expected to be deployed to a single location for an extended period, but may be relocated one or more times during the lifetime of the deployment
It is expected that a relocatable device will manage its own GPS behaviour, to allow GPS fixes to occur as needed
The Myriota SDK provides specific functionality to support the latter category of "relocatable devices".
Device Relocation Support
In the case of relocatable devices, there is a unique need to be able to “reset” the module between deployments. This is necessary to enable a fresh start in the new location and prevent the occurrence of cross-over messaging, where user data from the old location remains in the queue and is transmitted from the new location.
You can achieve this by triggering the following APIs once the device is redeployed to its new location:
- Clear all scheduled messages using
- Clear all scheduled tasks using
- Reacquire a GPS fix for an updated position at the new location
At this point, the device can recommence the generation and scheduling of messages.