Skip to main content

 

Cisco Meraki Documentation

Common Sensor (MT) Event Log Messages

  1. Last updated
  2. Save as PDF
This article outlines the process of navigating the event log for MT sensor devices, detailing how to access, filter, and interpret various sensor event types through the Meraki dashboard. It provides comprehensive definitions for each event type, such as alert events, ambient noise, battery issues, and temperature events, aiming to aid users in monitoring and managing the physical state of sensors effectively.

Navigating Event Log for Sensors

The event log for MT sensor devices is a powerful tool that offers insight into the physical state of a given sensor. This article will cover how to navigate the event log and definitions of specific entries.

The event log is accessible through the Meraki dashboard. Navigate to Network-wide > Monitor > Event log. 

 If using a combined network, click the drop-down at the top of the page and select the for sensors option.

The gif is displayed to illustrate how to access the event log in the Meraki dashboard by navigating to Network-wide > Monitor > Event log for network monitoring and troubleshooting purposes.

Filter Options

  • Sensor: This filter allows users to select individual sensor devices to view individual logs

  • Gateway: This filter allows users to select sensors based on the gateway access point they are connecting to

  • Event Type: This filter allows users select specific events to focus on

  • Event Type Exclude: This filter allows users to remove event types from the list. Useful if trying to remove common event entries to focus on uncommon ones.

Event Types

Some event types include additional context, which can be found by clicking the expand chevron on the right-hand side:

The image is displayed to show that some event types include additional context accessible by clicking the expand chevron on the right-hand side for more detailed information.

This event triggers if any of the criteria defined in the Sensor Alert Profiles are met, and indicates the alerts are being sent to the configured recipients under the relevant alert profile.

Event Type Alert Event.png

This event triggers if ambient noise levels transition between the thresholds defined in the relevant Alert Profile.

The image is displayed to show that this event triggers when ambient noise levels transition between the thresholds defined in the Alert Profile.The image is displayed to show that this event triggers when ambient noise levels transition between the thresholds defined in the relevant Alert Profile.

This event triggers if a battery cover is attached to a sensor. (Only applicable to the MT20 Sensor)

The image is displayed to show that this event triggers if a battery cover is attached to a sensor, specifically applicable to the MT20 Sensor model.

This events triggers if the connection button was manually pressed, triggering a connection attempt to a wireless gateway.

Event Type Wake up press.png

This events triggers if the button for triggering the configured automation was pressed.

Event Type MT30 button press.png

Event Type MT30 long button press.png

This event triggers if a door is opened or closed.

Screen Shot 2021-02-03 at 4.23.40 PM.png

This event is triggered when an MT20 sensor is right around the threshold of open/close state. If you notice this event, you might want to consider placing the magnet a bit closer to the sensor body. Users can also set up Alerts under the General Status Alert Profile for administrator to be alerted of this state.

The image is displayed to show that this event is triggered when an MT20 sensor is near the threshold between open and close states, suggesting users may need to place the magnet closer to the sensor body, and that alerts can be set up under the General Status Alert Profile to notify administrators of this state.

This type of event indicates that the sensor is flipping between states. Due to the constant flicker, it keeps the sensor awake which has a huge impact on battery life of the sensor.

This event triggers if the sensor detects an unexpected magnetic field that exceeds that of the sensor’s expected magnet. Indicates that additional magnetic devices are affecting sensor operation.

This event is also triggered when the magnet tab is too close to the sensor. There should be at least 1 mm gap between the sensor and the magnet.

This event triggers if a configured humidity Alert Profile is exceeded and indicates a humidity abnormality is present.

This event triggers if the Indoor Air Quality Rating levels transition between the thresholds defined in the relevant Alert Profile.

The image is displayed to show that this event triggers if the Indoor Air Quality (IAQ) Rating levels transition between the thresholds defined in the relevant Alert Profile. This indicates a change in the indoor air quality status as monitored by the sensor system.

This event triggers if the particulate matter levels transition between the thresholds defined in the relevant Alert Profile.

The image is displayed to show that this event triggers if the particulate matter (PM 2.5) levels transition between the thresholds defined in the relevant Alert Profile, indicating a change in air quality as monitored by the sensor system.

This event triggers if the sensor detects a probe cable has been connected or disconnected.

The image is displayed to show that this event triggers if the sensor detects a probe cable has been connected or disconnected, indicating a change in the probe cable connection status for monitoring purposes.

This event triggers when the wireless connection between sensor and gateway is lost temporarily. Recommend ensuring that the wireless environment is stable and a clear connection is available.

This event triggers if the sensor RSSI (Received Signal Strength Indicator) falls below the required minimum value.

The image is displayed to show that this event triggers when the sensor's Received Signal Strength Indicator (RSSI) falls below the required minimum value, indicating insufficient signal strength for reliable communication. This helps identify weak wireless signal conditions affecting sensor performance.

This event triggers whenever an action occurs (such as an MT30 button press) that triggers a Webhook to be sent, as defined under the MT Automation Builder function.

The image is displayed to show that this event triggers whenever an action occurs, such as an MT30 button press, which sends a Webhook as defined under the MT Automation Builder function, enabling users to automate tasks and trigger custom actions through the Meraki dashboard.

This event triggers whenever an action occurs (such as an MT30 button press) that triggers a notification to be sent, as defined under the MT Automation Builder function.

CIRCUIT | Cisco data The image is displayed to show that this event triggers whenever an action occurs, such as an MT30 button press, which sends a notification as defined under the MT Automation Builder function, allowing users to configure custom notifications via email or SMS to be sent automatically upon the button press event.

This event triggers whenever an action occurs (such as an MT30 button press) that causes a Switchport to be toggled, as defined under the MT Automation Builder function.

The image is displayed to show that this event triggers whenever an action occurs, such as an MT30 button press, which causes a specific MS switchport or group of switchports to be toggled on or off, as defined under the MT Automation Builder function, allowing users to automate switchport control via the Meraki dashboard.

This event triggers whenever an action occurs (such as an MT30 button press) that triggers a Camera snapshot to be taken, as defined under the MT Automation Builder function.

This image is displayed to show that this event triggers whenever an action occurs, such as an MT30 button press, which causes a Camera snapshot to be taken, as defined under the MT Automation Builder function, allowing users to automate capturing snapshots from MV cameras via the Meraki dashboard.

This event triggers whenever an action occurs (such as an MT30 button press) that causes an SSID to be toggled, as defined under the MT Automation Builder function.

This image is displayed to indicate that this event triggers whenever an action occurs, such as an MT30 button press, which causes an SSID to be toggled, as defined under the MT Automation Builder function.

This event triggers if a configured temperature Alert Profile is exceeded and indicates a temperature abnormality is present.

This event triggers if the Total Volatile Organic Compound levels transition between the thresholds defined in the relevant Alert Profile.

This image is displayed to indicate that this event triggers if the Total Volatile Organic Compound (TVOC) levels transition between the thresholds defined in the relevant Alert Profile.

This event triggers when a USB cable is inserted or removed from a sensor.

This image is displayed to indicate that this event triggers when a USB cable is inserted or removed from a sensor.

This event triggers if a configured alert profile is exceeded and indicates moisture is present.This image is displayed to indicate that this event triggers when a configured alert profile is exceeded and moisture is detected, signaling the presence of water.

The event triggers if a water detection cable is added or removed from a sensor.

This event indicates that a test alert was issued by an administrator.

This image is displayed to indicate that a test alert was issued by an administrator to verify alert functionality.

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
    Stage
    Final
  2. Tags
    This page has no tags.