Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add API endpoint to determine most likely location of client #41

Closed
DatanoiseTV opened this issue Mar 26, 2018 · 4 comments
Closed

Add API endpoint to determine most likely location of client #41

DatanoiseTV opened this issue Mar 26, 2018 · 4 comments
Labels
enhancement New feature or request

Comments

@DatanoiseTV
Copy link

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.

@schollz
Copy link
Owner

schollz commented Mar 26, 2018

Yeah, I agree that's a useful endpoint. I will add that.

@schollz schollz added the enhancement New feature or request label Mar 26, 2018
@DatanoiseTV
Copy link
Author

@schollz Another useful response in the endpoint would be the time in seconds when the client was last seen at that location.

schollz added a commit that referenced this issue Mar 27, 2018
@schollz
Copy link
Owner

schollz commented Mar 27, 2018

Ok @DatanoiseTV, added in f2e6c94!

Try it here: https://cloud.internalpositioning.com/api/v1/location_basic/testdb/zack2@gmail.com

Let me know if that works!

I think it won't work on ESPs (I think), but FIND also supports some MQTT endpoints for more efficient transfers (just fyi!)

@DatanoiseTV
Copy link
Author

It works just as intended.

@schollz schollz closed this as completed Mar 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants