Parameters for status functions
DALI System... -> Configuration groups -> [x] Group name -> Enabled functions
DALI System... -> Configuration single devices -> [x] Device name -> Enabled functions
Status | Checkbox (yes / no) |
|---|---|
This parameter globally enables the status function for the selected group or single device. When enabled, the "Status" parameter page is visible. | |
DALI System... -> Configuration groups -> [x] Group name -> Status
DALI System... -> Configuration single devices -> [x] Device name -> Status
Cycle time | 0...23 h 0...2...59 min 0/(10)...59 s |
|---|---|
Each status can be transmitted also cyclically in addition to being transmitted when updated. The cycle time is defined uniformly for all status messages of the affected group and single device by this parameter. | |
Parameters for switching status
Switching status | Checkbox (yes / no) |
|---|---|
The gateway can track the current switching state of a group and single device via a separate status object and can also transmit them to the KNX, provided the bus voltage is switched on. Activated: The object "Switching - Status" is enabled. The switching status is transmitted once the status is updated. Deactivated: No switching status is available. | |
Switching status Updating of the object value | After each update "Switching"/"Central" object only if the feedback value changes |
|---|---|
It can be defined here when the gateway updates the feedback value for the switching status. The object value updated last by the gateway is then actively signalled to the KNX, provided the "Transmit" flag is set on the communication object. After each update object "Switching"/"Central switching": The gateway updates the feedback value in the object as soon as a new telegram is received at the input objects "Switching - Setting" or "Central function... - Switching" for groups or single devices are updated. A new telegram is also then actively transmitted to the KNX each time. The telegram value does not necessarily have to change. Consequently, in the event of, for example, cyclical telegrams to the input objects, the corresponding switching status telegrams are also generated. With other functions of the gateway (e.g. at the beginning or end of a disabling or forced position function or in the event of a manual operation or scene recall), no status is sent in this setting if the switching status does not change. Only if the feedback value changes: The gateway updates the switching status only when the telegram value also changes (e.g. "OFF" to "ON"). If the telegram value does not change (e.g. in the case of cyclical telegrams to the input objects with the same telegram value), the status then remains unchanged. Consequently, no telegram with the same content is output repeatedly either. This setting is recommended, for instance, if the objects "Switching - Setting" and "Switching - Status" are linked to an identical group address. This is often the case when activating by means of light scene push-button sensors (recall and storage function). | |
Switching status Delay after bus/mains voltage return | Checkbox (yes / no) |
|---|---|
The switching status can be transmitted to the KNX after the bus or mains voltage returns or after an ETS programming operation, provided the "Transmit" flag is set on the communication object and the reset behaviour of the underlying functions is not configured to "no reaction". In these cases, the status telegram can be transmitted with a time delay, whereby the delay time is set globally for all groups together. Activated: The status is transmitted after a delay after the bus or mains voltage returns or an ETS programming operation. No status is transmitted during a delay even if the state changes during this delay. The delay time is started immediately after the ETS programming operation is completed, i. e. already before the device is initialised (indication of "--" on the display). If the initialisation of the gateway (due to many groups and single devices) takes longer than the delay time configured in the ETS, the status is transmitted only after the initialisation phase has been completed. Deactivated: The status is transmitted immediately after the bus or mains voltage returns or after an ETS programming operation during the device initialisation. | |
Switching status Cyclical transmission | Checkbox (yes / no) |
|---|---|
The switching status can also be transmitted cyclically in addition to being transmitted when updated. Activated: Cyclical transmission is activated. The cycle time is defined uniformly for all status messages of the affected group and single device by the parameter with the same name on the same parameter page. Deactivated: Cyclical transmission is deactivated so that the status is transmitted to the KNX only when a state is updated. | |
Parameters for brightness value status
Brightness value | Checkbox (yes / no) |
|---|---|
The gateway can track the current brightness value of a group or single device via a separate status object and can also transmit them to the KNX, provided the bus voltage is switched on. Activated: The object "Brightness value - Status" is enabled. The brightness value status is transmitted as soon as the status is updated. Deactivated: No brightness value status is available. | |
Brightness value Updating of the object value | after each update "Brightness value"/"Central brightness value" object only if the feedback value changes |
|---|---|
It can be defined here when the gateway updates the feedback value for the brightness value status. The object value updated last by the gateway is then actively signalled to the KNX, provided the "Transmit" flag is set on the communication object. after each update object "Brightness value"/"Central brightness value": The gateway updates the feedback value in the object as soon as a new telegram is received at the input objects "Brightness value - Setting" or "Central function... - Brightness value". A new telegram is also then actively transmitted to the KNX each time. The telegram value does not necessarily have to change. Consequently, the corresponding brightness value status telegrams are also generated, for example, in the event of cyclical telegrams to the input objects. With other functions of the gateway (e.g. at the beginning or end of a disabling or forced position function or in the event of a manual operation or scene recall), no status is sent in this setting if the brightness value status does not change. Only if the feedback value changes: The gateway updates the brightness value status only if the telegram value also changes. If the telegram value does not change (e.g. in the case of cyclical telegrams to the input objects with the same telegram value), the status then remains unchanged. Consequently, no telegram with the same content is output repeatedly either. This setting is recommended, for instance, if the objects "Brightness value - Setting" and "Brightness value - Status" are linked to an identical group address. This is often the case when activating by means of light scene push-button sensors (recall and storage function). | |
Brightness value Delay after bus/mains voltage return | Checkbox (yes / no) |
|---|---|
The brightness value status can be transmitted to the KNX after the bus or mains voltage returns or after an ETS programming operation, provided the "Transmit" flag is set on the communication object and the reset behaviour of the underlying functions is not configured to "no reaction". In these cases, the status telegram can be transmitted with a time delay, whereby the delay time is set globally for all groups together. Activated: The status is transmitted after a delay after the bus or mains voltage returns or an ETS programming operation. No status is transmitted during a delay even if the state changes during this delay. The delay time is started immediately after the ETS programming operation is completed, i. e. already before the device is initialised (indication of "--" on the display). If the initialisation of the gateway (due to many groups and single devices) takes longer than the delay time configured in the ETS, the status is transmitted only after the initialisation phase has been completed. Deactivated: The status is transmitted immediately after the bus or mains voltage returns or after an ETS programming operation during the device initialisation. | |
Brightness value Cyclical transmission | Checkbox (yes / no) |
|---|---|
The brightness value status can also be sent out cyclically in addition to being transmitted when updated. Activated: Cyclical transmission is activated. The cycle time is defined uniformly for all status messages of the affected group and single device by the parameter with the same name on the same parameter page. Deactivated: Cyclical transmission is deactivated so that the status is transmitted to the KNX only when a state is updated. | |
Parameters for colour temperature status
Color temperature | Checkbox (yes / no) |
|---|---|
The gateway can track the set colour temperature of a DALI group and single device via a separate 2-byte status object according to DPT 7.600 and can also transmit it to the KNX, provided the bus voltage is switched on. Activated: The object "Colour temperature - Status" is enabled. The colour temperature status is transmitted as soon as the status is updated. Deactivated: No colour temperature status is available. | |
Color temperature Updating of the object value | after each update of the input objects for absolute colour temperature control only if the feedback value changes |
|---|---|
At this point, you can define when the gateway updates the feedback value for the colour temperature status. The object value updated last by the gateway is then actively signalled to the KNX, provided the "Transmit" flag is set on the communication object. After each update of the input objects for absolute colour temperature control: The gateway updates the feedback value in the object as soon as a new telegram is received to specify a colour temperature value or a value is specified by an internal function of the gateway (e. g. scene function, HCL matrices). The default colour temperature value does not necessarily have to change. Consequently, in the event of, for example, cyclical telegrams to the input objects, the corresponding colour temperature status telegrams are also generated. only if the feedback value changes: The gateway updates the colour temperature status only when the telegram value also changes. If the telegram value does not change (e.g. in the case of cyclical telegrams to the input objects with the same telegram value), the status then remains unchanged. Consequently, no telegram with the same content is output repeatedly either. This setting is recommended, for instance, if the objects "Absolute colour temperature - Setting" and "Colour temperature -Status" are linked to an identical group address. This is often the case when activating by means of light scene push-button sensors (recall and storage function). | |
Color temperature Delay after bus/mains voltage return | Checkbox (yes / no) |
|---|---|
The colour temperature status can be transmitted to the KNX after the bus or mains voltage returns or after an ETS programming operation, provided the "Transmit" flag is set on the communication object and the reset behaviour of the underlying functions is not configured to "no reaction". In these cases, the status telegram can be transmitted with a time delay, whereby the delay time is set globally for all groups together. Activated: The status is transmitted after a delay after the bus or mains voltage returns or an ETS programming operation. No status is transmitted during a delay even if the state changes during this delay. The delay time is started immediately after the ETS programming operation is completed, i. e. already before the device is initialised (indication of "--" on the display). If the initialisation of the gateway (due to many groups and single devices) takes longer than the delay time configured in the ETS, the status is transmitted only after the initialisation phase has been completed. Deactivated: The status is transmitted immediately after the bus or mains voltage returns or after an ETS programming operation during the device initialisation. | |
Color temperature Cyclical transmission | Checkbox (yes / no) |
|---|---|
The colour temperature status can be transmitted also cyclically in addition to being transmitted when updated. Activated: Cyclical transmission is activated. The cycle time is defined uniformly for all status messages of the affected group and single device by the parameter with the same name on the same parameter page. Deactivated: Cyclical transmission is deactivated so that the status is transmitted to the KNX only when a state is updated. | |
Invalid colour temperature | Checkbox (yes / no) |
|---|---|
In addition to the status for displaying the current colour temperature, the gateway can use a separate 1-bit status object to indicate whether an externally specified colour temperature is valid ("ON" object value) or invalid ("OFF" object value). An invalid colour temperature exists if the specified value violates the set limits of the minimum and maximum colour temperature. Activated: The object "Colour temperature invalid - Status" is enabled. The status for an invalid colour temperature is transmitted as soon as the status is updated. Deactivated: No status is available for an invalid colour temperature. | |
Invalid colour temperature Updating of the object value | after each update of the input objects for absolute colour temperature control only if the feedback value changes |
|---|---|
At this point, you can define when the gateway updates the feedback value for the status of an invalid colour temperature. The object value updated last by the gateway is then actively signalled to the KNX, provided the "Transmit" flag is set on the communication object. After each update of the input objects for absolute colour temperature control: The gateway updates the feedback value in the object as soon as a new telegram is received to specify a colour temperature value. The default colour temperature value does not necessarily have to change. Consequently, in the event of, for example, cyclical telegrams to the input objects, the corresponding status telegrams are also generated. only if the feedback value changes: The gateway updates the status of an invalid colour temperature only if the telegram value also changes. If the telegram value does not change (e.g. in the case of cyclical telegrams to the input objects with the same telegram value), the status then remains unchanged. Consequently, no telegram with the same content is output repeatedly either. | |
Invalid colour temperature Delay after bus/mains voltage return | Checkbox (yes / no) |
|---|---|
The status for an invalid colour temperature can be transmitted to the KNX after the bus or mains voltage returns or after an ETS programming operation, provided the "Transmit" flag is set on the communication object and the reset behaviour of the underlying functions is not configured to "no reaction". In these cases, the status telegram can be transmitted with a time delay, whereby the delay time is set globally for all groups together. Activated: The status is transmitted after a delay after the bus or mains voltage returns or an ETS programming operation. No status is transmitted during a delay even if the state changes during this delay. The delay time is started immediately after the ETS programming operation is completed, i. e. already before the device is initialised (indication of "--" on the display). If the initialisation of the gateway (due to many groups and single devices) takes longer than the delay time configured in the ETS, the status is transmitted only after the initialisation phase has been completed. Deactivated: The status is transmitted immediately after the bus or mains voltage returns or after an ETS programming operation during the device initialisation. | |
Invalid colour temperature Cyclical transmission | Checkbox (yes / no) |
|---|---|
The status for an invalid colour temperature can be transmitted also cyclically in addition to being transmitted when updated. Activated: Cyclical transmission is activated. The cycle time is defined uniformly for all status messages of the affected group and single device by the parameter with the same name on the same parameter page. Deactivated: Cyclical transmission is deactivated so that the status is transmitted to the KNX only when a state is updated. | |
Parameters for colour status
Color | Checkbox (yes/no) |
|---|---|
The gateway can track the set colour of a group and single device by means of separate objects and transmit it also to the KNX, provided the bus voltage is switched on. The data format of the status objects depends on the selected colour space (RGB[W] combined, RGB[W] individually, HSV[W]) and is based on the format of the input objects. Activated: The objects for the colour status are enabled. The colour status is transmitted as soon as the status is updated. Deactivated: No colour status is available. | |
Color Updating of the object value | after each update of the input objects for absolute colour control only if the feedback value changes |
|---|---|
At this point, you can define when the gateway updates the feedback values for the colour status. The object values updated last by the gateway are then actively signalled to the KNX, provided the "Transmit" flags are set on the communication objects. After each update of the input objects for absolute colour control: The gateway updates the feedback value in the objects as soon as new telegrams are received to specify a colour value or values are specified by an internal function of the gateway (e. g. scene function, colour wheel sequence, HCL matrices). The default colour value does not necessarily have to change. Consequently, corresponding colour status telegrams are also generated, for example, in the event of cyclical telegrams to the input objects. only if the feedback value changes: The gateway updates the colour status only when the telegram values also change. If the telegram values do not change (e. g. in the case of cyclical telegrams to the input objects with the same telegram value), the status remains unchanged. Consequently, no telegram with the same content is output repeatedly either. | |
Color Delay after bus/mains voltage return | Checkbox (yes / no) |
|---|---|
The colour status can be transmitted to the KNX after the bus or mains voltage returns or after an ETS programming operation, provided the "Transmit" flag is set on the communication object and the reset behaviour of the underlying functions is not configured to "no reaction". In these cases, the status telegram can be transmitted with a time delay, whereby the delay time is set globally for all groups together. Activated: The status is transmitted after a delay after the bus or mains voltage returns or an ETS programming operation. No status is transmitted during a delay even if the state changes during this delay. The delay time is started immediately after the ETS programming operation is completed, i. e. already before the device is initialised (indication of "--" on the display). If the initialisation of the gateway (due to many groups and single devices) takes longer than the delay time configured in the ETS, the status is transmitted only after the initialisation phase has been completed. Deactivated: The status is transmitted immediately after the bus or mains voltage returns or after an ETS programming operation during the device initialisation. | |
Color Cyclical transmission | Checkbox (yes / no) |
|---|---|
The colour status can be transmitted also cyclically in addition to being transmitted when updated. Activated: Cyclical transmission is activated. The cycle time is defined uniformly for all status messages of the affected group and single device by the parameter with the same name on the same parameter page. Deactivated: Cyclical transmission is deactivated so that the status is transmitted to the KNX only when a state is updated. | |
