How do I exclude entities from Sophia?

mjoshd
Oct 2026
7 posts
0 likes
Member
How do I exclude entities from Sophia?
Posted Sun Oct 25th 14:55• Last edited Sun Oct 25th 15:11

Hi, Sophia NLU is very impressive and I have purchased the lifetime subscription with yearly updates.

Sorry if this has already been answered but I did not see any exisitng threads covering this specific issue.

My concern is that it appears that Sophia can see, and act on, all Home Assistant entities.

I was hoping that the Sophia NLU Engine would appear as a choice when using Home Assistant's UI for exposing entities (simple on/off toggles for Assist, Google Assistant, and Alexa) but this does not seem to be the case and it does not seem to respect the selections I have already made for exposing entites for voice control.

Example: In Home Assistant's UI I have exposed for voice control only 106 entities, a handfull of which are scripts (5, to be exact) but in the Sophia app - Entities page it can see 396 items in the "Scenes, Scripts and Automations" section (214 of which are scripts).

I have checked and Sophia is 100% able to run scripts and perform actions on entites that I do not wish to have exposed for voice control.

Is there a way to have Sophia see only the 106 entities I wish to expose for voice control, or possibly a way to block Sophia from acting the ones I do not wish exposed for voice control?

An idea, a sub-optimal for sure, would be manually applying a tag of 'ignore' or 'exclude' on every item a user does not wish Sophia to have control over; while this could be a solution it would require the user to maintain an two lists of entites they want exposed for voice control:

Home Assistant - Settings - Voice Assistants - Expose

Home Assistant - Settings - Apps - Sophia NLU Engine - Open Web UI - Entities

Related and maybe useful: I did a little digging and found that 'config/.storage/core.entity_registry' already contains all entities along with the user's choices made from the UI when selecting to expose a specific entity or not for voice control.

..."options":{"conversation":{"should_expose":true},"cloud.google_assistant":{"should_expose":false},"cloud.alexa":{"should_expose":false}}...

Is it possible to limit Sophia to the items with "conversation":{"should_expose":true} so that it would respect the Home Assistant UI selected choices of whether to expose an entity for voice control or not?

Alternatively, would it be possible to somehow add Sophia in the Home Assistant UI for exposing entities for voice control as an additional toggle next to Assist, Google Assistant, and Alexa?

I apologize if this question has already been answered and I somehow missed it.

Please let me know when you have a moment.

Thanks, Josh

Matt
Apr 2025
94 posts
0 likes
Member
Posted Sun Oct 25th 16:48

First, thank you very much for your purchase of Sophia, it really helps to further develpment.

I'm not sure what the issue would be, but there's a disconnect somewhere as this functionality has been confirmed working by many customers. If an entity is marked as hidden or disabled, or if should expose is set to false, Sophia will skip it when loading the config.

Please double check your settings. If the problem persists, let me know and we'll figure something out to further investigate.

Warm regards, Matt

~reply.author~
~reply.tagline~
~reply.member_since~
~reply.total_posts~ posts
~reply.total_likes~ likes
~reply.user_type~
Posted Sun Oct 25th 17:46

Hi Matt, I guess I question got lost in the text and descriptions.. hopefully the linked images and additional descriptions will help clarify.

I'm not referring to Hidden or Disabled entitites. I'm referring specifically to the desired state of voice control exposure for each entity.

Examples of entities which are not Disabled or Hidden and have separate voice control exposure settings:

Desire: entity is enabled and exposed for voice control (voice control via HA Assist, Google Assistant, and Sophia all work, as desired)

Desire: entity is enabled and not exposed for voice control (voice control via Sophia still works even though the 'Expose' toggle is set to 'off')

I was able to ask Sophia to "Activate josh leaving for work" (script which is not exposed to voice assistants) and it absolutely did run the script even though it responded that it both did it and could not control it.

The script did run and that is the primary problem I am inquiring about (secondary would be the self contradicting response);.

I do not want to provide voice control access for the vast majority of entities.

I have already made specific selections about which entities get exposed for voice control and to which services they are exposed.

I expose only 106 of 3696 entities for Home Assistant voice control and a few of those also get exposed to Google Assistant (Alexa is not in use here).

What I am inquiring about is a way to make Sophia follow/respect the "Assist" toggle (as shown in the second image); is this already possible, or could it be added?

Hopefully this additional info helps to explain what I'm asking about.

Thanks for your quick reply; please let me know if anything still is unclear.

Regards, Josh

Edit
~reply.signature~
mjoshd
Oct 2026
7 posts
0 likes
Member
Posted Sun Oct 25th 17:54• Last edited Sun Oct 25th 18:23

Not sure what happened there.. images went missing and I can't edit my own reply.. attempting again with image urls as 'url'.


