Thanks to everyone who contributed; your hard work is greatly appreciated!
I’m also able to launch the Home Assistant app only when include_all_entities is set to false. While this does address some issues, the real benefit would come from being able to enable that setting without problems.
Same issue here sadly. Certainly better with this solution even with include_all_entities = true but i feel it would be awesome if i could get it working with include_all_entities = false. I have 20+ presence sensors that are flooding websocket.
Haven't tested it yet, but uix (successor to card-mod) has also a mechanism to throttle state changes.
But not sure if this helps for things that aren't displayed in the frontend, too?
Hi. The problem with homeassistant-entity-filter-proxy and include_all_entities is that since the run.sh file has set -eu at the begining it will stop executing when any program returns non-zero exit code and in this lines
INCLUDE_ALL_ENTITIES=$(jq -er '.include_all_entities // false' "$OPTIONS_FILE")
TRANSPARENT=$(jq -er '.transparent // true' "$OPTIONS_FILE")
the jq program is given the argument of -e which returns exit code 1 if the output value was either false or null. The fix would be to remove the e argument from jq on the lines that work with true/false values.
Example:
INCLUDE_ALL_ENTITIES=$(jq -r '.include_all_entities // false' "$OPTIONS_FILE")
TRANSPARENT=$(jq -r '.transparent // true' "$OPTIONS_FILE")
And with that the program should run.
@fuslwusl could you implement this?
I see there was an update to v0.1.4 but sadly still same issue for me when adding access_token and setting include_all_entities to false which in logs returns
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
inspecting the github, it looks like the recent update was to the proxy.go file, to fix stuff with authorised endpoints:
EDIT - the run.sh adjustments do seem to work. I created a local version of the fuslwusl app to test.
Will post back if anything strange pops up.
Wow, I wish I came back here sooner. I got bored and vibe coded the same thing apparently: GitHub - GabrielGoldsteinAnidea/HA-Websocket-Stripper: Strip noisy websockets from dashboards · GitHub
It solves the problem! I have it running on a NSPanelPro 120, My TV, and Samsung Fridge. The NSPanel coudn't even respond to button presses. Works nice now.
FYI for anyone trying HA-WebSocket-Stripper Add-On/App be sure to add the IP of your Home Assistant instance (the box not the container) to your http -> trusted_proxies list in configuration.yaml otherwise you'll probably run into a 400 error.
Is anyone getting this error?
[info] Starting ha-ws-proxy
2026/06/24 20:39:09 fetching lovelace config from http://homeassistant.local:8123 ...
2026/06/24 20:39:09 failed to fetch lovelace config: lovelace/config request failed: {"id":1,"type":"result","success":false,"error":{"code":"config_not_found","message":"No config found."}}
I implemented the fixes for jq but it won't start due to not finding config?
FYI ha-paneld is getting support for entity filtering - I just installed the 0.9.2-rc2 version on my wall tablet and migrated from HA-WebSocket-Stripper over to their filtering. Seems to work just as well.
FYI I have been working through updates to a fork of HA-WebSocket-Stripper - I was relying on entity filtering on the client side, but discovered it was still generating a ton of network traffic that was impacting my 2.4Ghz network. I’ve ended up with it front ending (via nginx for TLS) both mobile (wifi & cell) and in-home panel dashboard sessions.
Updated docs are here: GitHub - davidcoulson/HA-Websocket-Stripper: Strip noisy websockets from dashboards · GitHub
No promises that swapping my add-on out for the upstream one will work, so maybe easier to start from scratch - although the overall approach is similar.
Open an issue if you run into and i’ll dig into it.