Hey Jon. Any way I can reach you directly? Alternatively, can you share here how you’ve discovered the OTA URL (shown in your blog post)? I’d like to explore that path to get the latest and future updates. Thanks!
Just a quick follow up on this, basically I discovered that due to the size of my HA deployment, and the fact the HA sends all state changes for all entities to all clients (regardless of whether the client uses the entities) was causing my NSPanels to choke. I have quite a lot of metering type sensors (water, power, bandwidth, etc.) which clock up lots of frequent updates.
My solution was to install a second instance of HA, and then use the Remote Home Assistant integration to only replicate over the entities that I use on the NSPanels.
Now my NSPanels are all super fast and responsive.
1 Like
Hi i plan to buy a NSPanel Pro 120. I dont plan to root or something, only want to use original app and new webview mode, to control HA.
Any problem these device? I read that 120 are really slow and not sleep or disable the display in browser mode. these problems still exist?
Hi Ben,
I’ve noticed that quite often the camera strem got broken and doesn’t heal itself. What kind of optimization can be done to the ui to load faster and lighter?
Also I was thinking about connecting them via ethernet/POE.
Where’d you find this information from? I also have energy meters that update every 10 seconds so I’m wondering if this is something worth doing on my end
I discovered this myself.
My NSPanels were very slow, often not loading entity icons, and things like my weather forecast wouldn’t update…
In the HA logs, I could see entries like this:
'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; ’
Since I moved to having a second HA instance to proxy only the entities that NSPanel dashboards need, everything is very fast now.
Very interesting, I’ve never seen that error message so maybe not worth it for me. The response times on my NSPanels are about 1 second so it’s not terrible but it’s nowhere near instant either. What are you response times now when turning on a light (assuming it’s local control)
Mine are now the same as using my the HA app on my phone so as instant as HA gets!
The errors only occur when it gets really bad - but I think it’s a gradual degradation upto that point.
It’s easy to test for yourself, if you have the resources, just spin up a new HA instance and connect the panel to that. Either create some dummy test entities, or use Remote Home Assistant.
I’m having a slowness problem and thinking about implementing this solution but I’m a little confused by the remote home assistant integration. Did you create another instance and on the new instance specify the entities to include? And there is basically no configuration on the main instance?
Quite interesting discovery. I not have the error in the logs, but the app on the nspanel is slow. Time ago was faster, but i’m adding a lot of sensors.
My ha instance is hosted on a Rpi4, with HA os, so it’s not easy to create another instance.
As a test, would be useful to open the app via web browser? In this way i think that the client receives only the minimum needed sensors, and if it’s fast, the problem is confirmed.
How it works, is that the Remote Home Assistant has two components:
-
a server component (installed on your original HA), it has no configuration, you just install it as integration.
-
a client component (installed on your new proxy HA), it has lots of configuration options and you can choose to include (or exclude) entities individually or by domain.
I actually include everything in the light, switch, fan and cover domains. As there aren’t actually that many entities and they don’t change very option. The sensor and binary sensor domains are where the big difference is achieved, I have lots of sensors which update often and the only ones my NSPanels actually need are temperatures!
I hope that helps.
Actually all clients receive all updates, I believe the underlying API works that way.
So on my NSPanels the performance problem was the same whether I used the HA app or browser, in my case I use Fully Kiosk Browser anyway.
That helps a lot. I played with it last night after spinning up a home assistant vm. The nspanel are definitely faster! Adding each entity is driving me nuts but when I used an entire domain it started moving slowly. I’m going to play around more today. This is going to help me a lot since I have tablets around the house and 3 nspanels and I wanted to add more.
1 Like
Guys I lost a bit the logic of your method.
Also my NSPanel is a bit slowly, but I didn’t get your solution…
I found that it was only my sensors domain that caused the problem, I included everything from light, switch, fan, etc. though obviously this all depends on your own setup.
In terms of managing the entities I moved to YAML config for Remote Assistant, much easier to manage than the interface.
Absolutely. I tried the UI for about 5 mins and switched to YAML. I couldn’t deal with the UI for this
I’m going to try and include all groups and lights and see what happens.