vast sigil
I already managed to make different assistants (as personalities) for users as they prefer, but then, we can have only one preffered assistant. What I have on mind is even more restricting idea - to let user have only 'their' assistant without access to another one?
I tagged OpenAI as I use it, but I don't think it's matter which one you're using for this, right?
eager sluice
there is no way to restrict usage, though. whoever can speak to the satellite, can interact with the satellite
faint cairn
Yeah, there's nothing like voice tagging/identification that would map a user to a specific pipeline regardless of satellite or anything like that.
That's a hard problem to implement 😁
placid dawn
That's a hard problem to implement 😁
On current stage that is 🙂
vast sigil
Well, we already have very specific user, as to interact with HA you need to be logged in. And that's what I mean, not to determine user by voice, but who's logged in. So what i'd want to achieve:
elseif user == Joan Doe user assistant_2
else use assistant_3```And preferred uses for whole system. I can't change preferred AI for one user only, right?
faint cairn
you mean on the app, or on voice devices?
Though don't think either is really possible at the moment
vast sigil
App (mobile and computers). Voice devices would use that 'else'
faint cairn
Yeah don't think there's anything that decides a specific assistant to use per user
vast sigil
awww, so sad. Maybe one day. Do you think it would be matter of integration? addon?
round saffron
Would be cool if users could define the default pipeline to use in the user settings of the mobile app.
eager sluice
awww, so sad. Maybe one day. Do you think it would be matter of integration? add...
No, that's purely core and frontend implementation, but there needa to be critical mass to drive the implementation. In more than 2y of me being here, you are the first person to ask for this
vast sigil
I'm just AI weirdo 😄
round saffron
I'm just AI weirdo 😄
count me in
eager sluice
Would be cool if users could define the default pipeline to use in the user sett...
This would be a much more elegant solution, provided that non-admins could do this on themselves
vast sigil
count me in
Wohoo! Just an hour of this topic existing and already 100% more people on this! 😄
vast sigil
This would be a much more elegant solution, provided that non-admins could do th...
Yes and no, I would want to force user to use particular persona, OR prevent from using particular persona(s) 🙂
placid dawn
No, that's purely core and frontend implementation, but there needa to be critic...
Can't be! Alexa and Google have user mapping.
vast sigil
It's not language model specific problem after all. We have different VAs, we have different users. The thing is HA doesn't have enough user privilages settings IMO
you can prevent user from seeing entity in dashboard, but he still can access it
with pressing E they have access to simply anything. it's huge security issue.
eager sluice
It's not language model specific problem after all. We have different VAs, we ha...
That is a whole different topic. I thought we were discussing how you could achieve your goal in the current confinements 🙂
vast sigil
Yes, yes, sorry, got carried away
So... do you think there are existing user control addons/thingies that I could use to limit their access to VA (and other entities? ^^ )
It's actually one and same problem
eager sluice
No, there aren't any
vast sigil
VA is entity. If you have control what entities are accessible to user, then my problem is solved as well.
Thanks
placid dawn
VA is entity. If you have control what entities are accessible to user, then my ...
What you mean "VA is entity"?
assist_satellite is entity. But that doesn't mean you can restrict voice command, even if you (somehow) restrict that entity for user...
vast sigil
well, it exist on my entities list as i.e. conversation.chatgpt_1
If I would be able to restrict user's access to entities, I'd simply not allow certain user to access this chatbot and he couldn't use it.
The problem is I cannot it seems 🙂
eager sluice
He means the conversation agent, not the satellite. Which the app/browser isn't anyway. Which is also a bad approach, as multiple pipelines could share a conversation agent, so you want to restrict the pipeline.
Either way, it's not possible
vast sigil
Can you explain 'pipeline' or direct me to definition so I could address that please?
vast sigil
No, I don't think I wanted to do anything with pipeline (maybe custom voices, yes), but my intentions were to restrict user to certain personality of text-processing AI. Right now I have two services GPT chat installed each with different personality (prompt), and they are two different entities.
faint cairn
yeah so conversation agents are bound to pipelines, and pipelines are what make an Assistant
so one pipeline can't conditionally bind to different conversation agents
it's fundamentally not part of the design
the conversation agent is essentially the core of the pipeline. So if you want different "personalities" for each user, those would have to be separate pipelines (assistants) that would then get assigned to a user
but as tetele says, that's fundamentally not possible as things are now 🙂
vast sigil
S.A.D. 😭 But yeah, I understand and awaiting future changes 😄
faint cairn
I mean to be fair, not even google/alexa do that, and they've had a 10 year head start on home assistant 😁
they let you pick different voices and such, but as far as personality it's all the same assistant backend, they just layer some of your preferences and data on top
more or less contextual RAG
vast sigil
Well, differently than HA, they aren't supposed to work in multi-user multi-roles envirnoment. You usually don't want every user to have access to every device , right?
and even google allows you to select which devices you are sharing with other 'home users'
faint cairn
Yeah but that requires a more advanced system from the ground up
the idea of voice commands or even entire entities being restricted by users, a way to identify a user both at the control/interaction point as well as at the voice point (voice identification), possibly even a user role management system
I think I read recently that google has actually been overhauling that on their assistant as well
implementing role systems and such
vast sigil
Well yes, HA definitely needs some security options, be it roles (each role with set of entities/devices accessible) or even directly restrictions for each entity/device per user
eager sluice
one other important thing: Google does voice signature matching. Assist/HA simply relay the audio with no voice signature analysis
vast sigil
Tetele, I was talking about google assistant on phones. See, if I have on my phone set of lights, I can share for other memebers of family which of them are accessible. You are talking about (simplyfying here) google speakers which everyone uses.
placid dawn
Tetele, I was talking about google assistant on phones. See, if I have on my pho...
That's completely different approaches. In Google, each user has their own environment, basically.
faint cairn
Yeah in google when you add someone to your household, they are basically a new account and you have to add all the integrations, devices, etc all over again for them, at least that's how it was the last time I had used it
so that's akin to have a whole separate HA instance just for a different user 😅
vast sigil
You don't need separate instance, you need just different entity access for different logged user 😛
faint cairn
well yeah, but again that fundamentally doesn't exist, and is a pretty large change, a deep core change really
I was just describing how google/alexa do it more or less
vast sigil
even disabling that 'e' search would increase security in ha.
faint cairn
each person has their own assistant "instance" that stuff gets bound to
eager sluice
even disabling that 'e' search would increase security in ha.
Obscurity is not security. Hidden does not mean safe. I told you where you can submit feature requests, but heads up: role-based access control ia by far tge most requested feature for a few years and still nothing
