Skip to main content
Cisco Meraki

Sensor Alert Profiles

  1. Last updated
  2. Save as PDF

Overview

The MT line of sensors have a robust and easy to set up alerts in order to notify a user in the event of threshold violation. This article outlines the process to create an Alert Profile and assign it to a sensor.

Each alert profile may have multiple sensor thresholds which trigger based on the conditions specified.  We can assign multiple email recipients, as well as a phone number for SMS notification.

NOTE: No Twilio integration is required for SMS notifications to operate.

Setting up an Alert Profile

Once the MT sensors are set up correctly and reporting data to the dashboard, in order to set up notifications, an Alert Profile must be created. The Alert Profiles can also be set to only send alerts during a set schedule. To create an Alert Profile, follow the steps outlined below.

There are two types of Alert Profiles currently configurable:

Sensor Status Alerts

This is a default alert profile that allows the user to configure device level status alerts. The profile is treated as a default and applied to all sensors automatically and only allows the user to toggle the alerts on/off and configure recipients.

  1. Navigate to Environmental > Overview > Alert Profiles.
    clipboard_edb35bdf898effd2a2effd0a874c9c388.png
  2. Select Edit on the Sensor status alerts profile.

clipboard_e47dadfd6e4d2574b5750a8cb9c5b3349.png

3. Alert conditions can be set in this profile based on either general device health or model specific.

mt default alert new.png

 

4. An Email or SMS Recipient can be added in the field for notifications. As per the note, all default recipients in the network-wide alerts will be automatically subscribed.
clipboard_e662c03d84888b7f40e9ab843f463bbb3.png

Users can also subscribe to Meraki App Push Notification by adding their Dashboard User email as an Email Recipient on the alert profile.

5. Selecting Save will save the Alert Profile.

This Alert Profile is applied automatically to all sensors in the network and doesn't need to be applied manually.

Sensor Alert Profile

  1. Navigate to Environmental > Overview > Alert Profiles.
    clipboard_edb35bdf898effd2a2effd0a874c9c388.png
  2. Select New environmental alert.
    clipboard_ec4cec3ea7de9f5110e812d6d722132ea.png
  3. Provide a name and set an Alerting Schedule. If Always is going to be selected, skip to step 11.
    clipboard_e57d0fec19d97655e64c610e566f9169a.png
  4. If Alerting Schedule is set to Scheduled the alerts will only be sent during the specified timeframe.
     
  5. Click on Change schedules.
    clipboard_ed9106f16177f5e86d8190ba3634d20f7.png
  6. Create a New Schedule
    clipboard_e6075afacdf512c702158e3d2b167bbf1.png
  7. Provide a name and select a schedule for the alert to be enabled:
    clipboard_e1b0174282002f22ec29e3eac75937a38.png
  8. Click on Done to save the alert schedule.
  9. Click on Select for the newly created schedule.  You should see Selected under the schedule.
    clipboard_ea3ef1d9a8073dc5506c556e9eb314a2a.png clipboard_e659d1f4e8433196a58a86d0bb0f9f3c3.png
  10. Click Save to have it appear under Alerting Schedule.
    clipboard_edde69b41171c31654b2f5afb91666e36.png
  11. Alert Conditions can be set for Temperature, Humidity, Water, Door, Indoor Air Quality, TVOC, PM2.5, and Ambient Noise states and levels. Along with that an Alert back off can be optionally set for each metrics (with the exception of Water Detection) in case the alert only needs to be sent if the state persists for an extended period of time.
    mt alert conditions new.png
  12. An Email or SMS Recipient can be added in the field for notifications. As per the note, all default recipients in the network-wide alerts will be automatically subscribed.
    clipboard_e662c03d84888b7f40e9ab843f463bbb3.png

Users can also subscribe to Meraki App Push Notification by adding their Dashboard User email as an Email Recipient on the alert profile.

13. Selecting Save will save the Alert Profile.

Note: The alert profile will be sent if ANY of the condition's thresholds are triggered.

Note: As the UI suggests, all recipients under Network-wide > Alerts are automatically subscribed. This also includes any subscribed Webhook Servers.

Assigning the Alert Profile

After the Alert Profiles have been created, it needs to be assigned to a set of sensors. It can be assigned by 2 methods:

Individually from the Sensor Details page:



Devices - Meraki Dashboard 2020-10-26 12-34-35(1).png

  1. Once the Alert Profile has been created, navigate to Environmental > Monitor > Overview > Sensors and Select a sensor.

  2. On the left side rail, the pencil button under the Environmental Alert Profile section will bring up a modal to Assign Alert Profiles.
    clipboard_e8475cf05f737dd40bc83944d203e3710.png

  3. Select the desired Alert Profile and click Save.
    clipboard_e03e3c3035c8aaced629c53fdda175588.png

Bulk Assign

  1. After the Alert Profile has been created, navigate to Environmental > Monitor > Overview > Sensors.

  2. Check the box next to multiple sensors and click on More actions > manage alert profiles button in the top-right.
    clipboard_e70b62eefd6c04d06b2c4781ca638f600.png

  3. Select the desired Alert Profile(s) and hit Save. 
    clipboard_e9a5c5bd47ee7d0c1bb04b2defb17ec7c.png

Webhooks

The MT device alerts also generates Webhook Alerts when any of the conditions on an Alert Profile are met. A webhook server can be scoped to any alert profile. 

Here are the steps to get a Webhook Alert for MT sensors:

  1. Create and add a Webhook Server under Network-wide > Alerts.
    clipboard_ed8a93496f5cfea4ca609ec418a424175.png
  2. Add a new Environmental Alert Profile using any of the methods mentioned in Setting up an Alert Profile and scope the Webhook Server created in step 1.
    clipboard_e7520050784fc68ea593a524daba9e76d.png
    For additional help on creating Webhook servers, see Webhook setup for more information.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
    Stage
    Draft
  2. Tags
    This page has no tags.