I’ve not previously used postman to query the meater API before, but after logging in and using the provided token I get the same response, regardless of block on/off cloud status. App works fine from mobile-only connection.
Trying to login with wrong credentials/token gives expected 401 on /login as well as /devices, so API seems connected.
Ok, so my meater probes are showing online when i power my block up, which is showing that firmware 188.8.131.52 is installed. The mobile app has been bugging me for months to upgrade my firmware, but of course thats always when i’m about to use it , so i have not actually upgraded. I wonder if its an issue with 3.x?
I’ve tried several scenarios and it seems to me that (on block with 184.108.40.206) the probes are only exposed to the public API once a cook is started.
So when starting a cook on 2 probes, only those 2 show up in the get devices(https://public-api.cloud.meater.com/v1/devices) and switch online after the API gets refreshed by openHAB.
I see the same behaviour on a parallel running HA-instance.
Stopping the cook also brings the probes offline after some time(funny thing is that the elapsed cook time keeps counting upwards after stopping the cook), when the block disconnects(automatic behaviour when no active cooks).
Now I’m not sure if this is consistent with previous behaviour and if this has changed over firmware versions(only started using the meater block last November).
Thanks, I now see the same behavior. When starting a cook, the probe appears. I’m pretty sure this behavior changed, otherwise I wouldn’t have been able to discover all my probes (without starting four cooks which I’m sure I didn’t). I have updated the issue I created with this information. Thanks all!