I’m planning an automation to run a air‑conditioner alongside a Zehnder ComfoAir Q350 and want to avoid the MVHR venting cooled indoor air (i.e., opening the summer bypass while the AC compressor is running). I’ve read about both the official integration and the GitHub/HACS component and would like to confirm a few practical points ..?
My setup
ComfoAir Q350 with ComfoConnect LAN‑C bridge
Home Assistant (running HA OS)
sensor.comfoairq_bypass_state (reports 0/100),
sensor.comfoairq_inside_temperature,
sensor.comfoairq_outside_temperature,
sensor.comfoairq_supply_temp,
sensor.comfoairq_extract_temp.
Questions
From your experience, is it safe and reliable to automate the ComfoAir Q350 so the bypass is forced Closed while any AC compressor is active, and then allow Auto/Open only when outside is sufficiently cooler?
Any pitfalls I should be aware of when doing this.. ?
Does the HACS/custom component expose writable bypass commands or a select entity (e.g., select._bypass_mode) and services such as comfoconnect.bypass_on / bypass_off? If so, are those commands reliable for automation (immediate effect, persisted state)?
How does the official integration differ in practice from the HACS version regarding control (ability to force bypass open/closed), telemetry, and stability? Which would you recommend for a setup that must guarantee the bypass never opens while AC is cooling?
Any recommended automation patterns or safety checks you’ve seen work well (e.g., AC compressor detection method, hysteresis values, dew‑point checks, minimum timeouts)?
If helpful, I can paste entities, integration details, and a short log of the ComfoConnect messages when I manually toggle bypass.
Any guidance or examples you can share would be appreciated.
If there’s a preferred way to test or a debug log you’d like me to attach, tell me what to collect and I’ll post it.