Thanxs Colin, I would have thought as HomeSeer is doing updates that they would want there Beta community to be aware of Bugs/Issues. Also I would have expected that HomeSeer would want their Beta community to collect the same types of data so that we (collectively) don't waste each other's time with non-pertinent information, so that when the software folks are trying to determine if their fix(s) are effective and corrective, call me simple but being from hardware/software industry having folks simply trying and reporting anomalies/failures is kind of shotgun and hoping that you fixed it rather than inserting latent failures that materialize at later time due combination of situations/events. Mike
Announcement
Collapse
No announcement yet.
Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423
Collapse
X
-
Computer: 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.
-
Originally posted by MNB View PostThanxs Colin, I would have thought as HomeSeer is doing updates that they would want there Beta community to be aware of Bugs/Issues. Also I would have expected that HomeSeer would want their Beta community to collect the same types of data so that we (collectively) don't waste each other's time with non-pertinent information, so that when the software folks are trying to determine if their fix(s) are effective and corrective, call me simple but being from hardware/software industry having folks simply trying and reporting anomalies/failures is kind of shotgun and hoping that you fixed it rather than inserting latent failures that materialize at later time due combination of situations/events. Mike
Comment
-
Well, its 17:25 and I have a message "HS3 has stopped working" looking at my resource Monitor CPU remained within the ~1-5% range whilst Working Memory is 161,440 (KB) so.. memory leak is not the issue.
I've attached my Windows Event stuff for someone to review/advise.
This looks like what I saw yesterday when I couldn't get HS3 to restart. I was able to get HS3 restart at 16:04 and let's cross ones fingers.
@Rich any suggestions? MikeAttached FilesComputer: 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
-
@Colin and @Monk, I tried the link, had to get logon... but looking for Homeseer as keyword, I only found 265 bugs of which only ~29 are this year.
What's interesting is there is a Memory Leak bug that was reported 1/16/17. I would have thought that a number of Beta anomalies would have also been logged (typical for Alpha and Beta testing) but they seem to be missing, am I missing something? MikeComputer: 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
-
With build 383 I don't have any more reports of leaks. With the discovery of Bitdefender causing crashes, they have stopped if Bitdefender has been disabled.
So in your case, it may be an isolated issue. What I would do is try and run your exact system on another PC, just copy the HS folder. This will rule out some OS or hardware issue.
Originally posted by MNB View Post@Colin and @Monk, I tried the link, had to get logon... but looking for Homeseer as keyword, I only found 265 bugs of which only ~29 are this year.
What's interesting is there is a Memory Leak bug that was reported 1/16/17. I would have thought that a number of Beta anomalies would have also been logged (typical for Alpha and Beta testing) but they seem to be missing, am I missing something? Mike
Comment
-
@Rich, belay my email.. (Compressed it was 460 MB in size) obviously too large as an attachment. What made Bitdefender crash HS3? As I'm using Windows defender could there be something similar component?
I agree with you that .383 is not currently exhibiting memory leaks but obviously there must be something else that is stressing. Looking at my Event file (txt) I notice that Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll what does this have to do with HS3? I believe it has something to do with .NET is there something that I can do? MikeLast edited by MNB; November 13, 2017, 08:58 PM.Computer: 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
-
Bitdefender is inserting itself into the network sub system to monitor traffic and that appears to be messing with .NET. We run Windows Defender here and have never had an issue with that, so I don't believe that is your issue.
The faulting DLL is a .NET dll so it looks .NET related. Maybe you can download the latest .NET from Microsoft and see if that helps. It should refresh all the .NET files.
https://www.microsoft.com/net/download/windows
Originally posted by MNB View Post@Rich, belay my email.. (Compressed it was 460 MB in size) obviously not too large as an attachment. What made Bitdefender crash HS3? As I'm using Windows defender could there be something similar component?
I agree with you that .383 is not currently exhibiting memory leaks but obviously there must be something else that is stressing. Looking at my Event file (txt) I notice that Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll what does this have to do with HS3? I believe it has something to do with .NET is there something that I can do? Mike
Comment
-
Rich, thanxs for the comeback. I'm assuming that I'm downloading .NET Core v2.0.2 SDK?
Update: Looking at the options again me thinks .NET Framework 4.7.1 is the correct one.. I feel like choosing the Red over the Blue Pill....Computer: 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
-
@Rich, I downloaded and attempted to run .NET Framework 4.7.1 but I get a message that the installation will not occur because ".NET Framework 4.7.1 or a later update is already installed on this computer." more clues please
Looking a little further it looks like (looking a my Regedit) that I have;
On Windows 10 Fall Creators .NET Framework 4.7.1 - DWORD - 461308 which jives with the message above but it will not allow me to re-install. MikeLast edited by MNB; November 13, 2017, 09:34 PM.Computer: 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 rjh View PostWith build 383 I don't have any more reports of leaks. With the discovery of Bitdefender causing crashes, they have stopped if Bitdefender has been disabled.
So in your case, it may be an isolated issue. What I would do is try and run your exact system on another PC, just copy the HS folder. This will rule out some OS or hardware issue.
Comment
-
@Mike,
Maybe try to do a repair of the dot net which includes a reinstallation.
Microsoft .NET Framework Repair Tool
Looking at your logs above saw one plugin that stood out...
Log Name: Application
Source: Application Error
Date: 11/13/2017 5:40:59 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: LMBHomeSeer
Description:
Faulting application name: HSPI_PHLocation.exe, version: 3.0.1.109, time stamp: 0x59df1004
Faulting module name: mscorlib.ni.dll, version: 4.7.2556.0, time stamp: 0x59b83409
Disable this plugin maybe for a bit?Last edited by Pete; November 14, 2017, 06:45 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
@Gavin,
Have you tried to copy your Homeseer 3 directory out to a new installation of Homeseer 3?
One way too is just to
1 - copy out the Homeseer 3 directory. (while Homeseer 3 is off).
2 - build a new Windows 10 PC (even on old one)
3 - install Homeseer 3 new on new build (new).
4 - copy back up of Homeseer 3 over new build
5 - make sure that you either disable Bitdefender and install Windows Defender.
Many Windows 10 users are doing fine with current release of HS3 V.368. The other choice is to use a Lite version of Windows 7 (64bit) or utilize Windows 7 Embedded.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Faulting application name: HSPI_PHLocation.exe, version: 3.0.1.109, time stamp: 0x59df1004
Faulting module name: mscorlib.ni.dll, version: 4.7.2556.0, time stamp: 0x59b83409
Disable this plugin maybe for a bit?
Maybe try to do a repair of the dot net which includes a reinstallation.
Microsoft .NET Framework Repair Tool
Ah good, glad to see I'm being completely ignored - I'll just tell my server that the slowly creeping memory with .383 will go away on its own.
1. Delete your current HS3 directories and files,
2. Re-install v.368
3. Copy you working back-up over the newly re-installed v.368
4. Re-start HS3 to ensure that everything is working and then shut it down
5. Do the v.383 update
6. Re-start HS3 and monitor your CPU and Memory with Resource Monitor
Hopefully this will get your system working again and you can stop talking to your server, unless you want to? MikeLast edited by MNB; November 14, 2017, 10:08 AM.Computer: 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
-
Thought I would post an update of my observations on .383. This beta is probably the most memory stable version that I have seen in a long time. All functions that I have tested seem to work fine. HSTouch is responsive and stable for me. Event actions are fast with no noticeable delays.
Current Date/Time: 11/14/2017 8:53:30 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.383
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 1 Day 18 Hours 26 Minutes 44 Seconds
IP Address: 192.168.1.21
Number of Devices: 365
Number of Events: 201
Available Threads: 800
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
Enabled Plug-Ins
3.1.1.24385: Blue-Iris
3.0.0.40: EasyTrigger
5.0.0.58: Global Cache Pro
3.1.0.22: Sonos
3.0.6331.36036: UltraCID3
3.0.0.76: weatherXML
3.0.1.150: Z-Wave
Comment
-
@Mike,
Here had a lingering HS3 Linux plugin (Omni) which would continue to run after shutting down Homeseer and causing errors in the logs. Well too because it talked to a dead server.
Not sure what Rob did to the plugin on an update such that I wouldn't see this anymore.
So basically the attached file above is showing a crash with Homeseer (unexplained right now) with an application (plugin) trying to talk to a dead HS3 server and your plan of action is to repair your dot net stuff eh?
Yes here have more dependencies on serially connected devices (direct) and now a few network connected devices.
ZWave is remote via the LAN (but you need to back this up power wise).
1-Wire is based now on using the LAN. Old one wire was a 1-wire serially connected hub of sorts.
Test your stuff...IE: for an internet WAN or LAN dependency kill the internet or LAN connection and watch the plugin.
For a wireless dependency, kill the wireless and watch the plugin.
No plugin should debend or take down the Homeseer 3 server if it gets disconnected. This was an issue way back with Homeseer 2.
I am all at Gb here (managed switches) and have no real dependences on wireless (testing some tabletops which are Gb connected to Wireless connected and they work).
IE: X10, UPB are directly wired to the HS3 box. Z-Wave and Zigbee (for the OmniPanel) are wired serially to the OmniPanel.
The old HS2 ZTroller was a serial connection to the Homeseer 2 box. There is the built in Z-Wave GPIO card (mainline connection) or USB stick and then there is the ZNet ZWave connection.
The ZNet connection used more transport pieces (network) where as the GPIO card / USB stick plugged in to the HS3 box uses less pieces (well my box is in the basement here and the POE ZNet like box is in the attic).
802.11X wireless is still magical and you cannot predict the propagation of it. You can today add multiple Access Points for better throughput around your home. I have updated my wireless but yet have no automation dependencies on it. (I want sure bet automation here - that is me).Last edited by Pete; November 14, 2017, 10:44 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
Comment