#not sure if it's me missing something (
humble heart
it hasn't popped up, i've been paying attention for the past week. however, it might be an older issue we can trace with new tools. go to https://my.home-assistant.io/redirect/developer_assist/ and try it there, then paste the log
normal knoll
cheers , the log below
intent:
name: HassGetState
slots:
name: temperature
area: back garden
details:
name:
name: name
value: sensor.temperature_3
text: temperature
area:
name: area
value: back_garden
text: back garden
targets: {}
match: true
sentence_template: >-
(do you know|tell me|<what_is>) [the [current] (state|value) of] <name> [in
<area>]
unmatched_slots: {}
source: builtin
mkay, that sounds like the right intent. i'll assume you have a temperature sensor in the back garden. is it called simply Temperature?
normal knoll
it is called Garden Temperature - interestingly the sensor.temperature_3 is allocated to 'sitting room'
humble heart
ok, i think i know what the issue is. @frigid oxide could it be that the new recognition doesn't go through all matches to see if they make sense before trying to handle the intent? is it just the first match that it's trying to handle?
@normal knoll you said you don't get any error logs in core, right?
normal knoll
i did until i rebooted. and i didn't copy it like a fool. it was an intent error, and said no climate entity in the area ( or words to that effect ) since rebooting they no longer show though so I cant copy it for you
just tried again and get this warning
Logger: homeassistant.helpers.template
Source: helpers/template.py:2345
First occurred: 08:58:50 (3 occurrences)
Last logged: 09:32:26
Template variable warning: 'None' has no attribute 'state_with_unit' when rendering '{{ slots.name | capitalize }} is {{ state.state_with_unit }}'
listen though , it's no biggie! I know you guys are all up to your eyes in it at the moment. I just wanted to bring it to your attention more than anything in case it was beta related. so no sweat for me. 👍
humble heart
it might be beta related, due to the new way of handling errors. could you please create a core issue about it?
normal knoll
yeah no probs will do
humble heart
oh, and please drop the link in #beta too, so it gets properly tagged and prioritized
frigid oxide
@normal knoll Is your sentence "what is the garden temperature"?
normal knoll
what is temperature in back garden @frigid oxide
frigid oxide
OK, thanks 👍
normal knoll
OK, thanks 👍
just tried again and get this log
Logger: homeassistant.components.conversation.default_agent
Source: components/conversation/default_agent.py:296
Integration: Conversation (documentation, issues)
First occurred: 20:03:33 (1 occurrences)
Last logged: 20:03:33
Intent handling error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 296, in async_process
intent_response = await intent.async_handle(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 108, in async_handle
result = await handler.async_handle(intent)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/climate/intent.py", line 50, in async_handle
raise intent.IntentHandleError(f"No climate entity in area {area_name}")
homeassistant.helpers.intent.IntentHandleError: No climate entity in area back_garden
The temperature intent only supports climate entities for now, not temperature sensors (despite the name 😛). This will be fixed likely in the next HA version with a batch of new intents.
humble heart
Still, it shouldn't spit out a handler error
The intent should simply not be recognized
frigid oxide
It shouldn't throw a handler error, but the intent will be recognized regardless because hassil doesn't know there aren't any climate entities in that area.
There is a different error to throw that will be much better 👍
normal knoll
i have a climate control in the living room , and that gives the same result , also if i phrase it , 'what is back garden temperature' i get an unexpected error has occured
climate.house_thermostat is in 'living room' - when i ask 'what is temperature in living room' I get the same result. "temperature is" and logs shows warning
Template variable warning: 'None' has no attribute 'state_with_unit' when rendering '{{ slots.name | capitalize }} is {{ state.state_with_unit }}'
This seems to be alternating between the actual temperature intent and the generic "get state" intent. {{ slots.name | capitalize }} is {{ state.state_with_unit }} is part of HassGetState
humble heart
yes, and the issue i see is that it only tries to handle a single result, instead of cycling through them until it can finally handle an intent. which would not have been a problem if the recognition wouldn't have yielded multiple matches, based on required name/device_class/area
i mean... in older terms, those wouldn't have been matched at all