Manual · for version 1.4.6 · View on GitHub

This manual comes from the public repository of the Home Assistant integration. It still uses the old name OpenThermostat, and calls the box the E32: the BBQKees Gateway E32 V2 that Emthera runs on today.

Devices: what OpenThermostat reads, and how sure we are #

The firmware and the project's main repository are not public at the moment. What these guides say about downloading the firmware or a release ZIP from GitHub, updating the E32's firmware from Home Assistant or with Check for updates, and the tester program's GitHub form does not work for now. The Home Assistant integration is installed and updated through the Marketplace as described. A few references to pages that are not public have no link here. Questions or problems: open an issue.

Nederlands

OpenThermostat works with devices of many brands. This page says which routes work for any device, which devices we have tested and how: verified with a real capture (what a real device sent, kept as a test), or built from the device description, not yet confirmed (made from what Zigbee2MQTT or Home Assistant says the device sends). Every device in the table below is a test that runs on every build, so a change that would stop reading it is caught before a release.

Your device is not in the table, or not read well? Add a device: send a capture. It takes a few minutes, and from then on every build is tested against your device.

Any device, through Home Assistant #

These routes do not depend on the brand:

• Radiator valve: any valve Home Assistant knows as a climate entity (ZHA, Z-Wave, Zigbee2MQTT, Shelly, a cloud integration). Choose it in the room's form, section Radiator valves; Home Assistant then drives it on the E32's rules. Its target temperature comes from the entity's temperature, or from target_temp_low when the device has only a temperature range. Its battery comes from a battery sensor on the same device, its opening from a position sensor when it has one.
• Setting device (the thermostat or knob you set a room with): any climate, number or input_number entity. A thermostat with only a temperature range (such as the Bosch Room thermostat II) works through its target_temp_low.
• Thermometer: any Home Assistant temperature sensor, or a Bluetooth thermometer the E32 hears itself (pvvx, Shelly H&T, Xiaomi).

Zigbee2MQTT valves the E32 drives itself #

For the valve models it knows (Bosch BTH-RA, Sonoff TRVZB, Sonoff TRV Gen2, Tuya TV02), the E32 talks to Zigbee2MQTT on the same MQTT broker itself, also when Home Assistant is away. For any other Zigbee2MQTT valve choose Other (setpoint only). It reads the common names in this order and uses the first one the valve sends:

• target temperature: occupied_heating_setpoint, then current_heating_setpoint; the E32 writes the target temperature under the name the valve itself uses;
• opening: position, then pi_heating_demand; only shown, the boiler never relies on the opening of a valve the E32 does not know;
• battery: battery (a percentage) and battery_low (a flag);
• mode: system_mode, then preset; only to see that someone switched the valve off, which the E32 then leaves alone.

A message the E32 cannot read (too large, cut off, not a device state) is never dropped silently: the E32's System → Diagnostics and system log page and Home Assistant's Diagnostics tab (Connection with the E32) say "Messages the E32 could not read since it started: 3, last: zigbee2mqtt/…, too large (7.1 KB)". Put that line in your report.

The device matrix #

The table is generated from the test collection (test/fixtures/devices/) by tools/dev/device_matrix.py, so it says exactly what the tests hold.

Radiator valves #

Setting devices #

Thermometers #

Boilers #