Maestro MCZ Extra Sensors is a read-only custom integration for Home Assistant that exposes additional data reported by compatible MCZ Maestro stoves. It uses the existing Maestro MCZ integration to show information such as exhaust temperature, operating state and brazier cleaning values as entities.
The integration remains beta. See the Bronze quality review for completed work and outstanding requirements; this is not an official quality rating.
The integration includes the MCZ icon and logo as local branding for Home Assistant 2026.3 or newer.
The integration has been installed on Home Assistant 2026.10.4 with Maestro MCZ 0.6.7-beta and an MCZ Ego Comfort Air stove with M2S.AIR.24.20 firmware. Not every entity or operating state has been validated. Other models and firmware may expose different fields and have not been verified.
- Configure your stove in the Maestro+ MCZ app and verify that it is connected.
- Install and configure the Maestro MCZ integration in Home Assistant. Confirm that it can see your stove.
- Make sure your Home Assistant installation can reach the MCZ cloud through the existing integration.
- Copy the
custom_components/maestro_rtinfodirectory from this repository to thecustom_componentsdirectory in your Home Assistant configuration directory. Createcustom_componentsif necessary. - Restart Home Assistant.
- In HACS, open Integrations and choose Custom repositories from the menu.
- Add
https://github.com/olerida/maestro_rtinfowith category Integration. - Find Maestro MCZ Extra Sensors in HACS and select Download.
- Restart Home Assistant.
This is a custom repository; it is not included in the default HACS catalog. The current release is a beta; select Show beta versions in HACS if it is not listed.
Install the available update from HACS and restart Home Assistant. If the beta release is not listed, enable Show beta versions for this repository in HACS. Existing entity settings are preserved.
- In Home Assistant, open Settings → Devices & services.
- Select Add integration and search for Maestro MCZ Extra Sensors.
- Under Maestro MCZ integration, select the account already configured in the original integration and submit.
No additional MCZ credentials are required. Repeat the setup for another Maestro MCZ account if needed.
The integration discovers scalar values available in the original integration's State and Status data. Depending on the stove and data returned, it can provide:
- Sensors: operating phase and active power, exhaust and board temperatures, requested and actual exhaust fan and auger speeds, cleaning information, and recipe values.
- Binary sensors: available on/off status fields, such as the adaptive mode and other operating options.
Identified entities have icons appropriate to their function; undocumented fields use a neutral icon. You can customize an entity icon in Home Assistant.
The integration does not provide controls and does not send commands to the stove. Fields already registered by Maestro MCZ are not intentionally duplicated. Some reviewed fields use technical names because their meaning has not been verified. See the field inventory for the investigation based on one stove.
New entities for fields whose meaning is unconfirmed are disabled by default. To enable one, open Settings → Devices & services → Entities, show disabled entities, select the entity and enable it. This default applies when an entity is first registered; existing enabled or disabled choices are preserved during updates. Field availability can vary with the data reported by the stove.
The integration reads data from the existing Maestro MCZ coordinator and updates when that coordinator updates. It does not make its own cloud requests. The polling interval is controlled by the original integration and may be slower than the Maestro+ app's real-time display.
Before setup, the integration checks that at least one source coordinator reports a successful last update. It does not force another cloud request. If all updates failed, configuration reports an error and existing entries retry setup.
- This is an independent community project, not an official MCZ integration.
- Only data retained by the original Maestro MCZ integration is available; some app data may be missing.
- Model coverage and the meaning and units of some fields remain unverified. A field may retain its last value while the stove is off; for example, active power alone does not prove that the stove is heating.
- The component uses internal interfaces of Maestro MCZ. An upstream update may require changes here. The code supports the coordinator structures inspected in 0.6.7-beta and 1.0.2; end-to-end operation with 1.0.2 has not been tested.
- Reload this integration after reloading or updating the original Maestro MCZ integration.
- Identified entity names and the setup flow are available in English and Spanish. Unidentified fields retain their technical names.
- No Maestro MCZ account is available during setup: configure the original integration first and check that it is loaded. Each account can be added only once.
- An entity is missing: check the device's diagnostics and the disabled-entity list. Entities are created only when the original integration supplies a scalar value; values unavailable for your model may never appear.
- Values are unavailable or stale: check the stove's connection and the original integration. This integration uses its connection and update schedule.
- The original integration was reloaded: reload Maestro MCZ Extra Sensors so it reconnects to the current coordinator.
Open Settings → Devices & services, select Maestro MCZ Extra Sensors, open its menu and select Delete. To remove the files as well, delete custom_components/maestro_rtinfo and restart Home Assistant. The original Maestro MCZ integration and its account are separate.
The project code is available under the MIT License. The Maestro+ icon and MCZ trademarks belong to their respective owner and are not covered by the MIT license.
Security: only explicitly reviewed telemetry fields are exposed; unknown fields are ignored. Previously registered unknown entities may become unavailable.