Limitations
Some features are not available on older versions of the gateway:
- Setpoint Groups and Humidity requires Protocol 2 or 3.
- Floor Temperature sensor requires Protocol 3.
- Slab setpoint is only available as a separate setpoint on Protocol 3 gateways (slab minimum target temperature when both room and floor sensing is configured).
This integration was tested and developed on Gateway 482 firmware version 154 protocol 3. Older gateways may only support protocol 1 or 2. The firmware version and protocol version are shown on the device page in Home Assistant.
Firmware updates are available from Tekmar.
The Gateway 482 does not support changing scenes or setback control (the home/away/sleep thing). It can change setpoints used by different modes, but not a device or network scene change. You can change scenes manually through the User Switch 480 (by pressing the buttons or by using the wired inputs).
It's possible to send unsupported values (such as a temperature setpoint) to the gateway because the gateway doesn't know the actual settings on the thermostats. If this happens, the thermostat will reject the value and the gateway will send a response back to Home Assistant with a value which will be different from the requested one. This isn't a bug, but can be confusing.
Tekmar devices can automatically address and notify of address changes - this is not supported in the integration because the device address is part of the entity unique ID. The integration will need to be reloaded to pick up new devices or address changes.
To avoid this issue you must assign a fixed address for each device instead of using AUTO mode. With the "installer" access level, go to Toolbox -> Address and set the address. You can start with AUTO mode to see what address it chooses then set that address manually.
Because the Gateway 482 does not report serial numbers or any other unique ID that we can use with Home Assistant, according to the entity registry developer documentation we are using the "Unique ID of last resort" which is based on the Config Entry ID. This means if you uninstall and reinstall the integration you will lose all historical data, although the entity names will remain the same. Entity names are based on the device type and device address.
Some devices are slower than others in initializing their network communications. This may cause the "slow" devices to not appear at integration start up time if the Gateway 482 powers on before all network devices have initialized.
One workaround for this behavior is to use a smart plug with the Gateway 482. You can either delay its power on with plugs that support powering up in the "off" state (for example, on a Zooz ZEN15 set parameter 21 to 2, or on a ZEN25 set parameter 1 to 2) then turn on after 30 seconds, or power cycle the Gateway 482 and reload the integration after.