Announcement
Collapse
No announcement yet.
Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423
Collapse
X
-
Originally posted by TechFan View PostCurrent Date/Time: 1/26/2018 10:18:25 AM
HomeSeer Version: HS3 Standard Edition 3.0.0.398
Linux version: Linux HomeTrollerZeeS2V2 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux System Uptime: 1 Day 6 Hours 28 Minutes 0 Seconds
IP Address: 10.x.x.x
Number of Devices: 259
Number of Events: 163
Available Threads: 389
HSTouch Enabled: True
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:
Enabled Plug-Ins
2.0.48.0: BLBackup
3.5.1118.14: HSBuddy
30.0.0.36: RFXCOM
3.0.5.6: SDJ-Health
3.0.1.173: Z-Wave
If you think it's related to upgrading your Z-Wave plugin, you can do one of two things:
1. Downgrade to the version you were running previously.
2. Upgrade to 184 which other users had reported good success on Windows systems.
I myself am running 184 on Linux and can't contribute any crashes to the Z-Wave plugin at this time, your mileage may very and of course reporting any issues benefits everyone.
PCK (Pete)
Comment
-
Originally posted by John245 View Post
From your reported support info, it looks like you also upgraded to 404 and added some non-plugin scripting on Jan 21? Can you isolate if one or the other may be causing your issues?
I can't help you on your scripting, I'm just looking at the correlation of crashes reported and the versions of HS3 with the plugin's enabled at the time of the reported crash.
PCK (Pete)
Comment
-
Originally posted by PCK View PostJohn,
From your reported support info, it looks like you also upgraded to 404 and added some non-plugin scripting on Jan 21? Can you isolate if one or the other may be causing your issues?
I can't help you on your scripting, I'm just looking at the correlation of crashes reported and the versions of HS3 with the plugin's enabled at the time of the reported crash.
PCK (Pete)
---
John
Comment
-
Pete.....I have been having crashes since upgrading from .365 to .368 and greater. I am now on .399, I have been on .402 and .404 all have crashed.
this is the latest crash.
1/26/2018 8:01:46 AM
Exception of type 'System.OutOfMemoryException' was thrown.
HomeSeer version: 3.0.0.399
Source: Scheduler
Target: Void .ctor()
Stack trace:
at Scheduler.StateObject..ctor()
at Scheduler.Web_Server.AcceptCallback(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.Socket.AcceptCallback(Object nullState)
at System.Net.Sockets.Socket.RegisteredWaitCallback(Object state, Boolean timedOut)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitO rTimerCallback(Object state, Boolean timedOut)
Current Date/Time: 1/26/2018 3:52:12 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.399
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 0 Days 7 Hours 44 Minutes 14 Seconds
IP Address: 192.168.1.184
Number of Devices: 589
Number of Events: 238
Available Threads: 600
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender
Enabled Plug-Ins
2.0.50.0: BLBackup
2.0.76.0: BLLock
2.0.54.0: BLOnkyo
1.0.3.0: BLShutdown
3.1.1.24385: Blue-Iris
3.0.0.43: EasyTrigger
3.0.0.25: ImperiHome
3.0.0.45: Kinect
3.0.0.45: Kinect
3.0.0.45: Kinect
3.0.0.28: MediaController
3.9.6431.26038: Modbus
3.1.0.22: Sonos
3.0.6551.16959: UltraGCIR3
3.0.6542.35207: UltraWeatherWU3
3.0.1.184: Z-Wave
Comment
-
Originally posted by John245 View PostI added the scripting to .368. Then I had the crash and decided to update to .404 as a lot of people were reporting problems on .368 and some of the people were thinking that it was related to the use of scripts.
---
John
There may be someone that can help take a look at your scripting if you can get it narrowed down to a few possible scripts causing the problem.
PCK (Pete)
Comment
-
Originally posted by wadesready View PostPete.....I have been having crashes since upgrading from .365 to .368 and greater. I am now on .399, I have been on .402 and .404 all have crashed.
this is the latest crash.
1/26/2018 8:01:46 AM
Exception of type 'System.OutOfMemoryException' was thrown.
HomeSeer version: 3.0.0.399
Source: Scheduler
Target: Void .ctor()
Stack trace:
at Scheduler.StateObject..ctor()
at Scheduler.Web_Server.AcceptCallback(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.Socket.AcceptCallback(Object nullState)
at System.Net.Sockets.Socket.RegisteredWaitCallback(Object state, Boolean timedOut)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitO rTimerCallback(Object state, Boolean timedOut)
Current Date/Time: 1/26/2018 3:52:12 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.399
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 0 Days 7 Hours 44 Minutes 14 Seconds
IP Address: 192.168.1.184
Number of Devices: 589
Number of Events: 238
Available Threads: 600
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender
Enabled Plug-Ins
2.0.50.0: BLBackup
2.0.76.0: BLLock
2.0.54.0: BLOnkyo
1.0.3.0: BLShutdown
3.1.1.24385: Blue-Iris
3.0.0.43: EasyTrigger
3.0.0.25: ImperiHome
3.0.0.45: Kinect
3.0.0.45: Kinect
3.0.0.45: Kinect
3.0.0.28: MediaController
3.9.6431.26038: Modbus
3.1.0.22: Sonos
3.0.6551.16959: UltraGCIR3
3.0.6542.35207: UltraWeatherWU3
3.0.1.184: Z-Wave
Not knowing your system memory size, maybe you are in fact running out of memory when possibly anti virus starts running? Just a guess but see if you can correlate time stamps with anything starting that might push system memory over the limit. Windows is a memory hog and with win 10, it needs a lot to even run by itself.
PCK (Pete)
Comment
-
Originally posted by PCK View PostNot knowing your system memory size, maybe you are in fact running out of memory when possibly anti virus starts running? Just a guess but see if you can correlate time stamps with anything starting that might push system memory over the limit. Windows is a memory hog and with win 10, it needs a lot to even run by itself.
PCK (Pete)
then windows10 shows 3 errors in the log the first one is.
The description for Event ID 1325 from source ASP.NET 4.0.30319.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unhandled exception occurred and the process was terminated.
Application ID: HS3.exe
Process ID: 6772
Exception: System.OutOfMemoryException
Message: Exception of type 'System.OutOfMemoryException' was thrown.
StackTrace: at Scheduler.StateObject..ctor()
at Scheduler.Web_Server.AcceptCallback(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.Socket.AcceptCallback(Object nullState)
at System.Net.Sockets.Socket.RegisteredWaitCallback(Object state, Boolean timedOut)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitO rTimerCallback(Object state, Boolean timedOut)
I've never noticed my memory going beyond 54%, usually it runs between 48% and 54%.
System Processes/Load:153 Processes, 23% Load Free / Total Physical Memory:4.30 GBytes / 8.00 GBytes (54% free) Free / Total Virtual Memory:4.94 GBytes / 9.25 GBytes (53% free) HomeSeer Memory Used:127 Mbytes Plug-In Memory Used:18 EXE Plug-Ins using 618 Mbytes
Comment
-
this is the third error in the windows10 log.
Faulting application name: HS3.exe, version: 3.0.0.399, time stamp: 0x5a3ad5e4
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x2cd1ce3d
Exception code: 0xe0434352
Fault offset: 0x001008b2
Faulting process id: 0x1a74
Faulting application start time: 0x01d39628003c10c7
Faulting application path: C:\program files (x86)\homeseer hs3\HS3.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 617ccfd8-3c62-4bb4-8158-9e2321959fbe
Faulting package full name:
Faulting package-relative application ID:
Comment
-
Originally posted by wadesready View Postthis is the third error in the windows10 log.
Faulting application name: HS3.exe, version: 3.0.0.399, time stamp: 0x5a3ad5e4
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x2cd1ce3d
Exception code: 0xe0434352
Fault offset: 0x001008b2
Faulting process id: 0x1a74
Faulting application start time: 0x01d39628003c10c7
Faulting application path: C:\program files (x86)\homeseer hs3\HS3.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 617ccfd8-3c62-4bb4-8158-9e2321959fbe
Faulting package full name:
Faulting package-relative application ID:
This is something Rich would be interested in I believe, stay tuned
PCK
Comment
-
Adding a single value under status graphics (Z-Wave device) resulted three consecutive times in an CPU usage of 99 % (80% HS) with as result a unresponsive system and a required restart.
Can someone reproduce this?
Current Date/Time: 27/01/2018 20:46:24
HomeSeer Version: HS3 Pro Edition 3.0.0.404
Operating System: Microsoft Windows 10 Pro - Work Station
System Uptime: 0 Days 0 Hours 4 Minutes 2 Seconds
IP Address: 192.168.2.11
Number of Devices: 1288
Number of Events: 108
Available Threads: 100
HSTouch Enabled: True
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender McAfee VirusScan
Enabled Plug-Ins
2.0.49.0: BLBackup
3.0.0.21: Buienradar
1.2.0.0: Device History
0.0.0.31: drhsIpPlugIn
3.0.0.37: EasyTrigger
3.0.0.1: HS iTunes
3.9.6431.26038: Modbus
3.0.1.109: PHLocation
2.0.0.0: SNMPMONITOR
3.1.0.20: Sonos
3.0.5917.35093: UltraLog3
3.0.6440.19101: UltraMon3
3.0.6159.37431: UltraNetatmo3
3.0.6490.28457: UltraSmartThermostat3
3.0.1.130: Z-Wave
Comment
-
Originally posted by John245 View PostAdding a single value under status graphics (Z-Wave device) resulted three consecutive times in an CPU usage of 99 % (80% HS) with as result a unresponsive system and a required restart.
Can someone reproduce this?
Bill
Current Date/Time: 1/27/2018 9:43:16 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.404
Linux version: Linux rock64 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux System Uptime: 7 Days 22 Hours 36 Minutes 1 Second
IP Address: 192.168.2.236
Number of Devices: 376
Number of Events: 202
Available Threads: 399
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:
Enabled Plug-Ins
2.0.38.0: BLLAN
2.0.93.0: BLRF
2.0.71.0: BLSpeech
1.2.2.0: Device History
3.0.0.43: EasyTrigger
5.0.0.58: Global Cache Pro
2.0.1.9: JowiHue
3.0.1.90: PHLocation
30.0.0.36: RFXCOM
3.0.5.7: SDJ-Health
3.0.6413.20219: UltraNetCam3
3.0.0.79: weatherXML
3.0.1.184: Z-Wave
Comment
-
Originally posted by bdickhaus View PostIt worked OK here. But I am running beta .184 of the Z-Wave plugin, and I am on Linux.
Bill
Current Date/Time: 1/27/2018 9:43:16 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.404
Linux version: Linux rock64 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux System Uptime: 7 Days 22 Hours 36 Minutes 1 Second
IP Address: 192.168.2.236
Number of Devices: 376
Number of Events: 202
Available Threads: 399
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:
Enabled Plug-Ins
2.0.38.0: BLLAN
2.0.93.0: BLRF
2.0.71.0: BLSpeech
1.2.2.0: Device History
3.0.0.43: EasyTrigger
5.0.0.58: Global Cache Pro
2.0.1.9: JowiHue
3.0.1.90: PHLocation
30.0.0.36: RFXCOM
3.0.5.7: SDJ-Health
3.0.6413.20219: UltraNetCam3
3.0.0.79: weatherXML
3.0.1.184: Z-Wave
HS creates standard during the inclusion of the Fibaro Universal Binary sensor a start value of -2147483648 and an end value of 2147483647 in the added status text status graphics.
This will cause that HS will become unresponsive (also .368). Changing this range will solve this issue.
---
John
Comment
-
Originally posted by John245 View PostRoot cause found.
HS creates standard during the inclusion of the Fibaro Universal Binary sensor a start value of -2147483648 and an end value of 2147483647 in the added status text status graphics.
[ATTACH]66200[/ATTACH]
This will cause that HS will become unresponsive (also .368). Changing this range will solve this issue.
---
JohnComputer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by MNB View PostJohn, pray tell what range values did you finally inputted to make it work? MikeHS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
Comment