Early Access API - Roaming

[Ajay-Chandrasekaran]

Hi, I tried running the below API call however in the output i see some weird RSSI values. Can someone confirm me why do i see this '0' values ?

API call -https://api.meraki.com/api/v1/organizations/{{orgId}}/wireless/roaming/byNetwork/byInterval?networkIds[]=XXX&timespan=3600

Output -

{
"origin": {
"name": "XX-MR-09",
"serial": "Q4AE-DCWY-NN3P",
"mac": "68:49:92:32:72:b0"
},
"destination": {
"name": "XX-MR-11",
"serial": "Q4AE-67UZ-8X2B",
"mac": "68:49:92:32:6c:60"
},
"ssid": {
"name": "WiFiXXX",
"number": 2
},
"client": {
"id": "kd24161",
"mac": "10:5f:ad:f1:ee:0b"
},
"band": {
"before": 6,
"after": 6
},
"protocol": "802.11r-roam",
"duration": 70,
"rssi": {
"before": 0,
"after": 44
}

[aleabrahao]

A value of 0 does not mean 0 dBm, it simply means Meraki had no usable data for that moment.

[Ajay-Chandrasekaran]

So how do I interpret such data? if it is a good or bad roam? because I see lots of clients with same '0' value.

[aleabrahao]

I think that to evaluate roaming quality, you can use the following criteria:

duration: <150 ms = good
rssi.after: >35 (-65 dBm) = good

[Ajay-Chandrasekaran]

But if it is after then it means client has already roamed right. so, I think it is good to monitor both before & after.

[aleabrahao]

I understand that Meraki defines it as 0 when the AP does not have a valid measurement, which in this case is common and normal in fast roaming.
So I think the correct way would be to use "after" protocol and duration to assess roaming quality.

[Raphael_L]

That doesn't look normal. Are you using a recent firmware version ? I would reach out to support , early access API often have bugs

[Ajay-Chandrasekaran]

Yes, APs are running on 31.1.8 Firmware and APIs was taken from the Meraki Documentation.

[Ajay-Chandrasekaran]

Just let me know once you have an update.