Climate

Velair

cgonfer/velair · vv1.8.0

HACSLocal push

Climate automation that adapts to your life.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`switch`	Switch or outlet
`sensor`	Sensor (temperature, humidity, air quality…)
`select`	Mode picker (as switches)

What people report

Velair schedules climate entities; works with Daikin Onecta and, after a fix, local Daikin; tado Matter radiator groups requested.

Works2
Requested1

Device	In Home Assistant	What they said	Source
Daikin air conditioner (local integration)	Works Local	Target temperature now delivered reliably after 1.6.0 fix Saved copy Home Assistant version 2026.7.4 ### Velair version 4.6.15 ### Installation method HACS ### What happened? I'm using Velair v1.5.0 with several Daikin air conditioners in Home Assistant. Some units are connected through the Daikin Onecta integration, while others use the local Daikin AC integration. With the Onecta units, Velair works correctly. With the local Daikin units, HVAC mode and fan mode are applied correctly, but the target temperature is not. For example: climate.daikin_woonkamer Attributes: hvac_modes: fan_only, dry, cool, heat, heat_cool, off min_temp: 7 max_temp: 35 … Excerpt saved from GitHub on 2026-10-23.	Issue #11 · 2026-08
Daikin air conditioner (Onecta)	Works Cloud	Works correctly with Velair Saved copy Home Assistant version 2026.7.4 ### Velair version 4.6.15 ### Installation method HACS ### What happened? I'm using Velair v1.5.0 with several Daikin air conditioners in Home Assistant. Some units are connected through the Daikin Onecta integration, while others use the local Daikin AC integration. With the Onecta units, Velair works correctly. With the local Daikin units, HVAC mode and fan mode are applied correctly, but the target temperature is not. For example: climate.daikin_woonkamer Attributes: hvac_modes: fan_only, dry, cool, heat, heat_cool, off min_temp: 7 max_temp: 35 … Excerpt saved from GitHub on 2026-10-23.	Issue #11 · 2026-08
tado Smart Radiator Thermostat X via Matter	Requested Local	Room groups requested to share one schedule across heads and sensor Saved copy Use case In one room I have several climate entities exposed by the same heating system: tado X via Matter, with 3 Smart Radiator Thermostat X heads plus 1 Wireless Temperature Sensor X (which also shows up as a `climate` entity). tado passes a setpoint sent to the room sensor on to the heads in that room within a few seconds. If I manage all 4 entities in Velair, each one gets its own schedule and its own Adaptive Preconditioning start time. They then compete by sending different setpoints to the same room. Today my workaround is to manage only the room sensor in Velair and remove the heads, … Excerpt saved from GitHub on 2026-10-23.	Issue #55 · 2026-10

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local push

Talks to the device on your network, and the device tells Home Assistant the moment something changes.

Details

Installs (analytics)	126 (0.02%)
GitHub stars	109
Latest version	v1.8.0 (2026-10-21)
Set up in the UI	Yes
Maintainers	@cgonfer
License	MIT

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.

Sources

Documentation: https://github.com/cgonfer/velair
Source code: https://github.com/cgonfer/velair
Issues: https://github.com/cgonfer/velair/issues
HACS: https://hacs.xyz