Last time I checked it worked fine. Maybe it’s your automation config?
If knx_event works fine, why not use it?
Knx_event behaves the same way.
“Maybe it’s your automation config?” What do you mean? I just added a lovelace entry that show that specific sensor.
Probably its just a very simple problem but at the moment i have no clue 
Maybe try to completely describe your problem / expected behavior / awaited events and also show your configurations etc. I’m more and more confused what you mean.
If your sensor shows scene 23 and receives the same scene again it will probably still show 23.
When there is no automation listening for its state I’m not sure there will be any event.
First of all - thanks for the documentation.
KNX setup works fine with Weinzierl.
But I did not find a solution to add a light to an existing room. The KNX components always appears in “lights” group only.
knx:
tunneling:
host: '192.168.123.2'
light:
- name: danielsbuero
address: '0/3/7'
- name: sebisbuero
address: '0/3/8'
When I try to add the room information in frontend, I get the message “this entity has no unique ID”.
Hi Farmio,
thanks again. I’m listening with a node red “events.state”-node to this knx-scene-sensor.
I trigger a scene and everything works as expected. I trigger the same scene again (without any other scene in the meanwhile) and nothing is happening in node red because hassio does not write an update to this sensor, because the scene number is the same as before. But always_callback should, as far as i understand it, update the sensor so that the node red - node sees a change/upDATE and therefore triggers the event.
At the moment im using an automation which resets the sensor, it works but it should not be needed 
Good hint 
It was “Current state equals previous state” but that was exactly the reason. Sorry for all that confusion
Areas were added in 2021.4 - you’ll need to update HA. (Maybe wait till Wednesday when 2021.5 is out. There were some problems that require migration of the unique_id that you would just skip then - but it is automated and should be fine).
PS. You can use uppercase, spaces etc in your “name” attributes.
@farmio thanks for the info. Yeah first I had speaking names, but changed it - hoping this could solve my problem
Then I will wait for the update.
What’s the syntax to add the room/area? Or do I have to add this info in frontend?
It’s a frontend thing. You can then also change the friendly_name and entity_id. The configured name is used as default.
YAML does not accept friendly_name nor entity_id.
Invalid config for [knx]: [friendly_name] is an invalid option for [knx]. Check: knx->knx->light->0->friendly_name. (See /config/configuration.yaml, line 25).
Invalid config for [knx]: [entity_id] is an invalid option for [knx]. Check: knx->knx->light->0->entity_id. (See /config/configuration.yaml, line 25).
these are all only configurable in the frontend since 2021.4
I have another problem/question, regarding covers.
It seems like I can only configure one at the same time, but I cannot find the mistake I made in configuration.
Specifically: only the last one is working. I tried another order, then the other one works fine.
For this configuration only “Sebis Büro” works. The “Schlafzimmer Jalousie” appears in frontend, but is disabled (grey - not reachable).
Do you have any idea what’s wrong here?
knx:
tunneling:
host: '192.168.123.2'
light:
- name: 'Daniels Büro Deckenlampe'
address: '0/3/7'
- name: 'Sebis Büro Deckenlampe'
address: '0/3/8'
cover:
- name: 'Daniels Büro Jalousie'
move_short_address: '1/2/1'
move_long_address: '1/3/1'
cover:
- name: 'Gästezimmer Jalousie'
move_short_address: '1/2/2'
move_long_address: '1/3/2'
cover:
- name: 'Schlafzimmer Jalousie'
move_short_address: '1/0/3'
move_long_address: '1/1/3'
cover:
- name: 'Sebis Büro Jalousie'
move_short_address: '1/2/0'
move_long_address: '1/3/0'
In my entities the “Schlafzimmer” is listed as “Integration: Abdeckung”, the “Sebis Büro” is correcly listed as “Integration: KNX”. The others are not listed at all.
- makes a new item in a list. Seems like you are overwriting the cover: items couple of times.
Have a closer look at KNX - Home Assistant
You did it right in light:
Also consider configuring travelling_time_down and _up for covers 
This is the case when you delete (or invalidate) configuration of an entity. It leaves an orphaned entity in the entity_registry. You should be able to delete it from UI after a restart - or it works again after you fixed your configuration.
1 Like
Ah thanks. Perhaps it was too late already…
I will have a Look at travelling_time_down - guess I will have to measure it.
Now where is THAT screenshot from? Never saw this combination of checkboxes.
Hassio “event: state” node.
That node looks very different in my system - see my screenshot. Did you skip the updates of your Node RED add-on for a very long time?
No, its 9.0.1
Btw. I don’t see a screenshot