How are you performing the timestamp conversion?   When I convert 1548864847, I get Wednesday, January 30, 2019 11:14:07 AM GMT-05:00 ... View more

I am not seeing this issue.   I do have 2-factor authentication enabled for my account. ... View more

Make sure the Dashboard API is enabled for your organization.  Go to Meraki Dashboard > Organization > Settings.  Look for the "API Access" setting. ... View more

You've probably already found this document.  Make sure you start here: https://meraki.cisco.com/lib/pdf/meraki_whitepaper_captive_portal.pdf   Look at the "EXCAP Overview - Sign-on Splash" section, which is pretty close to your use case.   You can use the Walled Garden settings on your SSID to allow the user to interact with your site (to login and use their credits) while not providing access to everything else.   You will need a back-end application to serve the captive portal pages, handle login, do the points exchange, terminate the session when the time limit is reached, and confirm authentication via RADIUS. ... View more

In cases like this, your only option is to make a lot of separate API calls.  To avoid the API request limit, you can use a rate limiter.  For example, I sometimes use the throttled-request package with Node.js.   Remember that the rate limit applies at the organization level.  If you have any other integrations or tasks using the API, you need to consider the total usage.   Using the first two letters of the model to determine the device type seems good enough for now. ... View more

Try this:   - Network-Wide > General - Traffic analysis > Custom Pie Chart > Add a Slice     ... View more

When you add a license, you have the option of applying the license as additional devices or as a renewal.  It looks like you added three of your licenses as renewals.  As a result, you extended the expiration date of your one device rather than adding more devices to your network.   You get a brief period when you can "undo" your license addition, which will let you correct the operation.  That's why your screenshot has a circular arrow next to one of the licenses.  If you don't have the "undo" option, you're going to have to contact Meraki support. ... View more

I use customized FreeRADIUS servers to handle authentication for Meraki in many locations.   If you haven't already tried, I suggest running FreeRADIUS in debug mode ( radiusd -X ) and attempting to connect to your SSID.  You will have to look through the FreeRADIUS output, but it should provide an indication of the root cause.   Are you using Meraki's RADIUS proxy?   Have you configured FreeRADIUS to accept connections from all possible IP addresses that can originate the RADIUS requests?  The IP ranges will be different if you use Meraki's RADIUS proxy.   If you aren't using Meraki's RADIUS proxy, have you checked firewall configurations between your access points and your RADIUS server? ... View more

I'm not using Microsoft Teams, so I don't have a good way to test that end of the integration.   However, I did a quick test yesterday with ngrok and a simple Node.js receiver.  It took a little longer than I expected for the notifications to start arriving, but it did eventually work.  I wasn't keeping close track, but I would guess that it was 10 or 15 minutes.   I set my webhook to receive configuration change notifications only.  I didn't add it to the top-level notification list.  I then toggled a setting on the notification page a few times to cause the notifications to go out.   Here's one of the notifications as an example to look at:   { "alertData":{ "name":"Alerts", "url":"/manage/configure/alerts", "changes":{ "rogueAp":{ "label":"A rogue AP is detected", "oldText":"{\"enabled\":false}", "newText":"{\"enabled\":true}", "changedBy":"Someone (someone@company.com)", "ssidId":null } }, "userId":123456 }, "alertId":"1234567890123456789", "alertType":"Settings changed", "occurredAt":"2018-10-29T14:41:39.953568Z", "organizationId":"654321", "organizationName":"Org Name", "organizationUrl":"https://n123.meraki.com/o/5pWeda/manage/organization/overview", "networkId":"N_1234567890123456", "networkName":"A Network Name", "networkUrl":"https://n123.meraki.com/A-Network-Name/n/HakdfJH/manage/nodes/list", "version":"0.1", "sharedSecret":"asharedsecret", "sentAt":"2018-10-29T14:51:47.623106Z" } ... View more

Meraki does not validate the secret.  Instead, the value is included in the payload sent to your environment.  It's up to you to validate the secret (if you choose to do so).   If you're not going to validate the shared secret, you can enter any value you want. ... View more

Yes, you would create two RF Profiles.  You then assign the RF profiles to your access points using the Wireless > Radio Settings page.   You will find settings for 5GHz-only, 2.4GHz-only, and dual-band (with optional steering) on the RF Profile page. ... View more

