< Back to the Table of Contents


Below you can find general guidelines on how to correctly control your KNX installation with voice assistants and cloud smart home apps such as Apple HomeKit, Amazon Alexa and Google Home.

While most KNX devices should be automatically detected by our detection algorithm and work out of the box, it is still sometimes needed to adjust certain devices in your ETS file in order to have them work properly with smart assistant platforms.

To see all of the supported KNX devices for different smart assistants, go here.


Table of contents:


Introduction

After uploading your ETS project file, the devices will be automatically detected and imported into the Devices tab. Sorted by their corresponding rooms, each device will be presented with its name, device type and properties (on/off, status, set percentage …).

If this is your first time setting up your KNX home with smart assistants and your installer didn’t set up all the required functionalities, then some device adaptations might be needed. Below are in-depth instructions for each device type.

The devices in Apple HomeKit, Amazon Alexa and Google Home are linked to KNX via group addresses and imported as one of the predefined device types (e.g. adjustable blind, switch, RGB light, …). The device type can be changed at any time in the 1Home Dashboard, see how.

The name of a device should be carefully considered as it’s used in voice commands to Siri, Alexa or Google Assistant. A device name that is difficult to pronounce or contains numbers should be avoided. See device naming guideline with examples.

Here is an example of how a lamp named “Ceiling light” is displayed in the “Kitchen” room in the Apple Home app:


Simple Switch

The Simple Switch is used for setting any device ON or OFF. Feel free to use it for anything that requires only the on/off switching and make it smart (e.g. dishwasher, coffee machine, ….).

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) - current status of the device to show in the mobile app or query via voice.

Additional settings:

  • If you have two separate addresses for turning the switch on and off, toggle it to “Two addresses” and enter both addresses.

  • If needed, change the device name, room or device type. This will be imported in the assistant mobile app.

Common issues:

  1. Voice command for on turns the device off → Select “invert commands” in device settings to invert the command that we send on the bus for turning the device on/off.

  2. Missing the checkbox on “Read status enabled” → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  3. "Switching on/off feedback" function is not configured in ETS → the mobile app can't know what the current status of the device is. Apple Home app won’t show the device at all.

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

  5. "Switching on/off feedback" doesn't have the R (read) flag enabled in ETS →The mobile app can’t query the state of the switch. This may result in the wrong state of the switch in the mobile app."


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.

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

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. Simply change the “KNX Device type” drop-down value to “Simple light”.

See the Simple Switch section to see how to properly configure a simple light.


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 the light on or off.

  • Switching on/off feedback (1 bit, flags: C,R,T) - current status of the light to show in the mobile app or query via voice.

  • Brightness value (1 byte, flags: C,W) - sets the brightness to a specific percentage (eg. to 70%).

  • Brightness value feedback (1 byte, flags: C,R,T) - listens to the status of the current brightness percentage of the light.

Additional settings:

  • If needed, change the device name, room or device type. This will be imported in the assistant mobile 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 mobile apps don't use relative dimming, only absolute!

  2. Missing Switching on/off feedback address → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  3. Missing the checkbox on “Read status enabled” → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  4. "Brightness value" function not configured → the mobile app can’t set the light to a specific percentage.

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

  6. "Brightness value feedback" function not configured → the mobile app can't show the current brightness percentage of the device. Apple Home app won’t show the device at all.

  7. "Brightness value feedback" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the brightness percentage has changed and will only show it when you explicitly request the status.

  8. "Switching on/off feedback" doesn't have the R (read) flag enabled in ETS → The mobile app can’t query the state of the light. This may result in the wrong state of the light in the mobile app.


RGB Light

NOTE: RGB lights can’t currently be imported in Google.

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

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) - current status of the light to show in the mobile app or query via voice.

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

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

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

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

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

  • BLUE brightness value feedback (1 byte, flags: C,R,T) - current status of the 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 → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  3. Missing the checkbox on “Read status enabled” → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  4. "Brightness value feedback" function not configured → the mobile app can't show the current brightness percentage of the device. Apple Home app won’t show the device at all.

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

  6. "Switching on/off feedback" doesn't have the R (read) flag enabled in ETS → The mobile app can’t query the state of the switch. This may result in the wrong state of the switch in the mobile app.

  7. 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) - current status of the light to show in the mobile app or query via voice.

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

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

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

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

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

  • HSV value value feedback (1 byte, flags: C,R,T) - current status of the 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 mobile 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 mobile 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.


