Below you can find some general guidelines on how to configure your ETS project file so that it will work well with voice assistants and cloud smart home apps such as Apple HomeKit, Amazon Alexa and Google Home.

If the ETS file isn’t adapted for the needs of smart assistants, then some devices might not show in the assistant’s mobile apps or not work as intended.

Make sure to configure the required functions for each device type as described below.


Table of contents:


Simple Switch

The Simple Switch device type only supports the functions: ON/OFF.

Required functions:

  • Switching on/off (1 bit, flags: C,W) - turns device on or off.

  • Switching on/off feedback (1 bit, flags: C,R,T) - sends information whether the device is on or off. This is needed by cloud mobile apps in order to show you the current status of the device in the app.

Common issues:

  1. "Switching on/off feedback" function is not configured → Then the cloud apps can't know what the current status of the device is.

  2. "Switching on/off feedback" doesn't have the T (transmit) flag enabled → This means that when the state of the device changes, the cloud app will not know that it changed right away. It will only know when the app requests the state explicitly.


Simple Light

The Simple Light device type works exactly the same as a simple switch, it supports ON and OFF functions. The same functions are required and the same rules and issues apply, see above.

The simple light will be detected as a simple switch. You can change the type to simple light in the 1Home Dashboard under Devices tab.

NOTE: If your light can be dimmed, use Dimming Light device type instead.


Dimming Light

The Dimming Light device type supports the functions: ON/OFF & can be dimmed to a specific brightness percentage.

Required functions:

  • Switching on/off (1 bit, flags: C,W) - turns device on or off.

  • Switching on/off feedback (1 bit, flags: C,R,T) - sends information whether the device is on or off. This is needed by cloud mobile apps in order to show you the current status of the device in the app.

  • Brightness value (1 byte, flags: C,W) - commands the light to turn on to a specific percentage (eg. to 70%). All cloud apps use this function to set the brightness percentage of the light.

  • Brightness value feedback (1 byte, flags: C,R,T) - sends information on the current brightness percentage of the light. This is needed by cloud apps to display the correct brightness percentage in the app.

Common issues:

  1. IMPORTANT: Most common problem. KNX integrator only configured "Dimming function (4 bit)" which changes brightness relatively and didn't configure "Brightness value (1 byte)" that sets light to a specific brightness percentage. This makes sense when you only dim your lights with wall push buttons, but cloud apps don't use relative dimming, only absolute!

  2. "Switching on/off feedback" function is not configured → Then the cloud apps can't know if the light is turned on or off.

  3. "Brightness value" function is not configured → Cloud apps can't set the light to a specific percentage.

  4. "Switching on/off feedback" doesn't have the T (transmit) flag enabled --> This means that cloud apps will not know when the light turns on or off and will only know when they specifically request the status.

  5. "Brightness value feedback" function is not configured → Cloud apps can't know what the current brightness percentage of the light is.

  6. "Brightness value feedback" doesn't have the T (transmit) flag enabled → This means that cloud apps will not know when the brightness percentage changes and will only know when they explicitly request the status.


Simple Blind

The Simple Blind device type supports the functions: fully open or fully close.

NOTE: Use Adjustable Blind if possible.

Required functions:

  • Up/down (1 bit, flags: C,W) - fully opens or fully closes the blinds.

  • (Alternatively, Up and Down can also be represented as two different functions.)

Common problem:

  • If possible, try using Adjustable Blind type over the Simple Blind. Simple blind can only be fully closed or opened, but it can't show what the current state of the blind is. It also lacks many other important blind functionalities like setting a specific position of the blind.


Adjustable Blind

The Adjustable Blind device type supports the functions: fully open, fully closed & set percentage. If configured, you can also control the slats (currently available only with Apple HomeKit).

Required functions:

  • Up/down (1 bit, flags: C,W) - fully opens or fully closes the blinds.

  • Step/stop (1 bit, flags: C,W) - stops the blind from moving.

  • Absolute position (1 byte, flags: C,W) - sets the blind to a specific position measured in percentages.

  • Current position status (1 byte, flags: C,R,T) - sends information on the current position of the blind. With this cloud apps can show the correct position of the blind in the app.

Optional functions:

  • Absolute position of the slats (1 byte, flags: C,W) - sets the slats to a specific position.

  • Current position status of the slats (1 byte, flags: C,R,T) - sends information on the current position of the slats.

Common problems:

  1. No "Absolute position" function is configured → The blind is detected as a Simple blind instead of an Adjustable blind.

  2. No "Current position status" function is configured → the cloud apps can't know and display the correct current position of the blind.

  3. "Current position status" does not have a T (transmit) flag enabled → This means that when the position of a blind changes (eg. via push button), the cloud app will not get notified about the change and it will display a wrong position of the blind.

  4. If slats are controllable, the same applies as with "Current position status" to "Current position of the slats status". Make sure that this function is configured and that the T (transmit) flag is enabled.


Thermostat

The Thermostat reads the temperature in the room and controls heating devices based on the desired temperature and heating mode.

Required functions:

  • Current temperature (2 bytes, flags: C,R,T) - sends information on the current temperature.

  • Temperature setpoint (2 bytes, flags: C,W) - sets the desired temperature.

  • Temperature current setpoint (2 bytes, flags: C,R,T) - tells what is the current desired temperature.

