Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

[rjh]

Correct, I removed the queue status. There is now a queue for each plugin, but if it ever goes over 50 entries, you will get a log entry like:

"Warning", "Plugin XXXX is not processing events quickly enough is not responding, the HS event will not be processed, queue is full"

This is funny

Following Rich' ask I have updated HS3 to .383 and now the "plugin callback queue" is no longer listed....it disappeared from the overview that I normally accessed through Tools -> About Homeseer --> Display Details for Support (button half way down the page)


@Rich: I am still testing and monitoring but believe the changes in the way the plugin call back's are handled is working. Allthough I can no longer check the queue, the system seems more responsive. I'll keep you updated. with more results.

Is there another way to check the queue or has this now disappeared with the changes to separate threads?

[Tomgru]

Don't see plugins in Task Manager

Hey... am i nuts, or is this normal?

was checking taskman today, and noticed that i don't seen any of the plugins listed, although all are working fine.

for example, i used to see the harmony and itach cache plugs as background processes... now i don't see them at all.

[MNB]

@Rich,

I've been up and running for System Uptime: 1 Day 3 Hours 38 Minutes 55 Seconds. I'm noticing that my Working memory is creeping from its yesterday's snapshot.

Looking at Resource Metrics;

Todays Snapshot
CPU: 0-1%
Working Memory: 592,160-606,520 (KB)

Yesterday Start-up Snapshot
CPU: 0-2%
Working Memory: 126,00-139,000 (KB)

[Pete]

Posting an issue here that I see with Linux HS3 V.383 and seen with previous beta versions of Homeseer. Windows users are seeing the same thing.

Issue is: updater not showing currently installed versions

Note here I have the Omni Plugin installed and it doesn't show the version in the second image attached.

[randy]

Please try build 383. We moved each plugin callback to its own thread. This way if one plugin is not responding, all other plugins will continue to run. It will log a message with the plugin name of any plugin that is not responding to an event callback.

Rich;

When I run .383 or .384 I get the following every 2-4 minutes:

Nov-18 10:50:56 AM Warning Plugin Z-Wave is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:50:56 AM Warning Plugin PHLocation is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:50:56 AM Warning Plugin EasyTrigger is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:50:56 AM Warning Plugin BLStat is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:48:52 AM Warning Plugin Z-Wave is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:48:52 AM Warning Plugin PHLocation is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:48:52 AM Warning Plugin EasyTrigger is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:48:52 AM Warning Plugin BLStat is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:46:49 AM Warning Plugin Z-Wave is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:46:49 AM Warning Plugin PHLocation is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:46:49 AM Warning Plugin EasyTrigger is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:46:49 AM Warning Plugin BLStat is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:42:58 AM Warning Plugin Z-Wave is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:42:58 AM Warning Plugin PHLocation is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:42:58 AM Warning Plugin EasyTrigger is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.
Nov-18 10:42:58 AM Warning Plugin BLStat is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.

It is the same 4 plug-ins every time. There are over 1300 of these since 11/17. I rolled back to .379 Saturday morning just after the last log entry above to stop these log entries.

I am surprised that a HS plug-in would generate these warnings. Does this all seem correct? I have a VERY busy system.

[MNB]

Looking through my HS Log, I have only from yesterday. Mike

Nov-19 07:50:00 Warning Plugin BLGData is not processing events quickly enough is not responding, the HS event will not be processed, queue is full.

However, I had pages of the following;

Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 TimeofDay Script.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\Jon00UptimeHS3.vben
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 TimeofDay Script.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II Format.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\Jon00UptimeHS3.vben
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II Format.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 TimeofDay Script.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\Jon00UptimeHS3.vben
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 TimeofDay Script.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II Format.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\Jon00UptimeHS3.vben
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\Jon00UptimeHS3.vben
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II Format.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 GCalendar Events Script II.vb
Nov-19 07:50:47 Error Too many scripts running, cannot run script: C:\Program Files (x86)\HomeSeer HS3\scripts\HS3 TimeofDay Script.vb

Which normally I would simply restart the system again to get a clean HS Log, did not do that this time...

[TechFan]

There are a bunch of opensource linux utilities which graph utilization. A few have been posted here on this thread.

For Linux boxes here have mentioned the use of Webmin. Webmin has a few monitoring plugins which do graphing et al.

You can go easy button here by just configuring a remote ssh session with HTop on a remote desktop and leave it running just to look at Homeseer 3 Mono processes / CPU utilization and total RAM utilization.

Indeed. Been using Webmin for point in time views (works fine), but haven't looked at adding plugins for monitoring. HTop could also work, but only for manual checks it seems.

[Pete]

