search

apption-labs / meater-cloud-public-rest-api

MEATER Cloud REST API documentation.
87 stars 4 forks source link

Order of probes in API request #19

Open tmjo opened 3 years ago

tmjo commented 3 years ago

Hi! Just bought a Meater Block and is looking into working with the API, thanks for providing it!

I was wondering if there is any logic to the order of returned devices? During testing, it seems random (what Block shows as probe 1 is returned as 4 giving me hope it was just reverse order, but probe 3 is returned as 3 and probe 4 is returned as 2.

Is there anything I am missing here? Could the Block order be figured out by using the IDs somehow, or would it be a good idea to return the devices in the same order as shown on the Block?

Again, thanks for providing an API - that's awesome!

tmjo commented 3 years ago

Hi again! Any input on this issue? Thanks.

nojacko commented 3 years ago

There's no defined order in the API.

The device IDs don't change so you could easily map them to the order you want. Alternatively, you could name your cooks and order them by cook names.

tmjo commented 3 years ago

Thanks for your reply and for the provided information.

Is it possible to give any information on how the Meater Block uses these device ids to call them probe 1-4? I believe it is important that what is shown on my Block display is identical to what I show in my software that uses the API.

nojacko commented 3 years ago

That's a good idea. I'll add it to the list. We're currently working a big update to the apps and cloud. I will try to get probe numbers added as part of this.

tmjo commented 3 years ago

Sounds great! Thanks.

brimmasch commented 3 years ago

Definitely interested in this. I would like to display the probes in the same order as the app. I think this is a common ask and it doesn't make sense to make the user have to define the order again if the data is coming from the API.

probize commented 2 years ago

I would really like to see the mapping of the ID and den number of the probes. When is the next update of the API expected?