KNX Cookbook

[farmio (Matthias Alphart)]

@smallFire

I think since 2021.11 my date/time is only updated to the KNX-bus when I restart the core. No refresh after the usual 1 hour. Nothing changed in the config and it was working fine.

see KNX: Date/Time update (1h) not working anymore · Issue #61001 · home-assistant/core · GitHub
Please note that the Forum isn’t an issue tracker - the GH issue tracker is. If you encouter bugs please open an issue at Github and fill the issue template with as many information as possible.

@smallFire

I’m struggling around since I renamed some of my bus addresses

As a general rule of thumb: don’t rearrange GAs, give them a reasonable, searchable name and be done with it. I know some have the urge to keep some kind of scheamtics in their GA numbering in the end there is very little gain for the possible hassle it can produce.

@smallFire

but somehow there seems to be a history.
i.e.:
2/4/1 was a switch names child1.Christmas.light and should now be child.desk.lamp
2/4/2 is a new address and should now be child1.Christmas.light

it’s not a histroy, its HAs EntityRegistry. The KNX integration uses significant GAs of entities as unique_id to identify its entities globally in HA. This is needed to be able to rename entities and assign areas etc.
You changed a significant GA so a new unique_id (and entity) is created - leaving the old as orphan in the EntityRegistry. You can manually delete it from UI.
When you create a new one without delelting - having the same significant GAs it basically replaces the old, and the friendly_name, area assignment etc. is preserved in the EntityRegistry.

PS: you are free to use spaces and upper case characters, even special characters (and emojis I think) in your yamls name keys - no need for special custom dot-notation. But this is only used for the default friendly_name anyway so not that important.

@smallFire

I change the YAML and reboot - but it’s keeping the old names on the UI

Just change it in UI then.

@smallFire

how could changing the update interval change anything for that? (+ how could I do so to try)

Not possible for time exposure - thats a fixed interval.

@smallFire

Actually there is not really so much logic yet. All the things are in node-red and it seems that “Output only on state change” triggers the action - where actually there shouldn’t be a state change at all.

Involving Node-Red doesn’t make finding problems easier Maybe the entities change their state from something to unavailable and back due to disconnects of your KNX tunnelling device. Automations (and I guess node-red things) should be set up to be resilent for these state changes.