- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sensor data models misalignment for downStream power (latest/history)
Hi Meraki devs.
There are two different models for "downstreamPower", depending on whether you call latest or history endpoints. Please could this be fixed?
Latest returns:
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @david_n_m_bond , we're rolling a fix out for this. Notifying here since its a breaking change and I can post what to expect. Both latest and historical will send the response in the following format:
{ "ts": "2023-05-03T19:59:14Z", "metric": "remoteLockoutSwitch", "remoteLockoutSwitch": { "locked": false } }, { "ts": "2023-05-03T19:59:14Z", "metric": "downstreamPower", "downstreamPower": { "enabled": true } }
Note that for historical data, there will be extra info about the SN and Network ID in each objects.
This will be rolled out in a few days.
Let me know if you have any questions.
Thanks,
Konark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @david_n_m_bond,
Thanks for posting in our Community forum.
Which API endpoint are you calling for each of these queries?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The "latest" and "history" endpoints, as documented here:
- https://developer.cisco.com/meraki/api-latest/get-organization-sensor-readings-history/
- https://developer.cisco.com/meraki/api-latest/get-organization-sensor-readings-latest/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @david_n_m_bond ,
It looks like each API call should return [mostly] the same information, just that Latest returns a separate array for the actual metrics. If you're getting inconsistent readings for each, I'd open a support case to have this behavior validated and for our back-end team to address it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for raising this @david_n_m_bond . This looks like a bug and if you'd like you can raise a support ticket to have it documented and prioritized.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @david_n_m_bond , we're rolling a fix out for this. Notifying here since its a breaking change and I can post what to expect. Both latest and historical will send the response in the following format:
{ "ts": "2023-05-03T19:59:14Z", "metric": "remoteLockoutSwitch", "remoteLockoutSwitch": { "locked": false } }, { "ts": "2023-05-03T19:59:14Z", "metric": "downstreamPower", "downstreamPower": { "enabled": true } }
Note that for historical data, there will be extra info about the SN and Network ID in each objects.
This will be rolled out in a few days.
Let me know if you have any questions.
Thanks,
Konark
