Well That sucks !   After ringing support, just been told that MR32's are not compatible with Firmware R27 or above so we will not be able to use the Location and scanning API Version 3.   Even though the Meraki Dashboard upgraded the Firmware and said they were on R27.1, the technician said they were still actually just running R26   Weeks of work down the swanny ! ... View more

Hi All,   Meraki Support have enabled our Dashboard so that I can now get the V3 (Beta) on the Bluetooth option,  So I have now selected this but I am now not getting any JSON files from the API at all.  I also noticed that there is now the option for Bluetooth clients on the Location Heatmap,  not sure if its linked but this is not showing any Bluetooth clients either ?   Is there anything else I need to do to get the V3 Beta working for Bluetooth.  I have validated the location API etc on the settings and everything is ok,  but its showing o the settings as Status Grey: Host has not been validated or sent any Scanning API requests.   Kind Regards   Ken ... View more

Hi Dexter,   SunGod did point me in the write direction in that I have many APs seeing the iTags,  sometimes up to 5 APs seeing on Tag, ALL with different X,Y Values,  so I have no idea which one to take,  unless I just take the one with the strongest RSSI Value.   I currently have Case : 05279068 open with yourselves,  because as shown above,  I am running Firmware R27.1 on all APs,  but on the General Settings in Network Wide for the Location and Scanning,  when I select Bluetooth,  I only get the dropdown options for V1 or V2.  If I select WiFi,  I get, V1,V2 and V3 (Beta).  So are you able to explain why I am not getting V3 (beta) as an option for Bluetooth ?       Is it available for Bluetooth ?,  the reason I ask is your web link on the Location and Scanning API specifically refers to V3 (beta) only for Wifi,  it does not mention BLE ?   https://developer.cisco.com/meraki/scanning-api/#!api-version-3-beta/wi-fi-location-api-v3   Kind Regards   Ken ... View more

Hi BrechtSchamp,   I'm not misinterpreting the X,Y values,  I fully understand they are from the Bottom Left of the Floorplan,  I was just asking the question in case they were not.  I am picking up the X,Y values from the AP 11 JSON file from the Location API and it positions the Tag next to AP 11,  when its actually sitting directly under AP 13 which is what is confusing me...   Kind Regards   Ken ... View more

Hi SunGod,   So I'm confused now,  sorry for my lack of knowledge,  but how do I know which JSON File to read from the location Scanning API to get the X,Y offset,  my theory was I look at which AP the tag was last seen on to get the X,Y offset,  but this positions the tag next to AP 11 and not AP 13 ?   Will the Tag appear in many of the JSON Files,  because we get a JSON file for each AP and if so,  how do I know which to choose in order to get the correct X,Y ?   Kind Regards   Ken ... View more

Hey SunGod,   Ok so we took the Tags downstairs to do a test as our APs are more in triangles to test this and we were completely confused to the result.  The Cross on the image is where the Tag was actually located,  probably 2 metres away from AP 13 with no obstruction,  however,  in the Meraki Dashboard under Bluetooth Clients,  it constantly showed every minute that the tag was last seen by AP 11 which was over 30 metres away through several glass walls.  Would you know how this was possible,  and why it was not being seen by AP 13 but yet other devices were using AP 13 without issue ?     ... View more

Hi,   Thanks for the swift response,  the Floorplan is accurate from CAD and the APs are positioned accurately,  I cannot see any walls between where the BLE tags are and the AP,  below is from the location heatmap but the Red Cross shows where my app is positioning the BL Tags and where they actually should be in the circle.  I was expecting it to be a little more accurate than this ?     ... View more

Ok, Hi All,   So we have updated to Firmware 27.1 and we still do not get the V3 (Beta) on the dropdown when we select Bluetooth on the Location and Scanning POST URLs section,  still only available for WiFi.   All our APs which are MR32's  now say firmware is 27.1   But I am still not getting the Bluetooth Low Energy iTags coming through in the JSON from the location API.   Kind Regards   Ken ... View more

Brilliant !   Thanks,  I can see it there now to upgrade.  I will just check with our IT Infrastructure its ok to proceed and will let you know.   Thanks SunGod. ... View more

Hi sungod,   I've not installed the R27.1 on the APs because when I go to the AP and scroll down to Firmware, its says the below and does not give me any option to update;  so I don't know how to get the R27.1 Firmware ?     ... View more

Hi sungod,   Yes I have Allow Beta's ticked in the dashboard,  and yes when I chcked Firmwares Beta I can see R27.1 has been available since May 2020,  however when I go to the Post URL settings page,  I still only get the option for V1 or V2 for Bluetooth,  if I select WiFi I can see the V3 (Beta),  but its BLE I need in V3 to get the Bluetooth LE tags.         Kind Regards   Ken ... View more

Hi Philip,   We cannot set the iTags signal,  they're basic tags,  but I can see them on the Meraki Dashboard and they are emitting signals very often ;     I can only select the V2 API on the location API setting on the dashboard,  and the JSON I am getting is only sending the BCM20732A devices...     ... View more

Hi All,   Thanks for the help,  ok,  here's where I'm at.  I setup Python and got everything running and validated and I am saving the JSON out to a file,  however,  it does not seem complete ?  If I go to the Meraki Dashboard and I can see I have 3 BLE iTags which are showing connected to a specific AP.     When I get the JSON from the location PI,  its showing other Bluetooth Clients but not the iTags ?   I think this is because we do not have the firmware R27 but I have signed up for the Developer Programme but not had any response,  anybody know how I can get the R27 firmware otherwise months of work and approvals to get this to where it is will have been wasted ?   Kind Regards   Ken ... View more

Cheers Philip,   Our IT Dept have set the server up, so it just a server which is public facing, all it has on it is IIS,  so I need to install / setup anything else on there in order to receive the data from the location API,  But I have no idea what I am supposed to setup.  Do I need to write a Web Service in orer to receive the Location PI Data ? ... View more

Brilliant,   Thanks John. ... View more

Hi Chris,   Thanks for your response.  I did state at the bottom of my post that I was replacing the NetworkID and the ClientID with the actual IDs.   The problem is,  you DO get the status when you are requesting the Network Clients using ; https://api.meraki.com/api/v0/organizations/{organizationId}/networks    however,  you DO NOT get the status when requesting the Bluetooth Clients https://api.meraki.com/api/v0/networks/{networkId}/bluetoothClients    Is this an oversight on Meraki as it is displayed when you use the actual dashboard web pages at https://n35.meraki.com/     Kind Regards   Ken ... View more

Brilliant, thank you ! ... View more