Hi Matt, I guess my actual question got lost in the text and descriptions.. hopefully the linked images and additional descriptions will help clarify.

I'm not referring to Hidden or Disabled entitites. I'm referring specifically to the desired state of voice control exposure for each entity. https://github.com/mjoshd/temp/blob/main/Screenshot%202026-10-25%20133007.png

Examples of entities which are not Disabled or Hidden and have separate voice control exposure settings:

Desire: entity is enabled and exposed for voice control (voice control via HA Assist, Google Assistant, and Sophia all work, as desired) https://github.com/mjoshd/temp/blob/main/Screenshot%202026-10-25%20125255.png

Desire: entity is enabled and not exposed for voice control (voice control via Sophia still works even though the 'Expose' toggle is set to 'off') https://github.com/mjoshd/temp/blob/main/Screenshot%202026-10-25%20130536.png

I was able to ask Sophia to "Activate josh leaving for work" (script which is not exposed to voice assistants) and it absolutely did run the script even though it responded that it both did it and could not control it.
https://github.com/mjoshd/temp/blob/main/Screenshot%202026-10-25%20131258.png

The script did run and that is the primary problem I am inquiring about (secondary would be the self contradicting response);.

I do not want to provide voice control access for the vast majority of entities.

I have already made specific selections about which entities get exposed for voice control and to which services they are exposed.

I expose only 106 of 3696 entities for Home Assistant voice control and a few of those also get exposed to Google Assistant (Alexa is not in use here). https://github.com/mjoshd/temp/blob/main/Screenshot%202026-10-25%20140137.png

What I am inquiring about is a way to make Sophia follow/respect the "Expose" and "Assist" toggles (as shown in the second image).

The idea is that Sophia only works with items where both "Expose" and "Assist" are enabled; and specifically can only "see" entities where "Assist" is enabled rather than every single not-disabled entity.

If the "Expose" toggle is "off" then Sophia should not be able to see or interact with that entity, full stop.

If the "Expose" toggle is "on" but the "Assist" toggle is "off" then Sophia should not be able to see or interact with that entity but Google Assistant or Alexa could if their toggles were enabled.

Is this already possible, or could that funcionality be added?

Hopefully this additional info helps to explain what I'm asking about.

Thanks for your quick reply; please let me know if anything still is unclear.

Regards, Josh

Matt
Apr 2025
94 posts
0 likes
Member
Posted Sun Oct 25th 21:04

Hmmm... do you have access to the file system HA is installed on?

If so, can you open the file at /config/.storage/core.entity_registry

Search for your script ID, so something like "script.josh_leaving_for_work" or something similar. Does that JSON object of the script have an "options" block in it with a "should_expose" attribute inside? If yes, is that attribute set to true or false, or is it simply not there?

PS. Life decided to play a funny prank on me years ago and make me totally blind, so no worries about including screenshots. I can't see them anyway.

mjoshd
Oct 2026
7 posts
0 likes
Member
Posted Sun Oct 25th 23:23

Hi Matt,

I checked in the "core.entity_registry" file and located the line pertaining to that specific script.

It does exist and does contain the "options" block in it along with "conversation":"should_expose" attribute set to "false".

Please let me know if there is any other info I can provide.

Regards, Josh

mjoshd
Oct 2026
7 posts
0 likes
Member
Posted Sun Oct 25th 23:35

Also, thank you for letting me know that pictures are unhelpful.

In regard to the earlier verbal activation of the script:

I said "Activate Josh leaving for work".

Sophia responded "alright, Josh Leaving For Work is now on.. And except josh leaving for work couldn't be controlled Feel free to reach out if there's anything more i can do."

Then the "Josh Leaving For Work" script ran and performed all defined actions.

That is an exact reproduction of the whole interaction.

Thank you for your replies and all your work on Sophia it really does work amazingly well!

Regards, Josh

Matt
Apr 2025
94 posts
0 likes
Member
Posted Mon Oct 26th 02:52

Ok, thanks for pointing this out. This was actually a small bug still in the software. It would correctly exclude devices that are not exposed, but wouldn't do so for scripts, scenes and automations.

I just released an emergnecy patch to v2.3.4 that resolves this. Upgrade the app and it should begin working fine.

Thanks for your patience while I got this fixed.

mjoshd
Oct 2026
7 posts
0 likes
Member
Posted Mon Oct 26th 13:04

Hi Matt, I just wanted to let you know that the latest version is excluding automtions, scripts, and scenes as desired.

Thank you very much for taking the time to work with me, understand the issue I was encountering, and for finding and fixing the bug so quickly!

You are an amazing developer and with the latest patch Sophia is exceeding expectations of how well a fully local voice assistant can perform.

Thanks again for your dedication and for creating Sophia!

Regards, Josh

Quick Reply

You must be logged in to reply to this thread.

Login Register