Skip to content

Mention that the date, datetime and time entities can be configured from the UI #42035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
silamon merged 1 commit into from
Dec 3, 2025
Merged

Mention that the date, datetime and time entities can be configured from the UI #42035

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions source/_integrations/knx.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,7 @@ There is currently support for the following device types within Home Assistant:
- [Climate](#climate)
- [Cover](#cover)
- [Date](#date)
- [DateTime](#datetime)
- [Fan](#fan)
- [Light](#light)
- [Notify](#notify)
Expand Down Expand Up @@ -1267,6 +1268,10 @@ Dates that have a `state_address` configured request their current state from th
DPT 11.001 covers the range 1990 to 2089. Year values outside of this range are not allowed.
{% endnote %}

Date entities can be created from the frontend in the KNX panel or via YAML.

{% details "Configuration of KNX date entities via YAML" %}

```yaml
# Example configuration.yaml entry
knx:
Expand Down Expand Up @@ -1319,6 +1324,8 @@ entity_category:
default: None
{% endconfiguration %}

{% enddetails %}

## DateTime

The KNX datetime platform allows to send datetime values to the KNX bus and update its state from received telegrams. It can optionally respond to read requests from the KNX bus.
Expand All @@ -1334,6 +1341,10 @@ System timezone is used as DPT 19.001 doesn't provide timezone information.
Year values outside of the range 1900 to 2155 are invalid.
{% endnote %}

Datetime entities can be created from the frontend in the KNX panel or via YAML.

{% details "Configuration of KNX datetime entities via YAML" %}

```yaml
# Example configuration.yaml entry
knx:
Expand Down Expand Up @@ -1386,6 +1397,8 @@ entity_category:
default: None
{% endconfiguration %}

{% enddetails %}

## Fan

The KNX fan integration is used to control KNX fans. Following control types are supported:
Expand Down Expand Up @@ -2321,6 +2334,10 @@ Times that have a `state_address` configured request their current state from th
The `day` field of the time telegram will always be set to 0 (`no day`).
{% endnote %}

Time entities can be created from the frontend in the KNX panel or via YAML.

{% details "Configuration of KNX time entities via YAML" %}

```yaml
# Example configuration.yaml entry
knx:
Expand Down Expand Up @@ -2373,6 +2390,8 @@ entity_category:
default: None
{% endconfiguration %}

{% enddetails %}

## Weather

The KNX weather platform is used as an interface to KNX weather stations.
Expand Down