jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

KNX UI configuration of light and switch (#34905)

Browse Source 
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
This commit is contained in:
Matthias Alphart 2024-09-24 22:36:56 +02:00 committed by GitHub
parent b797b3e33d
commit e51d9a5474
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
source/_integrations/knx.markdown
View File

@ -1241,15 +1241,10 @@ The KNX light integration is used as an interface to control KNX actuators for l
- LED controllers
- DALI gateways
To use your KNX light in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
Light entities can be created from the frontend in the KNX panel or via YAML.
```yaml
# Example configuration.yaml entry
knx:
light:
- name: "Kitchen"
address: "1/0/9"
```
<a name="configuration-light-yaml"></a>
{% details "Configuration of KNX light entities via YAML" %}
{% configuration %}
address:
@ -1382,11 +1377,9 @@ entity_category:
Many KNX devices can change their state internally without a message to the switch address on the KNX bus, e.g., if you configure a scene or a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given `state_address` (in most cases from the light actuator), it will overwrite the state of the object.
For switching/light actuators that are only controlled by a single group address and don't have dedicated state group objects you can set `state_address` to the same value as `address`.
For switching/light actuators that are only controlled by a single group address and don't have dedicated state group objects you can set `state_address` to the same value as `address` if it is readable from the bus.
*Note on tunable white:* Home Assistant uses Mireds as the unit for color temperature, whereas KNX typically uses Kelvin. The Kelvin/Mireds relationship is reciprocal, not linear, therefore the color temperature pickers (sliders) in Home Assistant may not align with ones of KNX visualizations. This is the expected behavior.
### Extended configuration examples
### YAML configuration examples
```yaml
knx:
@ -1472,6 +1465,8 @@ knx:
state_address: "1/0/5"
```
{% enddetails %}
## Notify
The KNX notify platform allows you to send notifications to [KNX](https://www.knx.org/) devices as DPT16 strings.
@ -1988,6 +1983,14 @@ knx:
The KNX switch platform is used as an interface to switching actuators.
Switch entities can be created from the frontend in the KNX panel or via YAML.
Switch entities without a `state_address` will restore their last known state after Home Assistant was restarted.
Switches that have a `state_address` configured request their current state from the KNX bus.
<a name="configuration-switch-yaml"></a>
{% details "Configuration of KNX switch entities via YAML" %}
```yaml
knx:
switch:
@ -2032,8 +2035,7 @@ device_class:
The optional `state_address` can be used to inform Home Assistant about state changes not triggered by a telegram to the `address` e.g., if you configure a timer on a channel. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
Switch entities without a `state_address` will restore their last known state after Home Assistant was restarted.
Switches that have a `state_address` configured request their current state from the KNX bus.
{% enddetails %}
## Text