Ventilation control

The function drives a two-speed VMC. It associates a command feature (ventilation-switch), on the switch side, with a control feature (ventilation-controller), on the output micro-module side.

Ventilation states

  • Off

  • Low speed

  • High speed

Command sources

  • The mobile app, either locally (Bluetooth) or remotely (via a WiFi gateway),

  • A two-way switch wired to a micro-module input,

  • A scenario configured from the app,

  • A voice assistant (via the gateway and the Cloud),

  • The IoT Hub (restricted access, administration)

Command switches

Two wirings are offered at installation:

  • PV/GV — a single two-way switch selects the speed, and the ventilation keeps running.

  • PV/GV + M/A — a double two-way switch: the M/A key turns the ventilation on or off, the PV/GV key selects the speed.

A ventilation system renews the air of the home and runs permanently. Turning it off is limited to a short maintenance period.

On an overheat alert, the ventilation goes off — see Overheat alert.

📋 Requirement: the ventilation takes one of the three states off, low speed and high speed.

📋 Requirement: at any time, at most one of the two outputs of the ventilation controller is closed, including during a speed change.

📋 Requirement: a command requesting the current ventilation state leaves its outputs in place, without switching.

📋 Requirement: the ventilation command is installed on an input wired to a two-way switch, in one of the two wirings PV/GV and PV/GV + M/A.

📋 Requirement: each position change of a command switch imposes on the ventilation the state matching its new position, whatever state the application, a scenario or another switch set it to in the meantime.

📋 Requirement: when the controller is installed, the ventilation starts at low speed.

📋 Requirement: the ventilation page in the application offers the three states off, low speed and high speed.

📋 Requirement: the application shows the actual ventilation state, whatever the source of the last change: switch, scenario, IoTHub, voice assistant, another phone, overheat alert.

📋 Requirement: the application commands the ventilation off only on an explicit choice of the user.

📋 Requirement: when the user chooses off from the application, the application shows a warning: turning a ventilation off is limited to a short maintenance period.

📋 Requirement: as long as the ventilation is off, whatever the origin of the stop — application, switch, scenario, IoTHub, voice assistant, overheat alert —, its page in the application shows a banner recalling that a ventilation runs permanently.

📋 Requirement: a scenario sets the ventilation to one of the three states off, low speed and high speed.

📋 Requirement: a voice assistant turns the ventilation on at low speed, turns it off, and sets low or high speed.