Retour

Known limitations

The following devices work with Versatile Thermostat, but with limitations. Some features will not work, or the regulation will not be as good as with a fully compatible device.

All these devices are installed with the over_climate type: the installation steps are given below on this page.

Air conditioners and heat pumps

  1. Sensibo: after an off command, a fan mode command can switch the air conditioner back on. Some units also turn off on their own.
  2. LG ThinQ: the cloud integration rejects some commands (target_temperature_low), and regulation cycles are lost when the cloud is unavailable.
  3. Gree: with auto-start/stop, the auto-stop does not send off to the air conditioner.
  4. Airzone Aidoo: the eco mode of the Airzone app forces 18 °C or off: disable it. After an auto-stop, a heating request can turn the unit on without VTherm sending off afterwards.
  5. Panasonic Comfort Cloud: the fan modes use capital letters, so the automatic fan mode of VTherm does not work. The internal sensor of the unit is unstable: use a room sensor.
  6. Mitsubishi Heavy Industries WF-RAC: keep the integration up to date, older versions turned the unit off right after start. The Wi-Fi module restarts regularly and is unavailable for about 30 seconds.
  7. Atlantic Naviclim (GW003-AS-IN-TE-FC): auto-start works in heating mode, but cooling regulation is slow.

Thermostats and heating systems

  1. Homematic thermostats (and possibly Homematic IP) are known to have issues with Versatile Thermostat due to the limitations of the underlying RF protocol. This problem particularly arises when trying to control multiple Homematic thermostats at once in a single VTherm instance. To reduce service cycle load, you can, for example, group thermostats using Homematic-specific procedures (e.g., using a wall-mounted thermostat) and let Versatile Thermostat control only the wall-mounted thermostat directly. Another option is to control a single thermostat and propagate mode and temperature changes via automation.
  2. Rointe type thermostats tend to wake up on their own. The rest works normally.
  3. Heating systems based on Netatmo perform poorly. Netatmo schedules conflict with VTherm programming. Netatmo devices constantly revert to Auto mode, which is poorly managed with VTherm. In this mode, VTherm cannot determine whether the system is heating or cooling, making it impossible to select the correct algorithm. Some users have managed to make it work using a virtual switch between VTherm and the underlying system, but stability is not guaranteed. An example is provided in the troubleshooting section.
  4. ecobee: check the temperature unit. A mix between °F and °C can pin the setpoint to the minimum value of the thermostat.

Device 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