[DE] Device in Area triggers scene instead of generic HassTurnOn

[badewanne1234]

I have a light called "Garderobe" and an area "Eingang", of course the light is linked to the area.

When parsing the sentence "Schalte Garderobe in Eingang ein" or "Schalte Garderobe in Eingang an" in the dev tools, I would expect it to parse it as follows:

intent:
  name: HassTurnOn
slots:
  area: Eingang
  name: Garderobe
details:
  area:
    name: area
    value: Eingang
    text: Eingang
  name:
    name: name
    value: Garderobe
    text: garderobe
targets:
  light.licht_garderobe:
    matched: true
match: true
sentence_template: ' (<schalten>|<machen>) <name>[ <area>] <an>'
unmatched_slots:
  name:{}
source: builtin

Instead, its parsed as a scene

intent:
  name: HassTurnOn
slots:
  area: Eingang
  domain: scene
details:
  area:
    name: area
    value: Eingang
    text: Eingang
  domain:
    name: domain
    value: scene
    text: ''
targets: {}
match: false
sentence_template: '[<szene> ]<name> <area>[ (<aktivieren>|<ausfuehren>|<an>)]'
unmatched_slots:
  name: 'Schalte Garderobe '
source: builtin

I'm not sure why it parses as a scene, any thoughts?

[mib1185]

I can't reproduce it (on ha core 2025.1.2). Which HA core version do you use?

[badewanne1234]

You are correct, I was on 2024.12.x, I updated to 2025.1.2 now and its a goner. Thank you, sorry for bothering...

[amatthies]

Hm, I'm on 2025.1.4 and I have a similar problem with Home Assistant Cloud

"Licht im Schlafzimmer aus" works as expected:

intent:
  name: HassTurnOff
slots:
  name: Licht
  area: Schlafzimmer
details:
  name:
    name: name
    value: Licht
    text: Licht
  area:
    name: area
    value: Schlafzimmer
    text: Schlafzimmer
targets:
  light.schlafzimmer:
    matched: true
match: true
sentence_template: <name>[ <area>] <aus>[<schalten>|<machen>]
unmatched_slots: {}
source: builtin

but "Licht im Schlafzimmer an" wants a scene (that I don't have) and fails:

intent:
  name: HassTurnOn
slots:
  name: Licht
  area: Schlafzimmer
  domain: scene
details:
  name:
    name: name
    value: Licht
    text: Licht
  area:
    name: area
    value: Schlafzimmer
    text: Schlafzimmer
  domain:
    name: domain
    value: scene
    text: ''
targets: {}
match: true
sentence_template: '[<szene> ]<name> <area>[ (<aktivieren>|<ausfuehren>|<an>)]'
unmatched_slots: {}
source: builtin

[mib1185]

even this i can't reproduce

[amatthies]

And what does your sentence parser show? When I switch to English ("Light in Schlafzimmer on") it works for me, domain is "light". Why is "scene" the domain in German for HassTurnOn, but not HassTurnOff? I have no scene called "Licht".

[mib1185]

looks good at my end - do you've any scenes exposed?

[amatthies]

Yes, I do have some scenes exposed, but none is called Licht or Schlafzimmer. The scene domain is also triggered for areas without any scene. Interestingly "Lampen im Schlafzimmer an" or "Lichter im Schlafzimmer an" triggers the correct sentence_template. It's just "Licht" that doesn't work correctly

[mib1185]

Just for science - please dis-expose (is this a real word 🤔 ) all scenes and test again

[amatthies]

Just for science - please dis-expose (is this a real word 🤔 ) all scenes and test again

How do I do that? I have 18 scenes, most of them coming from Hue Bridge. They work as supposed an none of them contains "Licht".

[mib1185]

here is the documentation, how to expose entities to assists - just do the reverse for all scene entities (keep in mind to note down the exposed, you you can expose them later again)