Helty Flow Cloud is a new Home Assistant integration for Helty Flow decentralized heat-recovery ventilation units that use the recent control panel, the one set up through the Helty Home app. The integration was merged into the development branch on 19 October 2026, and its documentation names 2026.11 as the first release. On 24 October two more pull requests from the same author, Ermanno Baschiera, added sensors and a filter alarm, so the first public version will do more than change fan speeds.
Why Helty now has two integrations
Home Assistant already has helty, which talks to the older panels over the local network. The new panels don't listen on any port. They hold an outbound connection to Helty's cloud, and that is the only way to reach them. So helty_cloud signs in with the email and password of the Helty Home account and needs a working internet connection. Owners of the older panels keep the local integration, which also works offline.
The documentation lists FlowPLUS, FlowULTRA, Flow40, Flow120 and FlowMANHATTAN. Only a FlowPLUS was tested; the other models use the same panel and are expected to work. Every unit on the account becomes a separate device.
What it exposes
- A fan entity with four speeds (25, 50, 75 and 100%) and three presets: Boost, Night and Free cooling. Turning it on without choosing a speed always starts at speed 1, not the last one used.
- Indoor temperature, outdoor temperature and indoor humidity.
- Air treated by filter, in cubic metres. Helty units don't count filter hours. They count the air that has passed through the filter since the last change and raise the alarm at 90,000 m³ with current firmware. Resetting the filter drops the value to zero.
- Total air treated, a lifetime counter that is disabled by default.
- A Filter binary sensor that follows the unit's own alarm bit, so Home Assistant isn't estimating anything.
The pending sensor documentation shows a sensible use for the counter: a numeric state trigger at 85,000 m³ that sends a reminder, leaving time to order a filter before the alarm goes off.
The catches
Home Assistant polls the cloud every 5 minutes, at the manufacturer's request, and reads the last report the panel pushed. A change made at the panel or in the app shows up within a few minutes. After a command sent from Home Assistant the integration asks the panel to report straight away, so a new speed appears in seconds.
If the panel hasn't reported for 2 hours, the entities go unavailable. Without internet the unit keeps ventilating and still obeys its own panel, but Home Assistant can't control it. The panel also can't report whether Auto is on, so in Auto you only see the speed the unit picked. The optional CO₂ and VOC probes aren't exposed yet, because they read zero when not fitted and need to be created conditionally.
The cloud API is undocumented. The author rebuilt it by watching the app's traffic and checked it against written answers from Helty, so it can change without notice.