HVAC Control and Smart Thermostat Integration

The current HVAC system is a ducted unit controlled by a proprietary Mitsubishi MA remote controller, which is incompatible with standard 24V smart thermostats like Nest or Ecobee. To achieve Wi-Fi connectivity, one must utilize Mitsubishi-specific interfaces or controllers rather than standard third-party smart thermostats.

Key claims

• [EXTRACTED] The HVAC system is a ducted unit [doc-1].
• [EXTRACTED] The existing wall controller is a Mitsubishi Electric PAR-21MAA, which uses a non-polarized 2-wire communication protocol rather than standard 24V signals [doc-2].
• [INFERRED] Standard smart thermostats (e.g., Nest, Ecobee) cannot be installed directly because they rely on conventional 24V wiring, which this system does not provide [doc-2].
• [INFERRED] Achieving smart control requires either a proprietary Mitsubishi Wi-Fi interface (e.g., MAC-567IF/MAC-587IF) or a specific Mitsubishi-compatible thermostat interface [doc-2].
• [AMBIGUOUS] The feasibility of using a "modern smart thermostat" depends on the specific model of the indoor AC unit, which has not yet been identified [doc-2].

Cross-references

• The "ducted unit" mentioned in [doc-1] provides the context for the control limitations discussed in [doc-2]. While [doc-1] establishes the hardware type, [doc-2] explains the technical constraints that this hardware imposes on smart home upgrades.

Open questions / gaps

• What is the specific model number of the indoor AC unit?
• What lies beneath the lower flap of the current controller, which is required to determine if a thermostat interface adapter is compatible?
• Are there third-party bridge devices (e.g., CoolAutomation) that might allow for Nest/Ecobee integration if the user prefers those over the native MELCloud interface?

Provenance

• [doc-1]: Identifies the HVAC system as a ducted unit.
• [doc-2]: Explains the incompatibility of the current Mitsubishi controller with standard smart thermostats and suggests proprietary alternatives.