#have multiple of the default conversation agent?

1 messages · Page 1 of 1 (latest)

haughty sequoia
#

is there a way to do this or a technical reason why it can't/shouldn't be done?

my thought is that i can expose different entities to different instances of the agent and then have different pipelines for voice hardware in different rooms around the house. so 1 room can call things the other can't.

I am sure there are workaround to achieve the same thing. or maybe i am missing an obvious way to do what i am thinking of. but i feel having multiple of the stock agent would be a good solution. maybe i am just heading the wrong direction and need slapped.

halcyon gyro
#

Well, the management UI would suck (i'm thinking about managing exposure), but i agree it would make sense for other usecases as well, such as very rudimentary voice RBAC

haughty sequoia
#

yeah thats what i was thinking. i really dont want people in the kitchen messing with the light at my desk. or someone in guest room setting off alarms etc...
how to make it usable is another matter. i guess would need to allow renaming of assist to a custom name(at least for additional instances)

final trout
#

It could be area-based assists.
Right now i achieve it via making everything area-aware, and adding aliases to each entity (so i have "top light" in every room, but the "turn on top light" command will work for current area top light. If you want to actually RESTRICT people from managing devices in different room, not just avoid unintentional switching - i guess there's no way now.

stray arrow
#

I don’t think the Expose UI would be too bad. Already there is a general check and one for assist. There could be the general one and then one for each “Assistant”. I don’t expect people have very many of these and most would just use the top toggle for all or none anyway.

#

I could see wanting to give my LLM pipelines access to different entities than my local one.

halcyon gyro
#

Somebody write a feature request for this, then. The idea is to have granular exposure per pipeline, the rest is already doable