I had to submit a case to Meraki support to get access to the Wireless Health APIs.  Until then, I received a 404 on any requests to that set of APIs.   Also, make sure you use valid values for t0 and t1.  I don't think you can submit 0 and 3600 (as you did in your example) to get the last hour.  Instead, you need to specify unix epoch values (see https://www.epochconverter.com/ if you are unfamiliar).   @PhilipDAth - I played around with connectionStats in hope that it would provide client counts or connection status for specific clients.  As far as I can tell, that's not what the API does.  Instead, the API provides the same type of information shown in the dashboard UI for Wireless Health.  The connectionStats object only seems to show information when a client attempted to establish a connection during the specified time window.   For example, one of my networks has 8 active clients.  When I query connectionStats for the last hour, I receive an empty array as a reply.  If I query for the last 3 hours, I only see a single entry for a device that happened to disassociate and re-associate at that time.   Unless I'm missing something, I don't see how the Wireless Health APIs can provide current client status information. ... View more

  Meraki describes the hash algorithm in pseudocode:     hash(mac bytes, org secret) = SHA1(mac bytes ++ org secret).takeRight(4) where: ++ indicates concatenation; takeRight(4) returns the least significant 4 bytes of the SHA1; and org secret is a per-customer salt. Example: client MAC is 11:22:33:44:55:66 org secret is t3lrdd least significant 4 bytes of SHA1(112233445566t3Irdd) = 0x0e456406   I'm not sure why you would want to implement this yourself, but here's an example in Node.js   var crypto = require('crypto'); merakiHash('11:22:33:44:55:66', 't3Irdd'); function merakiHash(mac, secret) { var sha1 = crypto.createHash('sha1'); var macBytes = mac.replace(/:/g, ''); sha1.update(Buffer.from(macBytes, 'hex')); sha1.update(secret); var hashResult = sha1.digest('hex').slice(-8); console.log('least significant 4 bytes of SHA1(' + macBytes + secret + ') = 0x' + hashResult); return hashResult; }   For any Meraki people following along, would you mind updating the docs?  The comment in your pseudocode uses a different org secret than the example, which made this a little more painful than it should have been.  "t3lrdd" is not the same as "t3Irdd".     ... View more

You're talking about 3 minutes to go through the entire organization.  I don't know your exact use case, but that doesn't sound 'very time consuming' to me.   The Scanning API includes the ssid parameter.  If you only want to track the connected clients, simply filter out the records with a empty ssid in the data you receive from the Scanning API.   If you want to review data from yesterday, last week, or last month, you can use the Organization Summary Report. ... View more

Are you certain that you're getting a 200 response?  Some Meraki API calls will respond with a redirect.  Not all libraries default to following redirects and some will even follow the redirect as a GET rather than a PUT or POST.   Do you want to share a bit of your python code (make sure to remove API key and any device serial numbers or network ids)? ... View more

To use /devices/[serial]/clients, you first need the serial number of the device you want to check.  You can get the serial number from another API (network or inventory) or from the Meraki Dashboard UI.   When you make the clients API call, you must include a parameter 'timespan'.  This parameter tells the API how far back you want to look when listing clients (in seconds).  For your use case, you might call the API with a timespan of 1 hour (3600 seconds) and again with a timespan of 1 day (86400 seconds).  For any devices that appear in the 1-day query but not in the 1 hour query, you would revoke the splash authorization through the API call I already mentioned.   With the Scanning API, you would listen for data from Meraki, keep a list of devices and when you last saw them, and revoke authorization when a device disappears for a predefined period of time.   ... View more

I'm aware of three ways to force a client to visit the captive portal page after they sign-in or click-through successfully:  - Time limit (as you know)  - Manually click 'Revoke' on the client detail page in Meraki dashboard  - Call the splashAuthorizationStatus API   I don't know of an automated solution to revoke the sign-in or click-through based on a client leaving an area of WiFi coverage.   I suppose you could use Meraki's Scanning API to monitor which devices are connected and call the splashAuthorizationStatus API when a device disappears for a set period of time.   You might also be able to use the /devices/[serial]/clients API with different values for timespan to try to figure out which devices were recently connected but are no longer in the area.   What's the reasoning behind forcing a client to re-login on each return visit and treating that differently from someone sitting in the store for a long period of time? ... View more

If you set up a trial account with Twilio, there are some important limitations to keep in mind.  For the full list, see https://support.twilio.com/hc/en-us/articles/223136107-How-does-Twilio-s-Free-Trial-work-   Here's the specific limitation you're likely seeing:   Outbound trial messages can only be placed to a validated phone number. Before attempting to place an outbound call, be sure to verify the number. Only numbers in the US and Canada can be reached by default; for help enabling messages to a desired country, please see our Global SMS on Trial Accounts article.     ... View more