Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About ChrisHykin
ChrisHykin
Here to help
Member since Feb 27, 2018
Aug 23 2022
Community Record
9
Posts
1
Kudos
0
Solutions
Badges
Jan 10 2019
2:01 PM
Yes it is. It's for obtaining floor plans autonomously, however this approach requires a user to view source of a page it's not really a 'hidden Api'... hence my question.
... View more
Jan 10 2019
7:51 AM
Hi, Is there any known way of determining the Node Group identifier for a given network via the API? This is the ID stored as Mkiconf.ng_id in the source of each page... Thanks, Chris
... View more
Labels:
- Labels:
-
Dashboard API
-
Scanning API
Jan 10 2019
4:07 AM
Sorry, I meant to add the following: There is an endpoint which states the rotation, and flex points. However it requires a user to login and obtain. https://nXYZ.meraki.com/node_groups/$id/floorplans Again, without heavy automation, you're somewhat at the behest of a user obtaining this themselves and working it through from there - but it's perhaps better than nothing.
... View more
Jan 10 2019
2:26 AM
Yes, if you build a mechanism for the alignment of a building / floorplan against a set geography of latitude and longitude. However you're then asking the user to do this once in additional software/add-on, and once in Dashboard. As a result there is room for error where there doesn't really need to be. However the Scanning API provides x and y co-ordinates, and the list of floorplans upon which it's seen/present. There is no way to link the Meraki (already geographically aligned floorplan) with these co-ordinates, or (at worst case facilitate upload) without either the pixel-scale of the floorplan supplied, or the a mechanism for obtaining the specific location of the floorplan.
... View more
Jan 9 2019
10:58 AM
Webfrank - you're grappling with the same problem I am. The Scanning API provides (for each client) a list of floorplans upon which it's appeared, and the x and y offset (in meters!) for the location. However, there doesn't appear to be any method provided for connecting the Meraki floorplans with this information, at all. It's most strange.
... View more
Jun 27 2018
6:02 AM
Hi Colin, Thank you very much for taking the time to respond to me. I think this is perhaps an area where the API could be improved. What i'm trying to achieve is an automated mechanism by which (essentially) I can obtain all the required information via the Dashboard API for a user to set up an account on my system, and then subsequently start listening from the Scanning API and interpretting the data. Importing the AP Mac addresses for a given network to x-reference against the Scanning API is easy, but in both your answers I'm unable to find an automated method of import for a 3rd party for the floorplans. (I have to know more than I'm able to find out via dashboard). I've filled out the 'make a wish' for this. Hopfully it's something you guys may consdier adding. Thanks very much again Colin
... View more
Jun 26 2018
1:32 AM
Hi, I have a couple of questions about the location/scanning API and the dashboard API. The scanning API will, upon detection of a client, issue the geolocation in lat/lng alongside floorplans upon which the device is seen ('apFloors') and the x and y co-ordinates of the device as part of the POST to a provided reciever. However, there doesn't seem to be a mechanism via the API to obtain a copy of the floorplans to cross-reference this against, nor are any units supplied for the X and Y values. I feel like I'm missing something that joins this together, but at the moment I can't see the value of the X/Y variables, yet I'd love to be able to map these devices on to a floorplan. What I'd like to be able to do: - Use the API and associated API key for Dashboard to make a call to retrieve the floorplans in use on dashboard (Base64?). These would then be provided and returned with a 'scale' that correlates with the X/Y co-ordinates issued by Scanning API. - Then I can tie the whole lot together.... Any help would be gratefully appreciated, and if I've missed something or some key piece of documentation, my apologies in advance, Chris Hykin
... View more
Labels:
- Labels:
-
Dashboard API
-
Scanning API
Feb 27 2018
6:03 AM
Hi, The API can deliver an array of the 'point in time' detections as you've quite rightly highlighted. From that there is typically a job to do to sort through these individual detections and work out those which are in the middle of a visit.. When we've done this previously we've maintained an intermediary SQL based database and some logic in the receiver script/program, broadly outlined as follows: For each recorded detection: "have I seen this Mac address in the last 3 minutes?" - if yes, update the last_seen on a visit entry. - if no, create a new visit and add the information. We've found this is the best way of cleanly doing it. This then allows you the ability to hold a table full of 'visits' which can be analysed separately to 'detections'. Hope that helps, Chris
... View more
© 2024 Cisco Systems, Inc.
