Just migrated from HS3 to HS4 and wish I hadn't.

[wpiman]

Well thanks. I've been having issues with event performance and if I disable the zwave plug-in -- no problems. It is a REAL DOG. Functionality has been replaced with a cool UI. Bad trade off.

I don't have any performance problems with events. I have a performance problem OPENING the events page. They trigger just fine. I can even open the events page in the HS Touch app and they are immediate. It is just with the web interface. I think HS checks the events to see if they are all valid and put a red flag next to events where devices are bad. I actually just open events through the search anyways so I barely even notice it.

That slow event loading page is REALLY the only HS4 issue I have. And it is relatively new. If you had upgraded last year, you would not have had any issue I don't think. My guess is it is related to the number of Zwave devices one has. I have issues with on the Google Home end. I think it might be my Google account.

And I am not sure I get your point. The default UI isn't that cool-- it just allows you to filter stuff better. It isn't really there to control the home, it is just there to allow you to configure things. It is mostly just set and forget.

I mostly control things from events, speech (alexa and Homebridge-- Apple watch siri is awesome), and Homeseer switches (double tap, etc).

[rmasonjr]

As a plugin developer, I can confirm. When the Events page opens, HS interrogates every single plugin an excessive number of times. If you have a large number of plugins, this is exponential.

I reported this on the github and made references here on the forums. They really need to somehow 'cache' the information from the plugins.

[rschein]

The ZWAVE UI is the culprit. My performance is when I try to edit the event and control a device it takes forever to bring up the controls. That the the add device does not work too swift either.. Remove seems to work.

[wpiman]

The ZWAVE UI is the culprit. My performance is when I try to edit the event and control a device it takes forever to bring up the controls. That the the add device does not work too swift either.. Remove seems to work.

I am running the latest Beta version of the Z-wave plugin- so I knowingly know it isn't without issues. I vaguely remember there being a seperate Zwave UI plugin at one point but I no longer see that.


"a plugin developer, I can confirm. When the Events page opens, HS interrogates every single plugin an excessive number of times. If you have a large number of plugins, this is exponential."

That makes sense. I think i have like 120 zwave devices or so. Or at least that many device numbers..

[rschein]

I'm on device 830+ so that may be the reason. Sounds like a poor design decision that worked on the small test case but does not scale up.[Not that I have not done that on other projects]

[randy]

I know this is practically useless info, but I am not seeing these issues with:

Device Count 4727
Event Count 1656
Z-Wave Devices 188
Plug-ins 30

Event page (either HS4 or legacy) takes 2-3 seconds to open. Xeon 6-core low power processor at 3.7ghz.

[kenm]

rmasonjr stated this may be related to the number of plugins, not devices or events.

Could it be a plugin that is very busy and therefore taking a long time to respond to HS requests for information?

[wpiman]

I know this is practically useless info, but I am not seeing these issues with:

Device Count 4727
Event Count 1656
Z-Wave Devices 188
Plug-ins 30

Event page (either HS4 or legacy) takes 2-3 seconds to open. Xeon 6-core low power processor at 3.7ghz.

What version of the HS4 plug in are you using? I saw this pretty recently.....

I don't see the CPU move much at all when I go to open it. I am on a ESXi VM on a 4-core XEONs. If I have events which are red (ie. reference deleted or no device_, it is much worse.

[randy]

What version of the HS4 plug in are you using? I saw this pretty recently.....

I don't see the CPU move much at all when I go to open it. I am on a ESXi VM on a 4-core XEONs. If I have events which are red (ie. reference deleted or no device_, it is much worse.

Z-Wave 3.0.11.0

[wpiman]

Z-Wave 3.0.11.0

I am on 4.1.0.3... If it is working, don't change.

[randy]

I am on 4.1.0.3... If it is working, don't change.

I’ve tried every V4 plug-in but had to immediately roll back due to problems. Each successive version has been better, but still breaks important things in my system.

[windracer]

I have a performance problem OPENING the events page.

That slow event loading page is REALLY the only HS4 issue I have. And it is relatively new.

This is still my only major as problem as well ... the slow events page really makes editing/changing events painful. I've started using the back button in my browser to go back to the events list after making changes to an event to avoid that "refresh tax."

[windracer]

This is still my only major as problem as well ... the slow events page really makes editing/changing events painful. I've started using the back button in my browser to go back to the events list after making changes to an event to avoid that "refresh tax."

Every time I hit events.html it takes 30 seconds to load, this includes trying to activate/deactivate events. Is there any chance this will be addressed?

Just found out about using _events.html and it works so much faster, so I'll be using the old HS3 interface when I need to make mass event changes.

[randy]

Hmmm…. I have 4768 Devices and 1650 Events. My event.html loads in 2 seconds.

Windows 10 pro
Supermicro SYS-5019C-L
Xeon E2176G CPU
32GB RAM.

[rmasonjr]

The new beta has a change labeled as:



Now, I dont know all the details of the case, but it might be a way to speed up processing under the hood of HS...

Per my post Energy Management Plugins above, I can tell you the calls to plugins is quite excessive when the events page is loaded.