I've noticed in my polling of the probes, that their status doesn't clear when they go offline.
The last status of the probes is given back to us as a response on each request.
I figured, if they were off/offline, the devices array would then be empty, which would indicate that a probe, or multiple probes are offline, or without power.
For example, when I was first building with the API, it took a bit of time for data to trickle in between polls and I would see a response like
Which makes sense, I was patient and the data then began to flow in.
Later on, I wanted account for when these devices power down. I expected the data above to show eventually, but the data maintained the last status of my probes
I've noticed in my polling of the probes, that their status doesn't clear when they go offline.
The last status of the probes is given back to us as a response on each request.
I figured, if they were off/offline, the devices array would then be empty, which would indicate that a probe, or multiple probes are offline, or without power.
For example, when I was first building with the API, it took a bit of time for data to trickle in between polls and I would see a response like
{ status: 'OK', statusCode: 200, data: { devices: [] }, meta: {} }
Which makes sense, I was patient and the data then began to flow in.
Later on, I wanted account for when these devices power down. I expected the data above to show eventually, but the data maintained the last status of my probes
Does the meater cloud eventually purge this status data? Or does the last status maintain itself until the probes come back online again?