Color Temperature Light

Color temperature light sets the light temperature (in K) to the desired value between cold/white or warm/yellow light or sets its brightness.

Required functions:

  • Switching on/off (1 bit, flags: C,W): turns the color temperature light on or off.

  • Switching on/off feedback (1 bit, flags: C,R,T): current status of the light to show in the mobile app or query via voice.

  • Color temperature value (2 byte, flags: C,W): sets the light color temperature to a desired value (in K).

  • Color temperature value feedback(2 byte, flags: C,R,T): current status of the color temperature.

  • Brightness value (1 byte, flags: C,W): sets the brightness to a specific percentage (eg. to 70%) to show in the mobile app.

  • Brightness value feedback (1 byte, flags: C,R,T): current status of the brightness percentage of the light to display it in the mobile app or query via voice.

Common issues:

  • "brightness value feedback" for lights is not set → the mobile app can't show the current status. Apple Home app won’t show the device at all.

  • Missing the checkbox on “Read status enabled” → the mobile app can't show the current status of the device. Apple Home app won’t show the device at all.

  • "Brightness value feedback" function not configured → the mobile app can't show the current brightness percentage of the device. Apple Home app won’t show the device at all.

  • "Brightness value feedback" doesn't have the T (transmit) flag enabled in ETS → When the brightness of the light changes, the mobile app will not know that it changed right away. It will only know when the app requests the state explicitly.

  • "Brightness value feedback" doesn't have the R (read) flag enabled in ETS → The mobile app can’t query the state of the light. This may result in the wrong state of the light in the mobile app.

  • "Color temperature value feedback" is not set → the mobile app can't show the current status of the color temperature.

  • "Color temperature value feedback" does not have the T (transmit) flag enabled → When the color temperature of the device changes, the mobile app will not know that it changed right away. It will only know when the app requests the state explicitly.

  • "Color temperature value feedback" does not have the R (read) flag enabled → The mobile app can’t query the state of the light. This may result in the wrong state of the light in the mobile app.


Simple Blind

Use the Blinds device type for any window coverings: blinds, shades, curtains, sun screens, …

NOTE 1: Use Adjustable Blind if possible. Compared to a Simple Blind, an Adjustable Blind can be also set to a specific position (eg. 30%) and is able to control the tilt of the slats.

NOTE 2: In the Google Home ecosystem, blinds can only be controlled with voice command with Google Assistant, it isn’t shown in their mobile app.

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

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 the 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) - listens to the status of the current position of the blind and displays it in the mobile 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) - listens to the status of 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 mobile 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) - current temperature status to show in the mobile app or query via voice.

  • 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.


Fan

NOTE: Fans can’t be imported into Google Home and Alexa and only work with Apple HomeKit. You can however always import them as a Simple Switch device to turn it on and off.

Fan can be turned on/off and you can also set the speed of a fan (in %). Additionally you can add addresses for swing mode if your fan supports it.

Required functions:

  • Switch on/off (1 bit, flags: C,W): turns the fan on/off.

  • Switch on/off status (1 bit, flags: C,R,T): listens to the status of the Fan to show in the mobile app.

  • Fan speed (1 Byte, flags: C,W): sets the fan to desired speed (in %).

  • Fan speed feedback (1 Byte, flags: C,R,T): listens to the status of the Fan speed to show in the mobile app (in %).

Optional functions:

  • Swing mode (1 bit, flags: C,W): sets the swing mode on/off.

  • Swing mode feedback (1 bit, flags: C,R,T): listens to the status of the swing mode to show in the mobile app.


Garage Door

Required functions:

  • (Pulse enabled) - Switching on/off (1 bit, flags: C,W): opens or closes garage doors by sending an ON signal and then after a few seconds an OFF signal.

OR

  • (Toggle enabled) - Toggle on/off (1 bit, flags: C,W) : opens or closes garage doors by sending either ON or OFF signal.

  • (Toggle enabled) - Switching on/off feedback (1 bit, flags: C,R,T): reads current status of the garage door to show in the mobile app or query via voice.


