LUNOS Heat Recovery Ventilation for Home Assistant

Provides control of decentralized LUNOS Heat Recovery Ventilation fans using any Home Assistant compatible smart relays. The design of the LUNOS low-voltage fan controller uses a pair of physical switches (W1/W2) to turn on/off ventilation, set fan speeds, and to toggle various additional modes such as summertime ventilation, exhaust only modes, etc. See the LUNOS installation details for more information on how the LUNOS wall switches are installed.

While this LUNOS integration allows control of the fan modes through Home Assistant apps, web consoles, and connected voice assistants such as Alexa, the real power comes in supporting a wide variety of automation opportunities when paired with other third-party sensors:

set LUNOS speeds to maximum when high humidity, CO2, VOCs, or radon is detected
keeping LUNOS running at lower speeds, EXCEPT when air quality issues are detected, could provide a balance between LUNOS fan noise (which is already a very quiet fan) and maintaining optimal fresh indoor air quality
increase LUNOS fan speeds to high when kitchen smoke alarm detects smoke
if outside temperature is closer to target temperature on thermostats, engage exhaust only modes in LUNOS devices to expel indoor air (drawing in temperature that is closer to target from leaks in the building envelope or open windows/doors)
turn off LUNOS air circulation when house vacation mode is set, and re-activate LUNOS air circulation whenever motion is detected (or someone arrives at the house)
turn off LUNOS air circulation if outside air quality is detected as being very poor (e.g. nearby forest fires or pollution)
automatically turn on summer ventilation mode when house is set to sleep mode (and return to normal operating mode upon wakeup or specific time during the day)

Support

There is no official support for this add-on and is community supported within the Home Assistant LUNOS discussion thread. If you have any proposed changes or bug fixes, please code them and create pull requests for your patches to the hass-lunos GitHub repository.

Installation

Visit the Home Assistant community if you need help with installation and configuration of LUNOS Fan Control.

Step 1: Install Custom Components

The easiest way to install (and ensure you are always running the latest version), first setup Home Assistant Community Store (HACS), and then add the "Integration" repository: rsnodgrass/hass-lunos

Step 2: Configure Home Assistant

LUNOS Controllers require a pair of switches (W1 and W2) to control the speed of the fans (as well as other features). Configuration is required to assign the Home Assistant accessible W1 and W2 switches for the fan controller to use in operating the LUNOS fan controller.

Configuration Variables

name (Optional): Friendly name for this fan controller
relay_w1 (Required): HASS entity id for the relay switch that is connected as W1 to the LUNOS controller
relay_w2 (Required): HASS entity id for the relay switch that is connected as W2 to the LUNOS controller
controller_coding (Optional): Indicates the manual coding the LUNOS controller is set to (default=e2-usa; see lunos-codings.yaml)
fan_count (Optional): Number of fans connected to this LUNOS controller
default_speed (Optional): Default speed when this LUNOS fan is turned on without any speed indicated

Configuration Example

This example configuration assumes that the relay switches are already setup in Home Assistant, since that setup differs substantially depending on the type of relay hardware being used (e.g. Tasmota MQTT vs WeMo Maker).

fan:
  - platform: lunos
    name: Basement Ventilation
    relay_w1: switch.lunos_basement_w1
    relay_w2: switch.lunos_basement_w2

  - platform: lunos
    name: Bathroom Fan
    default_speed: high
    controller_coding: ego
    relay_w1: switch.lunos_bathroom_w1
    relay_w2: switch.lunos_bathroom_w2

Step 3: Add Lovelace Card

The following is a basic Lovelace card using the fan-control-entity-row customization:

- entity: fan.lunos_bathroom
  type: custom:fan-control-entity-row

And another example with multiple LUNOS ventilation fans and ability to turn on/off the entire house:

type: entities
title: LUNOS Ventilation
entities:
  - entity: fan.lunos_basement
    name: Basement
    type: 'custom:fan-control-entity-row'
  - entity: fan.lunos_bedrooms
    name: Bedrooms
    type: 'custom:fan-control-entity-row'
  - entity: fan.lunos_bathroom
    name: Master Bathroom
    type: 'custom:fan-control-entity-row'

Automation

Supported Services

lunos_turn_summer_ventilation_on (only for supported LUNOS e2 models)
lunos_turn_summer_ventilation_off
lunos_clear_filter_change_reminder

Examples

While using NodeRED can be used to easily create sophisticated (and often easier to understand) ventilation automation, the following examples showcase a few automations that adjust LUNOS fan speeds based on occupancy or air quality issues:

Turn on fans when someone arrives:

automation:
  - alias: "Turn on LUNOS ventilation fans on when anyone arrives home"
    trigger:
      - platform: state
        entity_id: group.people
        to: "home"
    action:
      - service: fan.turn_on
        entity_id: "fan.lunos"
        data:
          speed: "high"

Turn LUNOS ventilation fan to highest speed when high humidity is detected:

automation:
  - alias: "Turn basement LUNOS ventilation on maximum speed if high humidity is detected"
    trigger:
      - platform: foobot
        entity_id: sensor.basement_humidity
    condition:
      condition: numeric_state
      entity_id: sensor.basement_humidity
      above: 55
    action:
      - service: fan.turn_on
        entity_id: "fan.basement_lunos"
        data:
          speed: "high"

# similar automation required to turn LUNOS to lower speed setting once humidity is within tolerance

These same strategies can be used with any Home Assistant compatible devices that track humidity (ecobee, Nest thermostat) or, even better, using air quality measuring devices (Airthings, AirVisual IQAir, Foobot) that measure CO2, VOCs, etc.

Hardware Requirements

LUNOS e2 HRV fan pairs or LUNOS eGO HRV fan
LUNOS Universal Controller
Home Assistant compatible relay

The LUNOS Universal Controller (5/UNI-FT) is powered by a 12V transformer (e.g. the Mean Well #RS-15-12 12V/1.3A/15.6W). To power more than one LUNOS Controllers and fan sets (plus powering a ESP8266 based WiFi relay) from a single transformer, it is recommended the LUNOS included 12V transformer be upgraded to a larger unit. For example, the Mean Well #RS-50-12 transformer produces up to 50W at 12V.

WiFi Smart Relays

IMPORTANT: The pair of smart switches CANNOT be 120V switches as they MUST NOT be connected to any power source. For non-smart installations, the LUNOS Universal Controller typically has non-electrified rocker switches connected as switche W1 and W2. These are relay switches only and not powered. Any smart switches connected the LUNOS Universal Controller must be relay switches only with no chance that the LUNOS Controller would be electrified.

While single-channel WiFi relays can be purchased, for centralized control of several LUNOS zones (using several LUNOS Controllers), purchasing multi-relay modules typically costs less than separate single-channel relays.

Example relays compatible with Home Assistant:

Model	Relays	Tasmota Supported	Manual Buttons	Power
WiFi Relay Switch Module	4	Y	Y	5V USB
MHCOZY 4-channel WiFI wireless switch	4	Y	N	5-32V
LC Technology 4X WiFi Relay (12V ESP8266)	4	Y	N	12V

Tasmota Setup

After flashing your multi-channel WiFi relay with Sonoff, you must connect to it via the Sonoff WiFi to access the Sonoff web configuration interface.

configure the Sonoff relay device to connect to your WiFi network
enable auto-discovery (for automatic Home Assistant integration)
configure the MQTT broker host/user/password that your Home Assistant instance uses
configure the Tasmota switches

In the Sonoff web interface Console, turn on auto discovery (option 19) so Home Assistant can find your relays:

SetOption19 on

Then you must configure in Sonoff web interface the address and username/password for the MQTT broker that Home Assistant uses.

For more information on flashing ESP8266 based relays:

Example Wiring with WiFi Relay Switch Module (SANT-4CH)

The only downside of the SANT-4CH relay switch is that the four pins (GND, VCC, TXD, RXD) are solder filled which makes it difficult to temporarily hook up wires to flash Tasmota.

Example Wiring with ESP8266 WiFi Relay

The following is an example connecting a LC Technology 12V ESP8266 Four-Channel WiFi Relay to the LUNOS Controller. Additional controllers that should work including the Sonoff 4CH.

Wireless and Alexa Integration

One idea for a clean physical LUNOS switch installation is assigning a Lutron Caséta Pico Fan Speed Controller (PD-FSQN-WH-R) to a LUNOS fan within Home Assistant allows extremely slick and simple control of a LUNOS fan in a single gang outlet box in an occupied space. The larger W1 and W2 control switches can then be "hidden" in a utility room or closet.

Additionally, once added to Home Assistant, LUNOS fan speeds can be configured to be controlled by Alexa or other voice enabled smart speaker.

Currently Not Supported

attribute indicating current ventilation mode: [standard, summer, exhaust-only] (standard = hrv)
special handling of exhaust only ventilation mode (eGO models)
fan controller modes that support a fourth flow rate (either when it can never be shut off, OR the turbo mode when W1 is pressed twice)
LUNOS type RA 15-60 radial duct fan

LUNOS Control4 KMX Module Consistency

Ideally, we would update this integration to follow naming/conventions similar to what LUNOS provides with the the Control4 KMX module (which, btw, may provide an alternative way of integrating LUNOS ventilation with Home Assistant).

Comfort mode (HVAC)
Standby operation (HVAC)
Night operation (HVAC)
Temperature protection mode (HVAC)
Shock ventilation (extended HVAC mode)
Sleep (Off) (extended HVAC mode)
Summer mode (switch object)
Night operation (switch object)

Known Issues

IMPROVEMENT: manual fan speed changes are not immediately detected (only on 30 second interval updates)

anisite / hass-lunos