Eight environmental and power sensors on the same dashboard as the network

Cisco Meraki MT sensors report temperature, humidity, water, air quality, door state, and power draw into the Meraki dashboard over Bluetooth Low Energy.

Availability, lead time, licensing, and configuration are confirmed during the quote.

Cisco Meraki MT Sensors product renderImage: Cisco Meraki

Models

8 of 8 models

Need better pricing?

Catalog pricing is available to everyone. Volume, project and registered-deal pricing is usually better — tell us what you need and we will price it.

Compatibility and references

Source review date: 2026-09-26

Official documentation

MT is a small, complete family: Cisco documents eight sensor types and HTS carries all eight. The MT10 measures temperature and humidity. The MT11 is a probe sensor for measuring inside a fridge, freezer, or other enclosed space where the gateway cannot sit. The MT12 detects water. The MT14 measures indoor air quality, and the MT15 adds carbon dioxide to the same measurement set. The MT20 reports open and closed state on a door or cabinet. The MT30 is a smart automation button. The MT40 is a smart power controller that both monitors and switches an outlet.

Cisco documents MT sensors as integrating with the Meraki dashboard using BLE, which is the detail that determines whether a deployment will work. The sensors do not carry their own network connection; they report through a nearby Meraki gateway device. That makes MT a straightforward addition to a site that already runs Meraki access points or a compatible gateway, and a more involved conversation at a site that does not — the sensor placement has to fall within radio range of something that can hear it, and cold rooms, metal cabinets, and thick walls all affect that.

The common deployments are narrow and worth naming: freezer and fridge monitoring in food service, catering, and clinical settings using the MT11 probe; server-room and comms-cupboard temperature using the MT10; leak detection under floors and in plant rooms using the MT12; occupancy comfort and ventilation evidence using the MT14 and MT15; and door-held-open alerting using the MT20. HTS quotes MT against the specific thing you need evidence of, confirms gateway coverage at each sensor position, and confirms licence alignment with your existing Meraki organisation before ordering.

How HTS deploys it

MT sensors report over Bluetooth Low Energy through nearby Meraki devices — MV cameras and MR access points act as the gateways — so the first thing HTS verifies is radio coverage at each intended sensor position, not the sensor. Freezers, metal cabinets, and thick walls are exactly where MT gets deployed and exactly where BLE struggles, which is why the MT11 probe exists for readings inside an enclosed space. Placement is confirmed with a live reading from each position before the quote closes.

Deployment rides the Meraki organisation you already have: sensors claim into the same dashboard, alert thresholds live next to the network they protect, and licensing co-terms with the organisation. For sites not yet on Meraki, the gateway conversation comes first — the sensors are the cheap part.

What it costs to run over three years

Each MT sensor needs an MT Enterprise licence in 1-, 3-, 5-, 7-, or 10-year terms, and every Meraki dashboard organisation includes five free MT licences to start (per Cisco's MT documentation). Figures are HTS catalog prices from the 2026-09-24 snapshot.

  • Sensor hardware, one-time: $74.69 for the MT10 temperature/humidity, MT11 probe, MT12 water, MT20 door, and MT30 button; $124.25 for the MT14 air quality and MT40 smart power controller; $365.86 for the MT15 CO2.
  • MT Enterprise licence, per sensor: $67.74 one year / $155.88 three years / $259.58 five years.
  • Worked example: an MT10 on a three-year licence runs $74.69 + $155.88 = $230.57 per point over three years — batteries included, since two AA cells carry up to five years per Cisco's datasheet.
  • The five included licences per organisation cover a pilot without any purchase decision at all.
  • No gateway hardware is needed where MR access points or MV cameras already hear the sensor — the gateway role rides the Meraki licence the site already pays.

What else this needs

  • An MT Enterprise licence per sensor beyond the first five per organisation.
  • BLE gateway coverage at each position — an MR access point or MV camera within radio range.
  • An active Meraki organisation: MT adds to a dashboard, it does not create one.
  • For enclosed spaces, the MT11 external probe rather than an optimistic placement guess.
  • Alert routing decided with the team on call — the dashboard alerts where you point them.

How to choose

  • What you need to measure: temperature and humidity (MT10), probe into an enclosed space (MT11), water (MT12), air quality (MT14), air quality with CO2 (MT15), open and close state (MT20)
  • Monitoring only versus the MT40 smart power controller, which also switches an outlet
  • MT30 automation button where a person needs to trigger an action rather than a sensor reporting a reading
  • Gateway radio coverage at each intended sensor position, since MT reports over BLE rather than its own uplink
  • Whether an existing Meraki deployment can already hear the sensors or a gateway needs adding