This integration monitors the inputs and outputs of the devices connected to a C.M.I. from Technische Alternative. It creates a separate (binary) sensor for each input and output which displays the current values.
The data is fetched every 10 minutes.
Currently supported devices:
- UVR1611
- UVR16x2
- RSM610
- CAN-I/O45
- CAN-EZ2
- CAN-MTx2
- CAN-BC2
- UVR65
- CAN-EZ3
- UVR610
- UVR67
Note The loading time of the integration is extended by one minute per configured node on the C.M.I. to avoid triggering the rate limit. The same applies to the setup process
{% if not installed %}
- Click install.
- In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Technische Alternative".
- Start the config flow.
{% endif %}
Note When saving the configuration, there may be a wait time due to the rate limit.
In the first step of the config flow, set up the connection to C.M.I.. To do this, enter the address, user name and password.
In the 2nd step, select the devices from which the data is to be read. For this purpose, a list of all devices and details about them are retrieved at the start of the step. This can take several minutes due to a rate limit of one request per minute. Once the data has been retrieved, select the supported devices from the list. If an error occurs during this query, the devices may be missing from the list. Depending on the type of error, you should try again after a few minutes.
If to configure the channels individually, continue with the next step, otherwise the setup is finished.
In this step, individual channels can be customized, including the following properties:
- Name of the sensor (can also be changed to HA afterward)
- Device class
To customize a channel, select the device, on which the channel is located, enter the channel number and finally select the channel type.
Device type | Inputs | Outputs | DL-inputs | System-values: General | System-values: Date | System-values: Time | System-values: Sun | System-values: Electrical power | Analog network inputs | Digital network inputs | M-Bus | Modbus | KNX | Analog logging | Digital logging |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
UVR1611 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ |
UVR16x2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ✔ |
RSM610 | ✔ | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ❌ | ❌ | ❌ | ❌ |
CAN-I/O45 | ✔ | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
CAN-EZ2 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
CAN-MTx2 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
CAN-BC2 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ✔ | ✔ | ❌ | ❌ |
UVR65 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
CAN-EZ3 | ❌ | ❌ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ❌ | ❌ | ❌ | ✔ | ❌ | ✔ | ✔ |
UVR610 | ✔ | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✔ | ❌ | ❌ | ❌ | ❌ |
UVR67 | ✔ | ✔ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
Note The supported data types may differ from the official API. If a device type supports other data types than listed here, please create an issue.