Running the below in powershell returns my sensors, however, there are no values returned with the data, example return data shown below, note that it returns the sensors and has the headers for the parameters, but no values are included. If I run the history command, I get values returned. If I run the same query in the Meraki API documentation page for testing, it returns values as expected. $APIKey = "xxxxxxxxxxxxxxxxxxxxx" $orgid = "xxxxxx" $headers = @{ "Content-Type" = "application/json" "Accept" = "application/json" "X-Cisco-Meraki-API-Key" = $APIKey } [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12 -bor [Net.SecurityProtocolType]::Ssl3 $suri = "https://api.meraki.com/api/v1/organizations/$orgid/sensor/readings/latest" Invoke-RestMethod -Method Get -Uri $suri -Headers $Headers | fl  serial : xxxx-xxxx-xxxx network : @{id=xxxxxxxxxxxxx; name=xxxxxx} readings : {@{ts=2022-10-19T23:06:47Z; metric=battery; battery=}, @{ts=2022-10-19T23:06:47Z; metric=humidity; humidity=}, @{ts=2022-10-19T23:06:47Z; metric=temperature; temperature=}} serial : yyyy-yyyy-yyyy network : @{id=xxxxxxxxxxxxx; name=xxxxxx} readings : {@{ts=2022-10-19T23:05:51Z; metric=battery; battery=}, @{ts=2022-10-19T23:05:50Z; metric=water; water=}}   ... View more

Heads up, something changed in the MX security appliance Layer 7 categorization and traffic handling over the weekend of October 1st, 2022. We came in Monday, the 3rd to support tickets from ClientVPN users who could no longer RDP to their desktops, timeclocks that could no longer communicate with their cloud service providers, and an application that no longer functioned properly across the SDWAN. Timeclocks were being blocked as "Citrix Static" Layer 7, remote application was blocked as some form of Peer-2-Peer, and the RDP was blocked as RDP even though it had worked forever for client VPN prior to this weekend. Just be on the lookout if you have L7 applied. ... View more