#Local fallback not being invoked, going to LLM, then not answering

1 messages · Page 1 of 1 (latest)

pliant girder
#

I've configured an OpenAI key and can converse using it just fine. I've configured it to prefer handling locally, but I'm running into strange issues. When I ask the Home assistant "What is the value of Motion Sensor Backyard Temperature?" it responds with the temperature. When I ask the same question (copy/pasted) to the OpenAI bot, it says it can't access temperatures. I've checked the sentence in the Dev Tools, and it correctly finds a HassGetState intent. Can anyone help me debug?

#
intent:
  name: HassGetState
slots:
  name: Motion Sensor Backyard Temperature
details:
  name:
    name: name
    value: Motion Sensor Backyard Temperature
    text: Motion Sensor Backyard Temperature
targets:
  sensor.0x0017880106459ec7_temperature:
    matched: true
match: true
sentence_template: >-
  (do you know|tell me|<what_is>) [the [current] (state|value) of] <name>
  [<in_area_floor>]
unmatched_slots: {}
source: builtin
kind star
#

Hm, maybe too short context window?
Too many exposed entities?

hybrid salmon
#

Did you grant Assistant control to your openai conversation agent?

pliant girder
#

I've already granted control. I've got about a hundred entities... Too much? I'm using default model settings.

#

Thanks y'all

hybrid salmon
#

So just to confirm, you have Assist selected on this screen (openai conversation agent config)

#

Weird that the same intent wouldn't trigger local, should behave exactly the same if local control is preferred

#

And also are you using the core OpenAI integration?

pliant girder
#

Yes to both.

hybrid salmon
#

Maybe silly, but have you tried rebooting HA? I've seen that sometimes fix weird stuff like this. Sometimes stuff gets stuck in the context cache that can make this happen.