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

Solved
david_n_m_bond
Building a reputation

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:

 

            {
                "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
KonJain
Meraki Employee
Meraki Employee

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

View solution in original post

5 Replies 5
bryona
Meraki Employee
Meraki Employee

Hi @david_n_m_bond,

 

Thanks for posting in our Community forum.

 

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

david_n_m_bond
Building a reputation

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.


John-K
Meraki Employee
Meraki Employee

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.

KonJain
Meraki Employee
Meraki Employee

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

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.