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

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.