aerosmart

The aerosmart integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] lets you monitor a combined aerosmart ventilation and heat-pump installation. Home Assistant connects locally through a Modbus TCP gateway or a directly connected serial Modbus RTU port, without a cloud service.

The integration represents the ventilation controller and heat-pump controller as one device. It provides operating values, filter information, and controller status.

Supported devices

The integration supports an aerosmart installation that exposes the expected register map as two Modbus units on one Modbus connection, reached either over TCP or serial RTU:

• A ventilation controller, typically at unit address 1.
• A heat-pump and hot-water controller, typically at unit address 2.

The register map was derived from one physical installation because no official manufacturer register specification was available. Other installations can use different addresses or return different values.

Prerequisites

• For a network setup, connect the controllers through a gateway that translates their serial Modbus communication to Modbus TCP, and make sure Home Assistant can reach its host and port.
• For a serial setup, connect the aerosmart Modbus bus to a serial port available to Home Assistant.
• Find the Modbus unit address for each controller. The defaults are 1 for ventilation and 2 for the heat pump.

Configuration

To add the aerosmart device to your Home Assistant instance, use this My button:

Supported functionality

The integration provides sensor entities for the complete installation.

Sensors

Sensors report information such as:

• Supply, extract, outdoor, room, heat-pump, and hot-water temperatures.
• Supply and extract fan speeds and airflow values.
• Heat-pump status, pressure inputs, and remaining time in the current state.
• Filter operating hours, service life, and volume values.
• Operating-hour counters and controller information.

Aerosmart automation examples

Use the aerosmart sensors in automations to react to changes in your installation. Create an automation in Settings > Automations & scenes with the trigger and action below.

Automation: Notify when the CO2 level is high

This automation sends a notification when the measured carbon dioxide level rises above 1000 ppm.

• Trigger: Numeric state crossed threshold
  • Entity: Aerosmart CO2 (sensor.aerosmart_co2)
  • Above: 1000
• Action: Send a notification message
  • Target: My Device (notify.my_device)
  • Message: The aerosmart CO2 level is above 1000 ppm.

alias: "Notify when aerosmart CO2 is high"
triggers:
  - trigger: numeric_state
    entity_id: sensor.aerosmart_co2
    above: 1000
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: "The aerosmart CO2 level is above 1000 ppm."

Data updates

The integration pollsData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] operating values and the controller clock every 60 seconds. It polls filter counters and other slow-changing values every 10 minutes.

Requests to both units are serialized because some serial-to-Modbus-TCP gateways need quiet time between requests. If one subsystem does not answer, only its entities become unavailable. Values from subsystems that answered remain available.

During setup, the integration waits for the first update from both controller units. A slow gateway can therefore delay setup for more than 30 seconds. If the initial update fails, Home Assistant retries setup. After setup, the integration polls values on its regular intervals.

Known limitations

• The register map was derived from one physical installation, not from an official manufacturer specification. Entity names and units might not match every aerosmart installation.
• The integration creates one Home Assistant device for the whole installation, even though the ventilation controller and heat-pump controller use separate Modbus units.
• Other Modbus clients can interfere with communication when they share the same gateway or serial bus.
• Each value is read separately because the reference controller rejects larger combined register reads. A complete update can therefore take more than 30 seconds through a slow gateway.

Troubleshooting

Removing the integration

This integration follows standard integration removal.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. Next to the entry you want to remove, select the three dots menu. Then, select Delete.
   • Depending on the integration, the entries are listed under one of the following headings:
     • Devices
     • Hubs
     • Services
     • Integration entries
3. To confirm, select Delete.
   • Home Assistant also deletes the devices and entities of the entry.
4. If Home Assistant asks you to restart, restart Home Assistant.
5. If Home Assistant asks whether to also delete the application credentials, select Remove or Keep.
   • If you keep them, Home Assistant uses them automatically when you add the integration again.
   • To delete them later, refer to Deleting application credentials.

Home Assistant releases its use of the shared Modbus connection when the integration is unloaded.