Marvin Connected Home for Home Assistant

An unofficial Home Assistant integration for Marvin Connected Home automated windows, skylights and doors.

Disclaimer

This is an independent, unofficial project. It is not affiliated with, authorized by, endorsed by, or sponsored by Marvin (Marvin Windows and Doors). “Marvin”, “Marvin Connected Home”, “Awaken” and “CLiC” are trademarks of their respective owners, used here only to identify the hardware this software talks to.

Marvin publishes no public API and runs no developer programme. This software was written by observing the network traffic of the author’s own Marvin account and the author’s own windows. It uses no confidential or proprietary information from Marvin, and no access to any account, device or system other than the author’s own.

Marvin makes no backward-compatibility commitment for these interfaces. Authentication, endpoints, data structures and behaviour may change at any time and without notice, and when they do this integration will break until someone fixes it. Marvin does not support it, and neither the breakage nor anything following from it is Marvin’s responsibility. Marvin’s own supported integration paths are Control4, Crestron and Amazon Alexa; if you need a vendor-supported setup, use one of those.

It is distributed through HACS as a custom repository only — it is not part of Home Assistant core and has not been submitted for inclusion.

Provided free under the MIT licence, as is and without warranty of any kind. It drives motorised windows: do not rely on it where a window failing to open, failing to close, or moving unexpectedly would matter. Use at your own risk.

Integration on GitHub · Python client library

What it does

Marvin’s own sanctioned integrations — the Control4 driver, the dry-contact terminals behind the trim — give you a handful of fixed stops and, in Control4’s case, roughly ten-minute polling latency. This integration talks to the same cloud service the Marvin Home app does, which turns out to be considerably more capable than what the sanctioned paths expose:

• Covers with real 0–100% positioning. Position streams live while the window is travelling, rather than jumping between preset stops.
• Sub-second state, including changes Home Assistant did not make. State arrives over SignalR, so pressing the button on the unit or firing a dry-contact relay shows up in Home Assistant immediately.
• Optional dry-contact fallback. If you have the contacts wired to switch entities and the Marvin cloud is unreachable, commands fall back to them automatically.
• Sensors for lock, rain, obstruction, backup power and faults, plus per-component firmware versions and writable dry-contact stop positions.

Why it is cloud-based

The windows are ESP32 devices that hold one outbound MQTT/TLS connection to Azure IoT Hub. A full 65,535-port scan of real hardware found no listening ports at all, so local control is not reachable without modifying firmware — which on an installed window means soldering, brick risk, and giving up rain auto-close and OTA updates.

The consolation is that the cloud path is genuinely fast. Sub-second updates were measured against real hardware.

Installing

Through HACS, add https://github.com/cb2206/ha-marvin-connected-home as a custom Integration repository, install it, and restart Home Assistant. Then add the integration from Settings → Devices & services.

Full installation and sign-in instructions, including why the config flow asks you to paste a URL back, are in the README.

Further reading

• API reference — the reverse-engineered endpoints and realtime protocol
• Design notes — entity modelling decisions and open questions
• Research notes — how the platform was worked out
• Issue tracker

Released under the MIT licence.