I saw an older thread with the same issue in 2020 saying this was fixed, but I am still unable to do a PUT call to update a device’s location info despite getting a 200 OK code returned.
Here is the call I am making:
/rest/o/{{org_id}}/g/{{group_id}}/d/{{device_id}}/loc
passing the following data:
{
“data”: {
“location_list”: [
{
“timestamp”: 0,
“la”: 0.0,
“lo”: 0.0,
“at”: 0.0,
“sp”: 0.0
}
]
}
}
Is anyone else having similar issues where this call doesn’t actually update the device location in IC2? I have tried removing all location info in IC2 as well and then making my call.
This API call is for injecting (batches of) external GPS location data for the device. The general use-case is for installations where users already have location data available from a navigation system or other device, and do not want (or cannot) add a dedicated GPS antenna.
The injected data should show up on the map as location point(s) for the attached timestamps. If manually testing an API bridge between devices, please avoid injecting historical (or invalid) timestamps, as the UI won’t give you visibility outside the selected range.
At the moment there isn’t a public API available to update a device static location.
I see, thank you for the clarification. Are there any plans in the future for an API call that would be able to inject devices with static location information? For reference, my organization would like an automated way to force the device to take the end shipping address as what is shown on the UI map without needing to manually enter it during our configuration phase.
There really should be an API endpoint to update the device location. With the push for B One and B One 5G for retail failover, it’s extremely painful to update them one-by-one when you have more than a few.
Hi Noah, Christopher,
Would the following feature suit your purposes?
It can be found just below both the organization and group level device lists as “Update device info by CSV file”
(For group level, click ‘edit’. For org level, make sure you’re in ‘devices’ mode)
We’ll take a look at making a public version of the api, but this is current available in production.
2 Likes