Yeah for Webmin there are metrics plugins that do graphing using RRTools.

With HTop you can direct the output to a text file and read it or to an HTML page via a bash script to watch it statically. There is also a Linux Scout program on steroids where you could see the separate mono processes on a Web page (thinking it is in the cloud).

With Homeseer you could do an automate manual about / help and then a screen scrap to variables thing.

The above said though here not seeing any crashes with Homeseer 3 running in Linux and just testing Homeseer 3 V383 and doing very light metrics (like manually looking at HTop once a day). (did not have any HS3 crashing / log errors with V.368).

A plugin similiar to Jon00's Windows Plugin in Linux would be nice.

[rjh]

This is fixed in build 387, which I just posted.

Posting an issue here that I see with Linux HS3 V.383 and seen with previous beta versions of Homeseer. Windows users are seeing the same thing.

Issue is: updater not showing currently installed versions

Note here I have the Omni Plugin installed and it doesn't show the version in the second image attached.

[rjh]

I just posted build 387 with some minor changes. I would like to release this next week.

https://forums.homeseer.com/showthread.php?t=181241

[rjh]

This means that the event queue for each of those plugins has exceeded 50 entries. This should never happen. I see one of the plugins is Spud's, let me work with him to see what he is doing in the event handler in his plugin. This will slow down a system for sure.

Looking through my HS Log, I have only from yesterday. Mike


However, I had pages of the following;


Which normally I would simply restart the system again to get a clean HS Log, did not do that this time...

[Pete]

Thank you Rich!!

Updated:

HomeSeer Version:HS3 ZEE S2 Edition 3.0.0.387 (Linux)
HomeSeer Version:HS3 Pro Edition 3.0.0.387 (Linux)

[randy]

This means that the event queue for each of those plugins has exceeded 50 entries. This should never happen. I see one of the plugins is Spud's, let me work with him to see what he is doing in the event handler in his plugin. This will slow down a system for sure.

The log entries I posted above were for

• Z-Wave
• PHLocation
• BLStat
• Easy Trigger

All 4 warnings occur once every 2-4 minutes for all 4. I understand that you are going to contact Spud, but what about the Z-Wave plug-in?

[rjh]

Good point, I did not even notice that. Will take a look.

I assume you have other plugins loaded, not just these 4?

The log entries I posted above were for

• Z-Wave
• PHLocation
• BLStat
• Easy Trigger

All 4 warnings occur once every 2-4 minutes for all 4. I understand that you are going to contact Spud, but what about the Z-Wave plug-in?

[jlrichar]

Update on .374

I now have ~ 39 days of uptime with v.374 with what appears to be a slow uptick in handles over time, and nothing else of concern. If not for applying windows updates I could probably get a lot longer uptime with this version. I do still have HSTouch disabled, as well as Foscam IP camera discovery disabled. Also, I have gone through all of my events to check that each one has no missing devices.

I think the issue I had was most likely related to event curruption. I still have a couple of events that do not run reliably even though they should and I have re-created from scratch a couple of times. Also making changes to the event trigger is known to break the event. Basically working with events seems to be quite buggy (sorry its the most accurate assessment). Maybe working on fixing these bugs in the events will uncover what is causing all the other issues? It is so much easier to test an event than to wait a week to see if some change affected memory usage. Worst case is you fix the event bugs, and it has nothing to do with memory leak\crashing.

Current Date/Time: 11/20/2017 11:37:00 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.374
Operating System: Microsoft Windows Server 2012 Standard - Server
System Uptime: 39 Days 13 Hours 24 Minutes 52 Seconds
IP Address: 192.168.1.105
Number of Devices: 708
Number of Events: 172
Available Threads: 200
Event Threads:2
Event Trigger Eval Queue:0
Event Trigger Priority Eval Queue:0
Device Exec Queue:0
Plugin Callback Queue:0
HSTouch Event Queue:0
Email Send Queue:0

Enabled Plug-Ins
3.2.0.5: APCUPSD
3.0.0.18: DirecTV
3.0.0.40: EasyTrigger
0.0.0.3: Garadget 3P
3.0.1.3: IFTTT
3.0.0.24: ImperiHome
1.1.3.1: JowiHue
2.17.0.18: MCSSPRINKLERSS
1.0.15132.98: MPower
3.0.0.28: Nest
3.0.1.83: PHLocation
3.0.0.5: Pushalot
0.0.0.34: Pushover 3P
30.0.0.35: RFXCOM
3.1.0.22: Sonos
3.0.6132.16975: UltraGCIR3
3.0.6440.19101: UltraMon3
3.0.0.40: UPBSpud
3.0.0.73: weatherXML
3.0.1.130: Z-Wave