I’ve got a 10 or so NSPanel Pros working pretty successfully, they have a separate dashboard setup which is pretty minimalist, however the performance can be sluggish and sometimes they don’t receive updates or even icons.
I tracked this down to loads of errors in the logs like 'Client unable to keep up with pending messages. Stayed over 1024 for 10 seconds. The system’s load is too high or an integration is misbehaving; ’
This is caused by all state updates being sent to all clients, the vast majority of which the NSPanels don’t need.
Is there anyway I can in someway restrict the states/events that go to a given client/user/dashboard.
I’ve dealt with the problem temporarily by reducing the update rate of some particularly noisy integrations, however this isn’t a long term solution.
Actually the same is true of just the standard app — the server sends ALL entity updates, regardless of whether the entities in question are visible in the dashboard. This wreaks havoc on mobile devices’ battery. Lovelace ought to set a serverside filter that’s appropriate for what is being displayed.