Skip to content

Supported Entities

This page provides a comprehensive reference of all entities provided by the Meraki Dashboard integration.

Overview

The Meraki Dashboard integration creates entities based on your Cisco Meraki device types and their capabilities. Each physical Meraki device becomes a Home Assistant device, with individual metrics exposed as entities.

Device Types

The integration supports the following Meraki device types:

  • MT - Environmental monitoring sensors for temperature, humidity, air quality, etc. (model prefixes: MT)

Sensors

MT Environmental Sensors

MT devices provide environmental monitoring capabilities:

NameKeyDevice ClassUnitState ClassCategoryIconPrecision
Apparent PowerapparentPowerAPPARENT_POWERVAMEASUREMENT---
BatterybatteryBATTERY%MEASUREMENT---
Buttonbutton----mdi:gesture-tap-button-
CO2co2CO2ppmMEASUREMENT---
CurrentcurrentCURRENTAMEASUREMENT--2
FrequencyfrequencyFREQUENCYHzMEASUREMENT--2
HumidityhumidityHUMIDITY%MEASUREMENT--1
Indoor Air QualityindoorAirQualityAQI-MEASUREMENT---
Last SeenlastSeenTIMESTAMP--DIAGNOSTIC--
NO2no2NITROGEN_DIOXIDEμg/m³MEASUREMENT---
NoisenoiseSOUND_PRESSUREdBMEASUREMENT---
Ozoneo3OZONEμg/m³MEASUREMENT---
PM10pm10PM10μg/m³MEASUREMENT---
PM2.5pm25PM25μg/m³MEASUREMENT---
Power FactorpowerFactorPOWER_FACTOR-MEASUREMENT--3
Real PowerrealPowerPOWERWMEASUREMENT---
Signal StrengthsignalStrengthSIGNAL_STRENGTHSIGNAL_STRENGTH_DECIBELS_MILLIWATTMEASUREMENTDIAGNOSTIC--
TVOCtvocVOLATILE_ORGANIC_COMPOUNDSμg/m³MEASUREMENT--0
TemperaturetemperatureTEMPERATURE°CMEASUREMENT--1
VoltagevoltageVOLTAGEVMEASUREMENT--1

MT Energy Sensors

Energy sensors are calculated from power readings when available:

NameKeyDevice ClassUnitState ClassPrecision
EnergyrealPower_energyENERGYWhTOTAL_INCREASING1

Organization-Level Sensors

These sensors provide organization-wide diagnostic information:

NameKeyUnitState ClassCategoryIcon
API Callsapi_calls-TOTAL_INCREASINGDIAGNOSTICmdi:api
API Calls per Minuteapi_calls_per_minutecalls/minMEASUREMENTDIAGNOSTICmdi:timer-outline
API Rate Limit Queue Depthapi_rate_limit_queue_depthrequestsMEASUREMENTDIAGNOSTICmdi:format-list-numbered
API Throttle Events (1h)api_throttle_eventseventsMEASUREMENTDIAGNOSTICmdi:clock-alert-outline
API Throttle Wait Timeapi_throttle_wait_seconds_totalsTOTAL_INCREASINGDIAGNOSTICmdi:timer-sand
Failed API Callsfailed_api_calls-TOTAL_INCREASINGDIAGNOSTICmdi:api-off

Network Hub Sensors

These sensors provide per-network hub diagnostic information:

NameKeyState ClassCategoryIcon
Device Countdevice_countMEASUREMENTDIAGNOSTICmdi:counter

Binary Sensors

MT Binary Sensors

NameKeyDevice ClassIcon
Door OpendoorDOORmdi:door
Downstream PowerdownstreamPowerPOWERmdi:power-plug
Remote Lockout SwitchremoteLockoutSwitchLOCKmdi:lock
Water DetectedwaterMOISTUREmdi:water-alert

Buttons

NameKeyDescriptionIcon
Discover devicesdiscover_devicesButton to manually trigger device discovery across all network hubs.mdi:magnify-scan
Update sensor dataupdate_sensor_dataButton to manually trigger sensor data update across all coordinators.mdi:refresh

Coverage Summary

Totals by platform:

PlatformCount
Sensors28
Binary Sensors4
Buttons2

Totals by device type:

Device TypeSensorsBinary SensorsTotal
MT21425
MR000
MS000
MV000

Device types without entity descriptions yet (device type exists but no entity descriptions are defined):

  • MR
  • MS
  • MV

Breakdown by description dictionary:

DictionaryCount
MT_ENERGY_SENSOR_DESCRIPTIONS1
MT_SENSOR_DESCRIPTIONS20
NETWORK_HUB_SENSOR_DESCRIPTIONS1
ORG_HUB_SENSOR_DESCRIPTIONS6
MT_BINARY_SENSOR_DESCRIPTIONS4

Entity Attributes

All Meraki entities include these common attributes when applicable:

  • network_id - Network identifier
  • network_name - Network name
  • serial - Device serial number
  • model - Hardware model
  • last_reported_at - Timestamp of the most recent reading (when available)

Additional attributes may be exposed:

  • mac_address, temperature_fahrenheit (MT devices when available)

Entity Naming

Entities follow Home Assistant naming conventions:

  • Device Name: Uses the Meraki device name (e.g., "Office Sensor", "Main Switch")
  • Entity Name: Combines device name with metric (e.g., "Office Sensor Temperature")
  • Entity ID: Sanitized version (e.g., sensor.office_sensor_temperature)

Update Intervals

Default polling intervals can be configured per hub and per organization. The defaults below are pulled from the integration constants (seconds):

  • Global default scan interval: 300
  • Default discovery interval: 3600
  • MT default scan interval: 30

Organization-level data uses tiered refresh timers by default:

  • Static data interval: 14400
  • Semi-static data interval: 3600
  • Dynamic data interval: 600

Entity Categories

Some entities are categorized as diagnostic to help organize the UI. The tables above include a Category column when set on the description.

See Also