FYI - Migration from HA WebSocket Stripper to native renderer entity filter

[davidcoulson]

For anyone else who was using HA WebSocket Stripper or some other proxy to limit entities - If you need to export the current list of permitted entities to load into ha-paneld run this from the dev tools console:

Object.keys(document.querySelector("home-assistant").hass.states).sort().forEach(e => console.log(e));

Then it's just a quick cut/paste job and some JSON formatting to create the file to load into ha-paneld.

[maxlyth]

Thanks for doing the work to post useful information but 0.9.2 is out and is designed to automatically learn needed entities so each panel learns only the entities it needs based on the dashboards it is asked to render.

I have finally retired my overcomplicated dual HA server infrastructure and while I initially used my hand curated entity list during testing I also retired that as redundant with the 0.9.2 release.

You can choose to leave auto-learning enabled or turn it on just long enough while you pin all the entities discovered as you exercise your dashboards. I opted for the latter option as my dashboards are fairly stable and don't want new entities automatically added to my panel subscriptions.

[davidcoulson]

I just updated to 0.9.2 and switched to auto entities. So far seems to work great but will tinker more tomorrow.

Would be great to have an auto-add entities open for minor dashboard adjustments. Wouldn't want it to remove anything automatically but if I change my dashboard without thinking and it needs an extra couple id be ok if it did it autonomously rather than drive a poor user experience.

[maxlyth]

The current automatic mode adds dependencies found in dashboard configuration or runtime hass.states access, but it does not fully guarantee “never remove”: removed static references can disappear on rescan, and unpinned runtime-only evidence expires after 30 days.

I’ve added an explicit add-only/auto-pin policy to the backlog; until then, pin anything that must persist.

[davidcoulson]

I am seeing "2 dynamic expressions not statically resolvable " in my entity subscription filter, although doesn't seem to have any impact. Is there a way to see what is not resolvable? I do have about a 10-15 "Dynamic expressions to exercise" entries, but can't tell which might be part of the two. My dashboard has a ton of card-mod CSS edits that are dependent on states so not really surprised so many get flagged.

[maxlyth]

Not currently — the count and list describe different sets, so the UI does not show which two expressions are unresolved.

I am treating that as a diagnostics bug: the list should mark the counted unresolved items and show a sanitised source and reason. It does not indicate that the live entity stream has changed.

[maxlyth]

v0.9.5-rc1 now lists each unresolved dynamic expression with its source location and a sanitised excerpt. Add-only automatic retention is still pending, so I’m leaving this open.