feat: Add user-scoped state/entity API filtering#28
Open
adityastic wants to merge 1 commit into
Open
Conversation
adityastic
force-pushed
the
feature/state-api-filter
branch
2 times, most recently
from
7428a50 to
89da8c4
Compare
adityastic
changed the title
adityastic
force-pushed
the
feature/state-api-filter
branch
from
89da8c4 to
5c6d98f
Compare
Filter websocket state, entity/area/device registry, and REST states by role; harden setup for double-load and HA 2026.6 options flow; hide RBAC internal entities from restricted users; and drive frontend blocking from the per-user API. Co-authored-by: Cursor <cursoragent@cursor.com>
adityastic
force-pushed
the
feature/state-api-filter
branch
from
1fd6a8c to
56854ef
Compare
adityastic
changed the title
adityastic
force-pushed
the
feature/state-api-filter
branch
from
19081b9 to
56854ef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Filter websocket get_states, REST /api/states, and entity/area/device registry lists by RBAC role via a User.permissions wrapper, so restricted users never receive forbidden entities on Overview.
Includes deny_all allow-list optimization, role-based visibility cache, registry cache invalidation, HA 2026.6 permissions patch fix, rbac.js deny_all support, and unit tests.
Some examples from my HA setup:
User without permissions:
User with permissions:
The same applies to every room entity inside any auto generated per room overview dashboard
Related Issues:
#20