---
description: This page provides a comprehensive reference of all entities provided
  by the Meraki Dashboard integration.
tags:
- home-assistant
- cisco-meraki
- network-monitoring
- smart-home
---

# Supported Entities

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

<!-- This file is auto-generated by scripts/generate_docs.py - do not edit manually -->

## 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:

| Name | Key | Device Class | Unit | State Class | Category | Icon | Precision |
|----------|----------|----------|----------|----------|----------|----------|----------|
| Apparent Power | apparentPower | APPARENT_POWER | VA | MEASUREMENT | - | - | - |
| Battery | battery | BATTERY | % | MEASUREMENT | - | - | - |
| Button | button | - | - | - | - | mdi:gesture-tap-button | - |
| CO2 | co2 | CO2 | ppm | MEASUREMENT | - | - | - |
| Current | current | CURRENT | A | MEASUREMENT | - | - | 2 |
| Frequency | frequency | FREQUENCY | Hz | MEASUREMENT | - | - | 2 |
| Humidity | humidity | HUMIDITY | % | MEASUREMENT | - | - | 1 |
| Indoor Air Quality | indoorAirQuality | AQI | - | MEASUREMENT | - | - | - |
| Last Seen | lastSeen | TIMESTAMP | - | - | DIAGNOSTIC | - | - |
| NO2 | no2 | NITROGEN_DIOXIDE | μg/m³ | MEASUREMENT | - | - | - |
| Noise | noise | SOUND_PRESSURE | dB | MEASUREMENT | - | - | - |
| Ozone | o3 | OZONE | μg/m³ | MEASUREMENT | - | - | - |
| PM10 | pm10 | PM10 | μg/m³ | MEASUREMENT | - | - | - |
| PM2.5 | pm25 | PM25 | μg/m³ | MEASUREMENT | - | - | - |
| Power Factor | powerFactor | POWER_FACTOR | - | MEASUREMENT | - | - | 3 |
| Real Power | realPower | POWER | W | MEASUREMENT | - | - | - |
| Signal Strength | signalStrength | SIGNAL_STRENGTH | SIGNAL_STRENGTH_DECIBELS_MILLIWATT | MEASUREMENT | DIAGNOSTIC | - | - |
| TVOC | tvoc | VOLATILE_ORGANIC_COMPOUNDS | μg/m³ | MEASUREMENT | - | - | 0 |
| Temperature | temperature | TEMPERATURE | °C | MEASUREMENT | - | - | 1 |
| Voltage | voltage | VOLTAGE | V | MEASUREMENT | - | - | 1 |


### MT Energy Sensors

Energy sensors are calculated from power readings when available:

| Name | Key | Device Class | Unit | State Class | Precision |
|----------|----------|----------|----------|----------|----------|
| Energy | realPower_energy | ENERGY | Wh | TOTAL_INCREASING | 1 |


### Organization-Level Sensors

These sensors provide organization-wide diagnostic information:

| Name | Key | Unit | State Class | Category | Icon |
|----------|----------|----------|----------|----------|----------|
| API Calls | api_calls | - | TOTAL_INCREASING | DIAGNOSTIC | mdi:api |
| API Calls per Minute | api_calls_per_minute | calls/min | MEASUREMENT | DIAGNOSTIC | mdi:timer-outline |
| API Rate Limit Queue Depth | api_rate_limit_queue_depth | requests | MEASUREMENT | DIAGNOSTIC | mdi:format-list-numbered |
| API Throttle Events (1h) | api_throttle_events | events | MEASUREMENT | DIAGNOSTIC | mdi:clock-alert-outline |
| API Throttle Wait Time | api_throttle_wait_seconds_total | s | TOTAL_INCREASING | DIAGNOSTIC | mdi:timer-sand |
| Failed API Calls | failed_api_calls | - | TOTAL_INCREASING | DIAGNOSTIC | mdi:api-off |


### Network Hub Sensors

These sensors provide per-network hub diagnostic information:

| Name | Key | State Class | Category | Icon |
|----------|----------|----------|----------|----------|
| Device Count | device_count | MEASUREMENT | DIAGNOSTIC | mdi:counter |


## Binary Sensors

### MT Binary Sensors

| Name | Key | Device Class | Icon |
|----------|----------|----------|----------|
| Door Open | door | DOOR | mdi:door |
| Downstream Power | downstreamPower | POWER | mdi:power-plug |
| Remote Lockout Switch | remoteLockoutSwitch | LOCK | mdi:lock |
| Water Detected | water | MOISTURE | mdi:water-alert |


## Buttons

| Name | Key | Description | Icon |
|----------|----------|----------|----------|
| Discover devices | discover_devices | Button to manually trigger device discovery across all network hubs. | mdi:magnify-scan |
| Update sensor data | update_sensor_data | Button to manually trigger sensor data update across all coordinators. | mdi:refresh |


## Coverage Summary

Totals by platform:

| Platform | Count |
|----------|----------|
| Sensors | 28 |
| Binary Sensors | 4 |
| Buttons | 2 |

Totals by device type:

| Device Type | Sensors | Binary Sensors | Total |
|----------|----------|----------|----------|
| MT | 21 | 4 | 25 |
| MR | 0 | 0 | 0 |
| MS | 0 | 0 | 0 |
| MV | 0 | 0 | 0 |

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

- MR
- MS
- MV

Breakdown by description dictionary:

| Dictionary | Count |
|----------|----------|
| MT_ENERGY_SENSOR_DESCRIPTIONS | 1 |
| MT_SENSOR_DESCRIPTIONS | 20 |
| NETWORK_HUB_SENSOR_DESCRIPTIONS | 1 |
| ORG_HUB_SENSOR_DESCRIPTIONS | 6 |
| MT_BINARY_SENSOR_DESCRIPTIONS | 4 |

## 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

- [Device Support](../device-support.md) - Detailed device compatibility
- [Entity Naming](../naming-conventions.md) - Naming convention details
- [API Optimization](../api-optimization.md) - Performance considerations