You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though we can currently determine the last known location of a client by sending a request to GET /api/v1/location/FAMILY/DEVICE, it would be useful to have a simplified API endpoint e.g. GET /api/v1/location_min/FAMILY/DEVICE which just returns the name and probability of the most probable last location. This would save a lot of memory on embedded devices by avoiding unnecessary JSON parsing.
The text was updated successfully, but these errors were encountered:
Even though we can currently determine the last known location of a client by sending a request to
GET /api/v1/location/FAMILY/DEVICE
, it would be useful to have a simplified API endpoint e.g.GET /api/v1/location_min/FAMILY/DEVICE
which just returns the name and probability of the most probable last location. This would save a lot of memory on embedded devices by avoiding unnecessary JSON parsing.The text was updated successfully, but these errors were encountered: