cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4178
Views
3
Helpful
5
Replies

Sensor data models misalignment for downStream power (latest/history)

david.bond
Level 4
Level 4

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:

{
"ts": "2023-07-09T15:01:26Z",
"metric": "downstreamPower",
"downstreamPower": {
"override": "disabled",
"state": "enabled"
}
},
History returns:
"downstreamPower": {
"locked": false,
"enabled": true
}
Personally, I prefer the "history" version, as I believe these to be boolean CIs.
Author, https://www.nuget.org/packages/Meraki.Api/
1 Accepted Solution

Accepted Solutions

konjain
Cisco Employee
Cisco Employee

Hey @david.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

View solution in original post

5 Replies 5

bryona
Cisco Employee
Cisco Employee

Hi @david.bond,

Thanks for posting in our Community forum.

Which API endpoint are you calling for each of these queries?

Hi @david.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.


John-on-API
Cisco Employee
Cisco Employee

Thanks for raising this @david.bond . This looks like a bug and if you'd like you can raise a support ticket to have it documented and prioritized.

konjain
Cisco Employee
Cisco Employee

Hey @david.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