# Daikin

Daikin air conditioners and heat pumps work with the `over_climate` type, but the result depends a lot on the Home Assistant integration.

## Choosing the integration

1. **Daikin AC (local)**: the core integration talks directly to the Wi-Fi adapter on the local network. Commands are applied immediately. This is the best choice when your adapter supports it.
2. **Daikin Onecta (cloud)**: commands go through the Daikin cloud. They are slow, and the daily API quota can be used up within a few hours because _VTherm_ sends commands often. When the integration becomes unavailable, the _VTherm_ state can be lost.
3. **BRP069B4x adapters**: with the core integration, some users see the air conditioner turn off right after _VTherm_ starts it. The HACS Daikin integration works with these adapters.

## Recommendations

- Avoid sending on/off commands too close together: the unit can drop them.
- With the cloud integration, prefer a light self-regulation to limit the number of commands.

> [!NOTE]
> Because of these limitations, Daikin devices are partially compatible.

## Compatibility status

- **Partial**: This device is supported by Versatile Thermostat, but some advanced features may not be supported. Devices: Daikin

## VTherm configuration

### Initialization

Go to your settings, then integrations, then click on add a new integration. Search for Versatile Thermostat.

Click on Thermostat over another thermostat.

### Basic attributes

Go to the "Main attributes" section.

1. Choose a name for your thermostat
2. Set the temperature sensor for your room
3. If you are using the Zigbee protocol and you have a "last_seen" entity for your temperature sensor, fill it in.

You can validate and return to the configuration menu.

### Underlying entities

Go to the underlying entities section.

1. Add the thermostats that will be controlled

You can validate and return to the configuration menu.

## Community references

Additional references may be old. A bug reported on an old version of VTherm may have been corrected on a more recent version.

- [#1844 V9.1.0 BUG - Infinite State Change Loop on Daikin Over-Climate (HA 2026.3.1)](https://github.com/jmcollin78/versatile_thermostat/issues/1844)
- [#1458 Recalling presets is broken since v8.3 for over_climate (Daikin AC)](https://github.com/jmcollin78/versatile_thermostat/issues/1458)
- [#1153 Thermostat turning off instantly with AC Unit](https://github.com/jmcollin78/versatile_thermostat/issues/1153)
- [#702 Integration Crash After Kernel Upgrade to 2024.12.0 - AttributeError in Versatile Thermostat Component](https://github.com/jmcollin78/versatile_thermostat/issues/702)
- [#781 self regulation issue with the managemen of Open Window sensor status](https://github.com/jmcollin78/versatile_thermostat/issues/781)
- [#1987 Incorrect state restoration on window close with over.climate](https://github.com/jmcollin78/versatile_thermostat/issues/1987)
- [Discussion #1060 Frequent & rapid changes to setpoint of underlying climate entity](https://github.com/jmcollin78/versatile_thermostat/discussions/1060)
- [Discussion #1944 Replicate physical thermostat to a VTherm](https://github.com/jmcollin78/versatile_thermostat/discussions/1944)
- [Discussion #743 2 VTHERM with the same external temperature sensor : one is outdated !](https://github.com/jmcollin78/versatile_thermostat/discussions/743)