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)
• MR - Wireless access points providing WiFi connectivity and network metrics (model prefixes: MR, CW)
• MS - Network switches providing port status, PoE power, and traffic metrics (model prefixes: MS)
• MV - Security cameras providing video analytics and motion detection (model prefixes: MV) (no entities defined yet)

Sensors¶

MT Environmental Sensors¶

MT devices provide environmental monitoring capabilities:

MT Energy Sensors¶

Energy sensors are calculated from power readings when available:

MR Wireless Access Point Sensors¶

MR devices provide wireless metrics per access point:

MR Network Sensors¶

Network-level wireless metrics aggregated per network hub:

MS Switch Sensors¶

MS devices provide switch and port monitoring:

MS Network Sensors¶

Network-level switch metrics aggregated per network hub:

Organization-Level Sensors¶

These sensors provide organization-wide diagnostic information:

Network Hub Sensors¶

These sensors provide per-network hub diagnostic information:

Binary Sensors¶

MT Binary Sensors¶

Buttons¶

Coverage Summary¶

Totals by platform:

Totals by device type:

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

• MV

Breakdown by description dictionary:

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 per device type, such as:

• lan_ip, gateway, ip_type, primary_dns, secondary_dns (MR/MS devices)
• memory_usage (MR/MS devices when organization memory data is available)
• port_types, poe_enabled_ports, port_configurations (MS devices)
• 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
• MR default scan interval: 600
• MS default scan interval: 600
• MV default scan interval: 600

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 - Detailed device compatibility
• Entity Naming - Naming convention details
• API Optimization - Performance considerations