Push Button

Push buttons allow you to control your Apple HomeKit devices or device groups with physical KNX switches.

Required functions:

  • Short press address (1 bit, flags: C,T): address that you want to trigger with a short press.

Additional settings:

  • Long press address (1 bit, flags: C,T): address that you want to trigger with a long press.

  • Double press address (1 bit, flags: C,T): address that you want to trigger with a double press.


Speaker

NOTE: Speakers are only supported in Alexa (mute/unmute and volume control) and Google Home (volume control).

Required functions:

  • Set mute (1 bit, flags: C,W): mutes/unmutes the speaker.

  • Mute feedback (1 bit, flags: C,R,T): tells if the speaker is muted or not.

  • Set volume (1 bytes, flags: C,W, DPT: 5.001): sets the volume to a specific value.

  • Volume feedback (1 bytes, flags: C,R,T, DPT: 5.001): sends information on the current volume value.


KNX Scene

This device is used to control your KNX Scenes.

Required functions:

  • Scene activate address (1 bit, flags: C,W, DPT: 17.001 or 18.001) - address for activating the scene.

  • Scene number (integer) - scene number.


Temperature Sensor

The Temperature Sensor is used to display the temperature in mobile apps.

NOTE: If you can also control the temperature with the device, please use a Thermostat instead of a Temperature Sensor.

Required functions:

  • Current temperature address (2 bytes, flags: C,R,T, DPT: 9.001 or DPT: 9.027): sends information on the current temperature.

Common issues:

  • "Current temperature address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the current temperature has changed and will only show it when you explicitly request the status.f

  • "Current temperature address" doesn't have the R (read) flag enabled → The mobile app can’t query the current temperature. This may result in the wrong current temperature in the mobile app.


Humidity Sensor

Humidity sensor is used to get and display the humidity in mobile apps

You can set the address that sends information of the humidity sensor in % or values.

NOTE: humidity sensor is currently not available on Alexa.

Required functions:

  • Humidity address(2 bytes, flags: C,R,T, DPT: 5.001) - sends information on the current humidity in percentages.

OR

  • Humidity address value(2 bytes, flags: C,R,T, DPT: 9.007): sends information of the current humidity value.

Common issues:

  • "Humidity address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the humidity percentage (or. value) has changed and will only show it when you explicitly request the status.

  • "Humidity address" doesn't have the R (read) flag enabled→ The mobile app can’t query the current humidity. This may result in the wrong humidity value in the mobile app.


CO2 Sensor

A CO2 sensor is used to display the amount of CO2 in a room in mobile apps.

When configuring CO2 detection you can receive notifications in HomeKit when the levels are abnormal. By tying an automation to it, you can then let your ventilation automatically turn on.

NOTE: CO2 sensor is currently only available in Apple HomeKit.

Required functions:

  • CO2 address (2 bytes, flags: C,R,T, DPT: 9.008): sends information on the amount of CO2 in a room in ppm.

Common issues:

  • "CO2 address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the CO2 value has changed and will only show it when you explicitly request the status.

  • "CO2 address" doesn't have the R (read) flag enabled→ The mobile app can’t query the current CO2 value. This may result in the wrong CO2 value in the mobile app.


CO Sensor

A CO sensor is used to display the amount of CO in a room in mobile apps.

Required functions:

  • CO address (2 bytes, flags: C,R,T, DPT: 9.008): sends information on the amount of CO in a room in ppm

Common issues:

  • "CO address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the CO value has changed and will only show it when you explicitly request the status.

  • "CO address" doesn't have the R (read) flag enabled → The mobile app can’t query the current CO value. This may result in the wrong CO value in the mobile app.


Room Sensor

The Room sensor combines the functionalities of Temperature, Humidity and CO2 Sensor. It sends information of all three values to the mobile app.

Required functions:

  • Current temperature address(2 bytes, flags: C,R,T, DPT: 9.001 or DPT: 9.027): sends information on the current temperature.

  • Humidity address value(2 bytes, flags: C,R,T, DPT: 9.007): sends information of the current humidity value.

  • CO2 address (2 bytes, flags: C,R,T, DPT: 9.008): sends information on the amount of CO2 in a room in ppm.


