Difference between Assist and sentence parser in development tools

[elfin patrol]

I've got a temperature sensor in my beer fridge, and set up an alias to that entity 'beer'.

When trying to ask with Assist, no LLM just the included assist, the following happens:

 < How cold is the beer?
 > Sorry, I am not aware of any climate```

meanwhile the exact same sentence in Developer tools produces the following, clearly getting the correct entity.

```intent:
  name: HassClimateGetTemperature
slots:
  name: beer
details:
  name:
    name: name
    value: beer
    text: beer
targets:
  sensor.0xa4c13807de2effff_temperature:
    matched: true
match: true
sentence_template: how (hot|cold|warm|cool) is (<name>|[it <in>] <area>)
unmatched_slots: {}
fuzzy_match: false```

is this a bug, or do I need to setup something else?

Difference between Assist and sentence parser in development tools

[ashen warren]

Just create custom automation, why pretending it to be climate?

[earnest locust]

Feels to me like a temperature sensor should work OOTB without needing a custom automation.

As a newbie, I'm fascinated with this question. In the Assist UI, the sentence isn't matched. In the Developer Tools UI, it matches fine. Why?

OP, if I were debugging this, I'd lock onto the unmatched "the". Does each UI respond identically to the (grammatically incorrect but template-conforming) sentence how cold is beer?

[elfin patrol]

I can, but that's not the point of the question. I'm trying to understand why there is a difference, where that difference comes from, and why that is in general.

[elfin patrol]

Good point, thanks. Alas this gives the same response:

 > Sorry, I am not aware of any climate```

Interestingly it does give a temperature answer for an area:
``` < how cold is kitchen?
 > 17.15 degrees```

[ashen warren]

The difference is, that you're trying to call built-in intent, targeted specifically to climate domain, and make it find your sensor entity. For sure it will fail.
Either have a thermostat, or use custom intent/automation.

[earnest locust]

How does the Developer Tools UI find the correct sensor? Is it using different built-in intents?

[ashen warren]

I believe it shows sentence match, not the built-in intent logic. It found the entity - nevertheless it doesn't fit the domain.

[earnest locust]

I was looking at that in the sentence match. You could set up the beer cooler as an area and assign the sensor to it.

formatBCE seems to be saying that devtools found a sentence match and a sensor match, but doesn't necessarily put them together into a coherent statement

So assigning the sensor to an area named "the beer" might just fit the sentence

[ashen warren]

The built-in sentences for area temperature are using climate - that is intentional. So even assigning it to area won't do. To get reading from temperature sensor, you need custom intent.

[elfin patrol]

As a user this is still quite confusing for me. I've been looking for the word climate in the integrations, in the development tools, and I can't find it. So this is something very important but also hidden for the user?