Optional functions:

  • Heating/cooling setting (1 bit, flags: C,W) - changes between heating and cooling mode (heating = 1, cooling = 0). If you need a 1 byte mode setting that supports auto, heating and cooling options, you can configure it in the 1Home Dashboard.

  • Heating/cooling setting status (1 bit, flags: C,R,T) - tells whether the current setting is set to heating or cooling.

  • NOTE: Additional functions that might still be configured in the 1Home dashboard are not automatically recognized. To see what are other options, head to my.1home.io -> Devices -> Green plus button (top-right corner) -> Add KNX device -> select KNX device type Thermostat.


Air Conditioning

The Air Conditioning device type supports:controlling the temperature, fans, swing modes and heating/cooling modes.

Required functions:

  • Switch on/off (1 bit, flags: C,W) - turns AC on or off.

  • Switch on/off status (1 bit, flags: C,R,T) - tells if the AC is on or off.

  • Current temperature (2 bytes, flags: C,R,T) - sends information on the current temperature.

  • Temperature setpoint (2 bytes, flags: C,W) - sets the desired temperature.

  • Temperature current setpoint (2 bytes, flags: C,R,T) - sends information on the current desired temperature.

Optional functions:

  • Heating/cooling setting (1 bit, flags: C,W) - changes between heating and cooling mode (heating = 1, cooling = 0). If you need a 1 byte mode setting that supports auto, heating and cooling options, you can configure it in the 1Home Dashboard.

  • Heating/cooling setting status (1 bit, flags: C,R,T) - sends information on whether the current setting is set to heating or cooling.

  • NOTE: Additional functions such as "fan speed", "swing mode" and more complex changing between heating, cooling and automatic modes can be configured in the 1Home Dashboard, but are not automatically detected. To see what the other options are, head to my.1home.io -> Devices -> Green plus button (top-right corner) -> Add KNX device -> select KNX device type Air Conditioning.


RGB Light

To control the RGB Light device type, you need to configure functions for: red, green and blue lights.

Required functions:

  • Switch on/off (1 bit, flags: C,W) - turns RGB light on or off.

  • Switch on/off status (1 bit, flags: C,R,T) - sends information whether the RGB light is on or off.

  • RED brightness value (1 byte, flags: C,W) - tells the red light to turn on to a specific percentage.

  • RED brightness value feedback (1 byte, flags: C,R,T) - sends information on the current brightness percentage of the red light.

  • GREEN brightness value (1 byte, flags: C,W) - tells the green light to turn on to a specific percentage.

  • GREEN brightness value feedback (1 byte, flags: C,R,T) - can tell what is the current brightness percentage of the green light.

  • BLUE brightness value (1 byte, flags: C,W) - tells the blue light to turn on to a specific percentage.

  • BLUE brightness value feedback (1 byte, flags: C,R,T) - sends information on the current brightness percentage of the blue light.

Common issues:

  1. Lights for specific colors don't have the 1 byte "brightness value" configured but instead a 4 bit "relative dimming value" configured. Make sure that the "brightness value" that sets the brightness percentage of the light to a specific position is configured.

  2. "brightness value feedback" for lights is not set → Then the cloud apps can't show the correct current status of the light.

  3. "brightness value feedback" for lights doesn’t have a T (transmit) flag enabled → Thus the cloud apps are not notified about the change of the light if that is not triggered from the app itself.

  4. Sometimes "brightness value" functions for different colors are mixed up among themselves. Make sure that the function for correct color is correctly set up in the Dashboard.


HSV Light

To control the HSV Light device type, you need to configure functions for: hue, saturation and value of the light.

Required functions:

  • Switch on/off (1 bit, flags: C,W) - turns HSV light on or off.

  • Switch on/off status (1 bit, flags: C,R,T) - sends information whether the HSV light is on or off.

  • Hue brightness value (1 byte, flags: C,W) - sets the hue of the light to a specific percentage.

  • Hue brightness value feedback (1 byte, flags: C,R,T) - can tell what is the current percentage of hue.

  • Saturation value (1 byte, flags: C,W) - sets the saturation of the light to a specific percentage.

  • Saturation value feedback (1 byte, flags: C,R,T) - can tell what is the current percentage of saturation.

  • HSV value value (1 byte, flags: C,W) - sets the HSV value of the light to a specific percentage.

  • HSV value value feedback (1 byte, flags: C,R,T) - can tell what is the current percentage of HSV value.

Common issues:

  1. Functions for specific settings don't have the 1 byte "value" configured but instead a 4 bit "relative value" configured. Make sure that the "value" that sets a specific brightness, saturation or value percentage is configured.

  2. "value feedback" for a setting (hue, saturation, value) is not set → Thus the cloud apps can't show the correct current status of the light.

  3. "value feedback" for a setting (hue, saturation, value) does not have T (transmit) flag enabled → Thus the cloud apps are not notified about the change of the light if that is not triggered from the app itself.

  4. Sometimes "value" functions for different settings (hue, saturation, value) are mixed up among themselves.


Sensors

Below is the suggested configuration of Sensor device type for the optimal detection in 1Home Dashboard.

  • Motion sensor - (1 bit, DPT: 1.001)

  • Occupancy sensor - (1 bit, DPT: 1.018)

  • Contact sensor - (1 bit, DPT: 1.019)

  • Humidity sensor - (2 bytes, DPT: 9.007)

  • CO2 sensor - (2 bytes, DPT: 9.008)

  • Temperature sensor - (2 bytes, DPT: 9.001 or DPT: 9.027)

  • Light sensor - (2 bytes, DPT: 9.004)


Do you have any questions or suggestions?

Our support team is happy to help via Chat (blue button in the bottom right corner).

Did this answer your question?