Contact Sensor

Contact Sensor sends information whether something is opened or closed (i.e. window, door).

When configuring Contact Sensor you can receive notifications in HomeKit when it's triggered. By tying an automation to it, you can then let your lights automatically turn on when the contact sensor is triggered or simply receive a mobile push notification.

Required functions:

  • Contact address (1 bit, flags: C,R,T, DPT: 1.019): sends the information on whether the i.e. window is opened or closed.

Common issues:

  • "Contact address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the state of contact sensor has changed and will only show it when you explicitly request the status.

  • "Contact address" doesn't have the R (read) flag enabled → The mobile app can’t query the state of contact sensor. This may result in the wrong contact sensor state in the mobile app.


Light Sensor

NOTE: Light sensor is currently only available in Apple HomeKit..

Light Sensor displays the light level in mobile apps. The light level is displayed in lux.

Required functions:

  • Brightness address (2 bytes, flags: C,R,T, DPT: 9.004): sends information on the current brightness in lux.

Common issues:

  • "Brightness address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the brightness has changed and will only show it when you explicitly request the status.

  • "Brightness address" doesn't have the R (read) flag enabled → The mobile app can’t query the current brightness. This may result in the wrong brightness value in the mobile app.


Motion Sensor

The Motion Sensor detects motion in a room.

When configuring Motion Sensor you can receive notifications in HomeKit when it's triggered. By tying an automation to it, you can then let your lights automatically turn on when the motion sensor is triggered.

NOTE: Motion sensor is currently not available on Google.

Required functions:

  • Motion address (1 bit, flags: C,R,T, DPT: 1.001): sends information if the movement is detected

Common issues:

  • "Motion address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the state of motion sensor has changed and will only show it when you explicitly request the status.

  • "Motion address" doesn't have the R (read) flag enabled→ The mobile app can’t query the state of the motion sensor. This may result in the wrong motion sensor state in the mobile app.


Occupancy Sensor

The Occupancy Sensor detects presence in a room.

When configuring Occupancy Sensor you can receive notifications in HomeKit when it's triggered. By tying an automation to it, you can then let your lights automatically turn off when the occupancy sensor hasn’t been triggered in a while.

NOTE: Occupancy sensor is currently not available on Google. You can use it on Alexa as a motion sensor.

Required functions:

  • Occupancy address (1 bit, flags: C,R,T, DPT: 1.018): sends information whether someone is present in the room.


Smoke Sensor

The Smoke Sensor quickly detects and alerts you in case of fire or smoke.

When configuring Smoke Sensor you can receive notifications in HomeKit when the sensor detects smoke. By tying an automation to it, you can then let all your lights automatically turn on in case of fire.

NOTE: Smoke sensor is currently only available in Apple HomeKit..

Required functions:

  • Smoke detected address (1 bit, flags: C,R,T, DPT: 1.001): sends information if the smoke is detected.

Common issues:

  • "Smoke detected address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the smoke is detected and will only show it when you explicitly request the status.

  • "Smoke detected address" doesn't have the R (read) flag enabled → The mobile app can’t query the state of the smoke sensor. This may result in the wrong smoke sensor state in the mobile app.


Leak Sensor

The Leak Sensor detects if there is a water leakage. When a leak is detected, quick action can be taken to limit the damage.

When configuring Leak Sensor you can receive notifications in HomeKit when the sensor detects a leakage. By tying an automation to it, you can then automatically turn off power or close a valve.

NOTE: Smoke sensor is currently not available on Alexa and Google.

Required functions:

  • Leak detected address (1 bit, flags: C,R,T, DPT: 1.001): sends information if the leak is detected.

Common issues:

  • "Leak detected address" doesn't have the T (transmit) flag enabled → The mobile app can’t show when the leak is detected and will only show it when you explicitly request the status.

  • "Leak detected address" doesn't have the R (read) flag enabled → The mobile app can’t query the state of the leak sensor. This may result in the wrong leak sensor state in the mobile app.


Do you have any questions or suggestions?

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


< Back to the Table of Contents

Did this answer your question?