BLE scanning not working on MR42 access points

Solved
AaronKennedy
Getting noticed

BLE scanning not working on MR42 access points

I have a network with a mix of wireless access points...

  • Cisco CW9162I
  • Cisco CW9164I
  • Meraki MR42

All devices are managed through the Meraki dashboard. In the dashboard (Wireless-->Configure-->IoT Radio Settings) BLE scanning is turned on, and on the individual page for every access point, it says that the "IoT radio assignment" is BLE. As an example, the image below is taken from the dashboard page for one of the MR42 access points.

Screenshot 2025-04-15 103633.png

The Cisco access points are able to detect BLE devices, and those devices show up in the dashboard at Wireless-->Monitor-->Bluetooth Clients and also show up on the Wireless-->Monitor-->Location Heatmap. However, none of the MR42 access points seem to be detecting BLE any devices.

 

Why are the MR42 access points not detecting BLE devices when everything indicates that those settings are on and enabled for those access points?

1 Accepted Solution
Jeremy_Meraki
Meraki Employee
Meraki Employee

Hi @AaronKennedy!

Knowing the issue is isolated to the MR42, I'm aware of a known issue that is related to Bluetooth client detection not working on this model.

 

I would recommend opening a case with Support for further review.

 

If this aligns with the known issue, Support can assist with enabling a setting on the MR42 APs to correct this behavior.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.

View solution in original post

3 Replies 3
alemabrahao
Kind of a big deal

Is the MR42 getting enough power?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Jeremy_Meraki
Meraki Employee
Meraki Employee

Hi @AaronKennedy!

Knowing the issue is isolated to the MR42, I'm aware of a known issue that is related to Bluetooth client detection not working on this model.

 

I would recommend opening a case with Support for further review.

 

If this aligns with the known issue, Support can assist with enabling a setting on the MR42 APs to correct this behavior.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
AaronKennedy
Getting noticed

Thanks.  I will open a support case and see if my situation corresponds with the known issue.

Get notified when there are additional replies to this discussion.