This is under embargo until October the 14th. Do not click on this link until then. If you do click on it - don't read any content.
Meraki trusts you.
I clicked, I read, I want to order some.
Ok, sadly this solution is not usable for 80% of my customers in the next probably three to five years:
Most of them have MR42/MR52 and will not relplace them anytime soon.
Is that with or without a PO 😁
@cmr compare a MR32 to an MR56 - both state they have "2.4 GHz Bluetooth Low Energy (BLE) radio with beacon and BLE scanning support". The MT devices show they use "802.15.1 (Bluetooth 4.2 Low Energy BLE)". So...if it is purely a marketing decision to get people to upgrade to the WiFi6 units, that's not so cool. We have APs in all of our server rooms and most IDFs, but we aren't putting WiFi 6 units in there as it isn't necessary - and won't be for quite some time.
@BHC_RESORTS I think the earlier APs may have Bluetooth 4.0 but I'm not 100%. I agree it does seem a shame that the WiFi5 APs aren't supported 😕
@cmr You're likely right with the BT version, but as it isn't defined anywhere in the documentation that I can find, that would be something good to mention so folks don't think it is an arbitrary requirement.
According to the FCC documents, it looks like the controller is a N52840, which is a Bluetooth 5 ready radio. So perhaps it is Bluetooth 5 only.
The MT devices use the Cisco Trust Anchor - maybe that’s how they securely, automatically connect to the MR or MV. I’m guessing that the MRx5/x6 and the MVx2 have the Cisco Trust Anchor built in too...
It's official now! Here's the announcement: https://meraki.cisco.com/blog/2020/10/simplifying-sensors-with-cisco-meraki/
Here's the new MT forum (who will be the first non-Merakian to post there?): https://community.meraki.com/t5/Sensors/bd-p/sensors