www.homeseer.com    
 

Go Back   HomeSeer Message Board > HomeSeer Products & Services > HomeSeer Help

HomeSeer Help Help, How-to's and Documentation

Reply
 
Thread Tools Display Modes
  #1  
Old July 4th, 2018, 11:58 AM
Al_M Al_M is offline
Seer
 
Join Date: Aug 2016
Location: Kansas City, USA
Posts: 20
HomeTroller SEL (Linux) Crashed — Out of Memory

My HomeTroller has been running rock solid for about 2 years.

Yesterday I was performing a config backup and during the process I inadvertently deleted the file in my downloads folder before it got a chance to complete. The only other thing that I did was downloaded and installed the HSBuddy plugin (just prior to the backup).

Next thing you know the web UI locked up. I could not get any response via the Web UI (no navigation, refresh did nothing). So I logged in via SSH and ran the top utility. I could see that almost all the memory was being used. About 3.5 GB out of 4.0 GB was used.

So I issued a reboot command via SSH and the unit rebooted. Memory usage was back to a reasonable amount (around 800-900MB).

Eight or so hours later, same thing happened. Web UI locked up solid again. Logged in via SSH ran top to confirm almost all memory used again and rebooted. I then disabled and uninstalled HSBuddy.

I'm not sure if the anomaly was due to HSBuddy or the fact I interrupted the Config backup process...

Now I am monitoring the memory usage. HomeSeer consistently reports between 80MB and 100MB usage. (via the System Information page) The Plugin Memory Used is blank for whatever reason. The Linux top utility shows the 6 largest users of memory which probably matches up with HomeSeer and my 5 enabled plugins:

************************************************************
top - 10:44:29 up 2:05, 1 user, load average: 0.16, 0.17, 0.16
Tasks: 117 total, 1 running, 116 sleeping, 0 stopped, 0 zombie
%Cpu(s): 7.8 us, 1.7 sy, 0.0 ni, 89.6 id, 0.7 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem: 4040048 total, 839376 used, 3200672 free, 135660 buffers
KiB Swap: 0 total, 0 used, 0 free. 282864 cached Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1369 root 20 0 142144 96788 23108 S 10.3 2.4 8:49.96 mono
1091 root 20 0 296240 90480 24320 S 6.6 2.2 9:33.61 mono
1370 root 20 0 82720 57020 16468 S 2.0 1.4 1:36.25 mono
1368 root 20 0 114224 70140 21840 S 1.7 1.7 1:12.11 mono
1373 root 20 0 76588 48148 18324 S 1.0 1.2 0:47.37 mono
1372 root 20 0 72256 48560 15764 S 0.7 1.2 0:38.30 mono
1 root 20 0 4460 3612 2556 S 0.0 0.1 0:03.81 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:01.83 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H

************************************************************ **

Any ideas as to what might have happened and/or more importantly how to keep it from happening again? I'm paranoid about the amount of memory now being used and not sure if the above values are normal or not. This morning I caught the memory usage over 1.1 GB (1100MB) and I rebooted again just to make sure it would go down, which it did. Down to around 600MB immediately after a reboot. It seems to settle to around the 800MB level. I'll try to see that it doesn't keep climbing over the next 24 hours.

Also, how can I identify the processes? The only unique identifiers are the PID column (in the partial top printout above).

Any help would be much appreciated.

***********************************************************
MESSAGE BOARD (copy/paste section below to message board posts)

Current Date/Time: 7/4/2018 10:53:03 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.435
Linux version: Linux hometrollerSEL 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 2 Hours 13 Minutes 23 Seconds
IP Address: 10.0.1.20
Number of Devices: 317
Number of Events: 77
Available Threads: 199
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
1.3.0.0: Device History
3.0.0.48: EasyTrigger
3.0.6.2: SDJ-Health
3.1.0.15: Sonos
3.0.1.190: Z-Wave

**UPDATE: After some further testing, I watched my Linux top display while performing several functions. I started disabled and enabled some plugins and watched the memory usage change accordingly.

Then performed a Config Backup and the memory usage shot up to 3.7 GB. Stayed there during the "Creating Backup" operation. Once the operation was complete, it remains there around 3.6 GB and did not decrease.

I waited about 5-10 minutes for it to decrease back to normal, but it did not. At that point I rebooted the HomeTroller (via the System > System Restart menu command) and after reboot the memory usage is down to around 640MB.

So I don't know, but I wonder if there is some bug with the Config Backup function in this version???

Last edited by Al_M; July 4th, 2018 at 01:02 PM. Reason: Update after config backup pegged memory again.
Reply With Quote
  #2  
Old July 5th, 2018, 09:43 AM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 15,430
Personally you can see more running HTOP and sorting the view on the Homeseer Mono plugins / Homeseer.

Install HTOP
1 - ssh to your box
2 - sudo apt-get install htop
3 - read the help for htop and configure it for your use with Homeseer 3.

Then I would shut down Homeseer 3 via the GUI == Tools-> System -> Shutdown Homeseer

and

SSH to the Homeseer box and manually run Homeseer from the command line inside of the Homeseer directory and watch it load.

1 - cd /usr/local/HomeSeer
2 - type ./go
3 - watch Homeseer start.
__________________
- Pete

Automator

HS3 Pro & Lite Edition Beta 3.0.0.4449

HS3 Wintel Touch | Ubuntu 16.04 64 bit | Oracle Windows Virtual Box ==> for Wintel only SAPI and HS3 plugins | Speech - Microsoft SAPI - Neospeech - Amazon Echo | Hardware | Haswell Intel iSeries 3 - 16Gb | Pine64 - 2Gb computers | Openpeak Intel Atom SoC tabletop touchscreens (15 HS tabletop tablets) | Touchscreens - Windows embedded POE connected |Light switches - X10,UPB, ZWave and Zigbee | Firewall - PFSense - 2 WAN plus 4 LAN interfaces | Network - Gb managed switches / POE WAP(s) | CCTV - Zoneminder IPHD cams - variety | Audio - Russound - AB8SS | Security - Leviton HAI Omni Pro 2 | Weather - Davis Vantage Vue - MeteoStick - WeeWx | 1-Wire - AAG, Midon and HB | OWFS - Mosquitto - Node Red - Python - RPi Stretch - OpenWRT
Reply With Quote
  #3  
Old July 6th, 2018, 02:58 PM
Al_M Al_M is offline
Seer
 
Join Date: Aug 2016
Location: Kansas City, USA
Posts: 20
Pete,

Thanks for the direction.

I installed HTOP and am using it now instead of TOP. The memory values are different between the two programs. Per HTOP the normal memory usage is around 600 MB (out of 3945 MB). Not bad at all, about 15%.

Then I started a Backup Config and watched one of the cores peg out at 100%. That's understandable and the memory hit about 2100 MB (53%) during the Backup operation. When the Backup Config completed, I saw the CPU drop back down to normal (around 10%), but the memory remained at 2100 MB. It looks like it just stuck there for 10 minutes or so at which point I followed your advice to shutdown HomeSeer and manually restart it from the SSH command line.

Below is the printout of the startup. Maybe you (or anyone else) can spot a problem. Any help would be appreciated.



============================================================ ===================

homeseer@hometrollerSEL:/usr/local/HomeSeer$ ./go
[sudo] password for homeseer:
HomeSeer Linux starting...
01:29:39:5049:[Database]->Opening (Mode=Read Only) up HomeSeer LOG database /usr/local/HomeSeer/Logs/HomeSeerLog.hsd
01:29:39:6288:[Startup]->Loading Settings
01:29:39:7357:[Startup]->Settings Loaded.
01:29:42:4154:[Startup]->
01:29:42:4160:[Startup]->************************************************************ ********************
01:29:42:4170:[Startup]-> HomeSeer version 3.0.0.435 Edition: HS3 Pro (SEL) Starting Now
01:29:42:4176:[Startup]->************************************************************ ********************
01:29:42:4182:[Startup]->
01:29:42:4394:[Startup]->Creating Class Objects...
01:29:42:4414:[Startup]->COM port classes started.
01:29:42:4440:[Startup]->Application interface class started.
01:29:42:4516:[Startup]->Web server class started.
01:29:42:4527:[Startup]->E-Mail SEND class started.
01:29:42:4533:[Startup]->E-Mail RECEIVE class started.
01:29:42:4566:[Startup]->Plug-In Interface class started.
01:29:42:4582:[Startup]->Local voice recognition class started.
01:29:42:4610:[Startup]->Database SAVE process started.
01:29:42:4613:[Startup]->Loading configuration file ...
01:29:42:4815:[Database]->Opening (Mode=Read Only) up HomeSeer database /usr/local/HomeSeer/Data/HomeSeerData.hsd
01:29:43:4699:[Database]->Loading Devices...
01:29:43:4857:[Load Config]->317 total devices loaded.
01:29:43:4885:[Load Config]->Loading Event Groups...
01:29:43:5125:[Load Config]->Loading Events...
01:29:43:7260:[Load Config]->77 total events loaded.
01:29:43:7264:[Load Config]->Loading COUNTERS...
01:29:43:7319:[Load Config]->Loading TIMERS...
01:29:43:7653:[Startup]->HomeSeer version is: 3.0.0.435
01:29:43:7659:[Startup]->Creating Speaker Client Interface Object...
01:29:43:7687:[Startup]->This version of HomeSeer is registered as a HS3PRO version.
01:29:43:8011:[Info]->Remote plug-in API interface started on port 10400
01:29:43:8015:[Startup]->Checking for available plug-ins
01:29:44:3904:[Plug-In]->Found plug-in: EasyTrigger, version: 3.0.0.48
01:29:44:8107:[Plug-In]->Found plug-in: SDJ-Health, version: 3.0.6.2
01:29:45:2264:[Plug-In]->Found plug-in: Device History, version: 1.3.0.0
7/6/2018 1:29:45 PM : Error in GetStringIniFile with section = and Key = diSonosPlayerType and Error = Object reference not set to an instance of an object
Exception in LOG of Sonos: Object reference not set to an instance of an object
7/6/2018 1:29:45 PM : Error in GetBooleanIniFile with section = Options and Key = MediaAPIEnabled and Error = Object reference not set to an instance of an object
Exception in LOG of Sonos: Object reference not set to an instance of an object
01:29:45:6781:[Plug-In]->Found plug-in: Sonos, version: 3.1.0.15
01:29:46:1086:[Plug-In]->Found plug-in: Z-Wave, version: 3.0.1.190
01:29:46:1098:[Startup]->Initializing Plug-Ins
Queuing plugin Z-Wave to load...
01:29:46:1341:[Plug-In]->Finished initializing plug-in Z-Wave
Queuing plugin SDJ-Health to load...
01:29:46:1384:[Plug-In]->Finished initializing plug-in SDJ-Health
Queuing plugin Device History to load...
01:29:46:1441:[Plug-In]->Finished initializing plug-in Device History
Queuing plugin Sonos to load...
01:29:46:1540:[Plug-In]->Finished initializing plug-in Sonos
Queuing plugin EasyTrigger to load...
01:29:46:1677:[Plug-In]->Finished initializing plug-in EasyTrigger
01:29:46:2186:[HSTouch Server]->Server started on port 10200
01:29:46:2442:[Startup]->HStouch server started, waiting for clients to connect.
01:29:46:3061:[Web Server]->Local IP address is: 10.0.1.20
01:29:46:3296:[Web Server]->Web Server started on port 80
01:29:46:3487:[Startup]->Start automation engine...Connecting to server at 127.0.0.1 with Instance = '' ...

01:29:46:3879:[Startup]->Initializing Speaker Client Interface
01:29:46:4157:[Speech]->Listening for remote speaker connections on port 10401
01:29:46:4280:[Database]->Opening (Mode=Read/Write) up HomeSeer Energy database /usr/local/HomeSeer/Data/Energy/Energy.hsd
Connecting to server at 127.0.0.1...
Plugin: EasyTrigger Instance: starting...
Connecting to server at 127.0.0.1...
7/6/2018 13:29:46.439 Trace Main.Main - >>>> Main.Main()
7/6/2018 13:29:46.727 Trace Main.Main - Device History starting up with arguments:
7/6/2018 13:29:46.748 Info Main.Main - Connecting to HS server at 127.0.0.1:10400 ...
7/6/2018 13:29:46.750 Trace Main.Connect - >>>> Main.Connect(127.0.0.1,1)
Connection attempt #1
Connecting to server at 127.0.0.1...
01:29:48:0371:[Info]->Plugin EasyTrigger has connected. IP:127.0.0.1:33654
Connected (HomeSeer API 3). Waiting to be initialized...
01:29:48:1136:[Starting Plug-In]->Initializing plugin EasyTrigger ...
01:29:48:1279:[Info]->Plugin Z-Wave has connected. IP:127.0.0.1:33651
Connected, waiting to be initialized...
01:29:48:1559:[Info]->Plugin SDJ-Health has connected. IP:127.0.0.1:33657
Connected, waiting to be initialized...
01:29:48:1765:[Info]->Plugin Sonos has connected. IP:127.0.0.1:33653
Connected, waiting to be initialized...
Jul-06 13:29:48 INFO EasyTrigger version 3.0.0.48
7/6/2018 13:29:48.183 Trace Main.Connect - <<<< Main.Connect=True
01:29:48:1842:[EasyTrigger]->INFO EasyTrigger version 3.0.0.48
01:29:48:1998:[Info]->Plugin Device History has connected. IP:127.0.0.1:33658
7/6/2018 13:29:48.200 Info Main.Main - Connected.
01:29:48:2899:[Startup]->Updater services starting...
01:29:48:2916:[Startup]->Starting Find service...
01:29:48:2981:[Startup]->Running the startup script Startup.vb
01:29:48:3523:[Starting Plug-In]->Plugin EasyTrigger started successfully in 238 milliseconds
01:29:48:5669:[Starting Plug-In]->Initializing plugin Z-Wave ...
01:29:48:5840:[Z-Wave]->InitIO called, plug-in version 3.0.1.190 is being initialized...
Z-Wave Plugin: OS Type is Linux
01:29:50:0149:[Z-Wave]->Database: Opening (Mode=Read Only) up HomeSeer database /usr/local/HomeSeer/Data/Z-Wave/Z-Wave2.db
01:29:50:8102:[Z-Wave]->Loading Z-Wave Network Objects...
01:29:50:8712:[Z-Wave]->2 total Z-Wave Network Objects loaded.
01:29:51:8295:[Z-Wave]->Loading Z-Wave Data Objects...
01:29:51:8359:[Z-Wave]->2 Networks were restored from the data in the database... Building data connections.
01:29:51:8379:[Z-Wave]->Network D645692A has 141 device data elements.
01:29:51:8676:[Z-Wave]->Network D9A92A20 has 48 device data elements.
01:29:51:8800:[Z-Wave]->189 total Z-Wave Data Objects loaded.
01:29:52:1238:[Startup]->Starting Event Scheduler...
01:29:52:1321:[Startup]->HSSentry is disabled in Setup, sentry will not be started.
01:29:52:1536:[Info]->Checking for updates...
update_control_file:/updates3/hs3linuxhs3.txt
01:29:52:1570:[Startup]->Scripting is OK and is now running Startup.vb
01:29:52:1797:[TTS]->Speak ():Welcome to Home-Seer
01:29:52:2838:[Info]->Latest update available is: 3.0.0.435
01:29:52:2853:[Info]->Latest BETA update available is: 3.0.0.454
01:29:52:2857:[Startup]->Start up complete.
Type 'shutdown' to shutdown HomeSeer

> 01:29:52:2846:[Info]->System connected to MyHS Service, waiting for acknowledge...
Playing WAVE 'temp.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
01:29:52:3632:[Info]->System connected to MyHS Service successfully with license ID XXXXX.
Jul-06 13:29:52 INFO Refreshing list of device's string triggers to monitor
01:29:52:6590:[EasyTrigger]->INFO Refreshing list of device's string triggers to monitor
Jul-06 13:29:52 INFO Found 0 device's string triggers
01:29:52:6703:[EasyTrigger]->INFO Found 0 device's string triggers
Jul-06 13:29:52 INFO Refreshing list of device's value triggers to monitor
01:29:52:6733:[EasyTrigger]->INFO Refreshing list of device's value triggers to monitor
01:29:52:8754:[Z-Wave]->0 event actions were loaded from HomeSeer.
01:29:52:8796:[Starting Plug-In]->Plugin Z-Wave started successfully in 4312 milliseconds
01:29:52:8814:[Starting Plug-In]->Initializing plugin SDJ-Health ...
Starting initializiation.
01:29:52:9076:[Z-Wave]->0 event triggers were loaded from HomeSeer.
Jul-06 13:29:52 INFO Found 4 device's value triggers
01:29:52:9488:[EasyTrigger]->INFO Found 4 device's value triggers
Jul-06 13:29:52 INFO Found 0 device's value conditions that need monitoring
01:29:52:9501:[EasyTrigger]->INFO Found 0 device's value conditions that need monitoring
Jul-06 13:29:52 INFO Refreshing list of schedule triggers to monitor
01:29:52:9537:[EasyTrigger]->INFO Refreshing list of schedule triggers to monitor
Jul-06 13:29:52 INFO Found 0 schedule triggers
01:29:52:9562:[EasyTrigger]->INFO Found 0 schedule triggers
Jul-06 13:29:52 INFO Refreshing list of random triggers to monitor
01:29:52:9673:[EasyTrigger]->INFO Refreshing list of random triggers to monitor
Jul-06 13:29:52 INFO Found 6 random triggers
01:29:52:9863:[EasyTrigger]->INFO Found 6 random triggers
Jul-06 13:29:52 INFO Refreshing list of device group value triggers to monitor
01:29:52:9919:[EasyTrigger]->INFO Refreshing list of device group value triggers to monitor
Jul-06 13:29:52 INFO Found 0 device group value triggers
01:29:52:9956:[EasyTrigger]->INFO Found 0 device group value triggers
01:29:53:0728:[SDJ-Health]->Version 3.0.6.2 Initialized.
Initializing done! Ready...
01:29:53:0738:[Starting Plug-In]->Plugin SDJ-Health started successfully in 192 milliseconds
01:29:53:0755:[Starting Plug-In]->Initializing plugin Device History ...
01:29:53:4163:[Z-Wave]->465 Simple AV Control Command Class Control Commands have been loaded successfully.
01:29:53:7280:[Z-Wave]->Z-NET (House): ============================================================ ==========
01:29:53:7293:[Z-Wave]->Z-NET (House): ----------------------------------------------------------------------
01:29:53:7313:[Z-Wave]->Initializing Z-Wave interface Z-NET (House) (HomeSeer Z-NET Ethernet) at 10.0.1.18, port 2001
01:29:53:7343:[Z-Wave]->Z-NET (House): ----------------------------------------------------------------------
01:29:53:7402:[Z-Wave]->Z-NET (House): The Z-Wave Command Execution Thread was Started or Restarted.
01:29:53:7643:[Z-Wave]->Z-NET (House): Z-Wave Ethernet at IP 10.0.1.18, connected to interface ok.
01:29:54:0187:[Z-Wave]->Z-NET (House): The Z-Wave API Execution Thread was Started or Restarted.
01:29:54:0305:[Z-Wave]->Z-NET (House): Getting node information from controller...
01:29:54:1690:[Starting Plug-In]->Plugin Device History started successfully in 1093 milliseconds
01:29:54:1710:[Starting Plug-In]->Initializing plugin Sonos ...
7/6/2018 1:29:54 PM : InitIO for Instance = found CurrentAppPath = /usr/local/HomeSeer
01:29:54:1951:[Sonos]->InitIO for Instance = found CurrentAppPath = /usr/local/HomeSeer
7/6/2018 1:29:54 PM : InitIO for Instance = found HS running on Linux = True
01:29:54:1985:[Sonos]->InitIO for Instance = found HS running on Linux = True
7/6/2018 1:29:54 PM : InitIO Called for Instance = and running on OS = Unix
01:29:54:2056:[Sonos]->InitIO Called for Instance = and running on OS = Unix
01:29:54:2072:[Sonos]->InitIO for Instance = found this plugin running on Linux = True
01:29:54:2113:[Sonos]->InitIO Called for Instance =
01:29:54:2991:[Sonos]->Registered SpeakerProxy
01:29:54:3891:[Sonos]->Sonos Plugin Initialized
01:29:54:3903:[Starting Plug-In]->Plugin Sonos started successfully in 219 milliseconds
01:29:55:3776:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 1 Set to 3844.44 (3844.44 Watts)
01:29:55:4998:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 2 Set to 3484.56 (3484.56 Watts)
01:29:56:0323:[Z-Wave]->Device: Basement Emergency Use Panel Watts 1 (Total) Set to 4305.36 (4305.36 Watts)
01:29:56:1279:[Z-Wave]->Device: Basement Emergency Use Panel Watts 2 (Total) Set to 3852.12 (3852.12 Watts)
01:29:56:2257:[Z-Wave]->Z-NET (House): Controller Manufacturer: Express Controls, ID=0x2, Type=0x5
01:29:56:2273:[Z-Wave]->Z-NET (House): Controller firmware version: 4.32
01:29:57:0844:[Z-Wave]->Z-NET (House): Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
01:29:57:0913:[Z-Wave]->Z-NET (House): Z-Wave Serial API version: 5
01:29:57:0944:[Z-Wave]->Z-NET (House): Z-Wave interface node ID: 1, Home ID: D645692A
01:29:57:1003:[Z-Wave]->Z-NET (House): Found 36 Z-Wave nodes in interface node ID 1 (Z-NET (House))
01:29:57:2282:[Z-Wave]->The interface's security support has been set.
01:29:57:2724:[Z-Wave]->Z-NET (House) Controller chip type is ZW050x.
01:29:57:2740:[Z-Wave]->Z-NET (House) Controller is static lib.
01:29:57:2756:[Z-Wave]->Z-NET (House) There is a SUC/SIS in the network.
01:29:57:2770:[Z-Wave]->Z-NET (House) is the SIS for the network.
01:29:57:2817:[Z-Wave]->Z-NET (House): ............................................................ ..........
01:29:57:2832:[Z-Wave]->Z-NET (House): .............................. FINISHED ..............................
01:29:57:2848:[Z-Wave]->Z-NET (House): ............................................................ ..........
01:29:57:9794:[Z-Wave]->Z-NET (Apartment): ============================================================ ==========
01:29:57:9838:[Z-Wave]->Z-NET (Apartment): ----------------------------------------------------------------------
01:29:57:9894:[Z-Wave]->Initializing Z-Wave interface Z-NET (Apartment) (HomeSeer Z-NET Ethernet) at 10.0.1.19, port 2001
01:29:58:0025:[Z-Wave]->Z-NET (Apartment): ----------------------------------------------------------------------
01:29:58:0301:[Z-Wave]->Z-NET (Apartment): The Z-Wave Command Execution Thread was Started or Restarted.
01:29:58:0419:[Z-Wave]->Z-NET (Apartment): Z-Wave Ethernet at IP 10.0.1.19, connected to interface ok.
01:29:58:3043:[Z-Wave]->Z-NET (Apartment): The Z-Wave API Execution Thread was Started or Restarted.
01:29:58:3056:[Z-Wave]->Z-NET (Apartment): Getting node information from controller...
01:29:59:6020:[Z-Wave]->Device: Basement General Use Panel Watts 2 (Total) Set to 292.32 (292.32 Watts)
01:29:59:6520:[Z-Wave]->Device: Basement General Use Panel Watts 2 (Total) Set to 292.32 (292.32 Watts)
01:30:00:4867:[Z-Wave]->Z-NET (Apartment): Controller Manufacturer: Express Controls, ID=0x2, Type=0x5
01:30:00:4883:[Z-Wave]->Z-NET (Apartment): Controller firmware version: 4.32
01:30:00:8400:[Z-Wave]->Z-NET (Apartment): Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
01:30:00:8415:[Z-Wave]->Z-NET (Apartment): Z-Wave Serial API version: 5
01:30:00:8428:[Z-Wave]->Z-NET (Apartment): Z-Wave interface node ID: 1, Home ID: D9A92A20
01:30:00:8442:[Z-Wave]->Z-NET (Apartment): Found 14 Z-Wave nodes in interface node ID 1 (Z-NET (Apartment))
01:30:00:8871:[Z-Wave]->The interface's security support has been set.
01:30:00:9074:[Z-Wave]->Z-NET (Apartment) Controller chip type is ZW050x.
01:30:00:9087:[Z-Wave]->Z-NET (Apartment) Controller is static lib.
01:30:00:9100:[Z-Wave]->Z-NET (Apartment) There is a SUC/SIS in the network.
01:30:00:9113:[Z-Wave]->Z-NET (Apartment) is the SIS for the network.
01:30:00:9148:[Z-Wave]->Z-NET (Apartment): ............................................................ ..........
01:30:00:9162:[Z-Wave]->Z-NET (Apartment): .............................. FINISHED ..............................
01:30:00:9175:[Z-Wave]->Z-NET (Apartment): ............................................................ ..........
01:30:09:8786:[Z-Wave]->************************************************************ *******************
01:30:09:9643:[Z-Wave]-> STARTUP COMPLETE: All configured interfaces were successfully initialized.
01:30:09:9670:[Z-Wave]->************************************************************ *******************
01:30:10:0548:[Z-Wave]->Device: Apartment General Use Panel Watts 1 Set to 25.68 (25.68 Watts)
01:30:10:1823:[Z-Wave]->Device: Apartment General Use Panel Watts 1 Set to 25.68 (25.68 Watts)
01:30:13:8387:[SDJ-Health]->PEData read sucessfully from child device #110
01:30:14:3535:[SDJ-Health]->PEData read sucessfully from child device #111
01:30:14:5109:[SDJ-Health]->PEData read sucessfully from child device #112
01:30:14:7178:[SDJ-Health]->PEData read sucessfully from child device #113
01:30:14:9072:[SDJ-Health]->PEData read sucessfully from child device #114
01:30:15:0906:[SDJ-Health]->PEData read sucessfully from child device #115
01:30:15:3208:[SDJ-Health]->PEData read sucessfully from child device #116
01:30:15:5597:[SDJ-Health]->PEData read sucessfully from child device #117
01:30:15:7725:[SDJ-Health]->PEData read sucessfully from child device #118
01:30:15:9440:[SDJ-Health]->PEData read sucessfully from child device #119
01:30:16:1171:[SDJ-Health]->PEData read sucessfully from child device #120
01:30:16:2701:[SDJ-Health]->PEData read sucessfully from child device #121
01:30:16:4793:[SDJ-Health]->PEData read sucessfully from child device #122
01:30:16:6688:[SDJ-Health]->PEData read sucessfully from child device #123
01:30:16:8534:[SDJ-Health]->PEData read sucessfully from child device #221
01:30:17:1093:[SDJ-Health]->PEData read sucessfully from child device #222
01:30:17:3560:[SDJ-Health]->PEData read sucessfully from child device #223
01:30:17:5605:[SDJ-Health]->PEData read sucessfully from child device #69
01:30:19:2304:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 1 Set to 3858.12 (3858.12 Watts)
01:30:19:3602:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 1 Set to 3858.12 (3858.12 Watts)
01:30:19:5360:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 2 Set to 3500.76 (3500.76 Watts)
01:30:19:5796:[Z-Wave]->Device: Apartment Emergency Use Panel Watts 2 Set to 3500.76 (3500.76 Watts)
01:30:20:8317:[Z-Wave]->Device: Exterior Patio Relative Humidity Set to 53 (%)
01:30:20:8341:[Event]->Event Trigger "Calculations - Temp & Humidity Average Outdoor Humidity"
01:30:20:8346:[Event]->Running script statement immediately: &hs.setDeviceValueByRef(326, ((hs.deviceValue(370)+hs.deviceValue(38))/2), True)
01:30:20:9601:[Z-Wave]->Device: Exterior Patio Temperature Set to 93.6 (F)
01:30:20:9626:[Event]->Event Trigger "Calculations - Temp & Humidity Average Outdoor Temp"
01:30:20:9630:[Event]->Running script statement immediately: &hs.setDeviceValueByRef(279, ((hs.deviceValue(368)+hs.deviceValue(430))/2), True)
01:30:21:6091:[Z-Wave]->Z-NET (House): Wake-Up Notification Processing for Node 41 (Exterior Patio MultiSensor)
01:30:23:7805:[Z-Wave]->Starting Z-Wave Polling for Network D645692A...
01:30:25:9946:[Z-Wave]->Device: Basement Emergency Use Panel Watts 1 (Total) Set to 3962.64 (3962.64 Watts)
01:30:26:0738:[Z-Wave]->Device: Basement Emergency Use Panel Watts 1 (Total) Set to 3962.64 (3962.64 Watts)
01:30:26:1973:[Z-Wave]->Device: Basement Emergency Use Panel Watts 2 (Total) Set to 3535.44 (3535.44 Watts)
01:30:26:2642:[Z-Wave]->Device: Basement Emergency Use Panel Watts 2 (Total) Set to 3535.44 (3535.44 Watts)
01:30:27:0963:[Z-Wave]->Z-NET (House): Z-Wave Wake-Up 'No More Info' Notification sent to Node 41(Exterior Patio MultiSensor).
01:30:27:8894:[SDJ-Health]->Found existing battery database.
01:30:28:1037:[Z-Wave]->Starting Z-Wave Polling for Network D9A92A20...
01:30:28:8098:[SDJ-Health]->Polling devices stopped.
01:30:28:8600:[SDJ-Health]->Activity Checking started.
01:30:29:4523:[Z-Wave]->Device: Basement General Use Panel Watts 1 (Total) Set to 117.12 (117.12 Watts)
01:30:29:5632:[Z-Wave]->Device: Basement General Use Panel Watts 1 (Total) Set to 117.12 (117.12 Watts)
01:30:29:6362:[Z-Wave]->Device: Basement General Use Panel Watts 2 (Total) Set to 115.44 (115.44 Watts)
01:30:29:7138:[Z-Wave]->Device: Basement General Use Panel Watts 2 (Total) Set to 115.44 (115.44 Watts)
01:30:31:9011:[Z-Wave]->Device: Basement Safe Room Relative Humidity Set to 45 (%)
01:30:35:3853:[Event]->Event Trigger "Humidity Control Relative Humidity Set Point"
01:30:35:3931:[Event]->Running script statement immediately: &hs.setDeviceValueByRef(434, ((hs.deviceValue(279)*0.5)+hs.deviceValue(432)), True)
01:30:36:4200:[Z-Wave]->Device: Apartment General Use Panel Watts 2 Set to 6.96 (6.96 Watts)
01:30:36:4454:[Z-Wave]->Device: Apartment General Use Panel Watts 2 Set to 6.96 (6.96 Watts)
01:30:36:6524:[Z-Wave]->Device: Apartment General Use Panel kW Hours 2 Set to 0.473 (0.473 kW Hours)
Reply With Quote
  #4  
Old July 6th, 2018, 11:26 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 15,430
Here is one error when booting...

01:29:44:3904:[Plug-In]->Found plug-in: EasyTrigger, version: 3.0.0.48
01:29:44:8107:[Plug-In]->Found plug-in: SDJ-Health, version: 3.0.6.2
01:29:45:2264:[Plug-In]->Found plug-in: Device History, version: 1.3.0.0
7/6/2018 1:29:45 PM : Error in GetStringIniFile with section = and Key = diSonosPlayerType and Error = Object reference not set to an instance of an object
Exception in LOG of Sonos: Object reference not set to an instance of an object
7/6/2018 1:29:45 PM : Error in GetBooleanIniFile with section = Options and Key = MediaAPIEnabled and Error = Object reference not set to an instance of an object
Exception in LOG of Sonos: Object reference not set to an instance of an object


01:29:45:6781:[Plug-In]->Found plug-in: Sonos, version: 3.1.0.15

01:29:46:1086:[Plug-In]->Found plug-in: Z-Wave, version: 3.0.1.190
01:29:46:1098:[Startup]->Initializing Plug-Ins

Disable your Sonos plugin. Maybe update it or reinstall it? This may not be the reason your HS3 abends.

I do not utilize the Sonos plugin but it might be better to post this issue under the Sonos plugin author section.

Here currently running (on two machines).

- Ubuntu 16.04 64 bit

HS3Pro:~# uname -a
Linux ICS-HS3Pro 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

- Mono

HS3Pro:~# mono -V
Mono JIT compiler version 5.12.0.226 (tarball Thu May 3 09:48:32 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: supported, not enabled.
GC: sgen (concurrent by default)

Homeseer 3 Pro and Lite V.435 - your post has me updating today to V.449 on the HS3 Pro and Lite box.

Jul-07 12:27:54 PM Startup HomeSeer version 3.0.0.449 Edition: HS3 ZEE S2 Starting Now and
ZWave to 3.0.1.228

ZWave 3.0.1.216 - via RPi2 / GPIO ZWave dot me card - serial to ethernet to HS3.

Jul-07 12:46:22 PM Startup HomeSeer version 3.0.0.449 Edition: HS3 Pro Starting Now

For HTop you can do a filter and sort on mono processes and you will see HS3 and your plugins in separate processes.
Look what is using the most utilization. It could be many times how many triggers / events you are using with any one specific plugin.

If you configure HTop and save the configuration and sort on mono processes you will see a nice granular view of your Homeseer stuff.

IE: do an F2 to change display options like this; then do an F10 to save these options for your next session.

Name:  htop-display.jpg
Views: 47
Size:  57.0 KB

Here is a display which only shows Homeseer and plugins running after tweaking the HTOP configuration (F2 / F10)

Name:  htop.jpg
Views: 48
Size:  55.4 KB

Best to open multiple ssh terminal sessions (remotely) to watch all of this stuff. Easy. You can even open a terminal window to watch all of the network traffic based on open ports if you want to look for chatty kathy applications.

Code:
Pine64:~# netstat -a | more
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
Code:
Pine64:~# netstat -s
Ip:
    10324136 total packets received
    0 forwarded
    0 incoming packets discarded
    10324136 incoming packets delivered
    9785353 requests sent out
Icmp:
    3040 ICMP messages received
    5 input ICMP message failed.
    ICMP input histogram:
        destination unreachable: 113
        echo requests: 2
        echo replies: 2925
    3033 ICMP messages sent
    0 ICMP messages failed
    ICMP output histogram:
        destination unreachable: 104
        echo request: 2928
        echo replies: 1
Many of today's firewall's let you watch the internet chit chat with the devices you have on your home network.

Note doing debug can slow your system down. Logging every trigger / event /transaction by the second can also slow down your system.

If debugging or checking one plugin concentrate on that specific plugin. If you have a few dependencies on your internet connection then the internet connection can be a bottleneck to your automation. Newest firewalls can QOS traffic from particular devices on your network.

As far as I know the SEL is running Ubuntu 14.04 32 bit and old mono.

Currently utilize Webmin, SSH and integrated "shell in a box" to HS3 GUI for side stuff.

Probably migrating Homeseer boxes from Ubuntu 16.04 to Ubuntu 18.04 shortly.

Just moved Laptops over to Ubuntu 18.04 and like it.

Have been helping a UK Homeseer User who got a second SEL. He is updating the second SEL to newest Ubuntu 64bit and will be migrating his HS3 set up to that computer shortly.

Last edited by Pete; July 7th, 2018 at 02:12 PM.
Reply With Quote
  #5  
Old July 7th, 2018, 04:12 PM
Al_M Al_M is offline
Seer
 
Join Date: Aug 2016
Location: Kansas City, USA
Posts: 20
I went and updated the Sonos plugin. While updating I also noticed an update available for Device History, so updated that as well.
After a reboot I'm now showing 430 MB of memory usage.



That's down from an average usage of 650 MB before the two plug-ins were updated. So that's an improvement right off the bat.

Next, I waited about an hour, and still at around 430 MB memory usage. Now I run a Config Backup operation. Here is a shot of HTOP during the backup operation:



This understandable during the operation. But I would expect it to go down after the operation completes:



As you can see, it does not. In fact it increases even more to over 1800 MB. As I sit here writing this post, I'm keeping an eye on it as it continues to increase to 1897 MB.

There is something definitely wrong with this....now at 1902 MB....increasing still.

So I am looking into updating HS as you did Pete. But the web UI is reporting that the installed version (3.0.0.435) is the latest. The .454 BETA is available but I make it a point to never run betas, as I'm not a developer and this is my primary and only HA box. 449 is not an option for me? How did you get that version?
Attached Images
   

Last edited by Al_M; July 7th, 2018 at 09:19 PM. Reason: added missing attachment
Reply With Quote
  #6  
Old July 7th, 2018, 04:35 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 15,430
Yeah...1800 plus Mb isn't much. V435 was stable for me and I have not seen any memory utilization issues with my two HS3 boxes in the last year or so.

How did you get that version?

manually. Linux HS3 and updated versions have been stable. None of my updates over this past year have caused me any issues.

The wax and wane of memory utilization / CPU utilization is relating to triggers, events and scripts running.

The backup running may be leaking. Use it, shut down HS3 and restart it. Best back up is of the entire Homeseer directory while HS is shut down. I did the same when running Homeseer 2 in Windows. There are 3rd party plugins that will copy the entire directory in vivo.

If it goes up and keeps going up then you have a leaky script or event or plugin running. IE: if you by accident install a circular / endless loop script / trigger or event you will probably abend HS3. This can happen with an multiple checks and balances (nested loops). Here do not use the configuration back up utils. Never have used them.

Here is my Zee2...

672M / 1.94G

HS3 Pro machine

5.48G / 15.6G

Here is my znet like RPi2 in the attic

163M / 973M


You can manually update your Homeseer version via SSH. Make sure that Homeseer is off.

Update it and reboot your computer.

On the Zee and HS3 Pro boxes there is an update script called updatehs.sh

You can run pieces of it to update or just type ./updatehs.sh 449 to update to version 449.

Pieces of the updatehs.sh are on the Zee2

-Pine64:/HomeSeer# cat updatehs.sh
sudo rm hslinux_zees2_3_0_0_$1.tar.gz
sudo rm hs3linuxhs3zees2.txt
sudo wget hxxp://homeseer.com/updates3/hs3linuxhs3zees2.txt
sudo wget hxxp://homeseer.com/updates3/hslinux_zees2_3_0_0_$1.tar.gz
sum=`md5sum hslinux_zees2_3_0_0_$1.tar.gz | awk '{print $1}'`
echo $sum
sudo tar xavf hslinux_zees2_3_0_0_$1.tar.gz
sudo chmod +x install.sh
sudo ./install.sh

xx=tt

manually above just change the $1 to version number...IE:

sudo wget hxxp://homeseer.com/updates3/hslinux_zees2_3_0_0_449.tar.gz
sudo tar xavf hslinux_zees2_3_0_0_449.tar.gz

Not sure what the SEL script looks like.

Make sure you make a backup of your homeseer directory while it is off.

If using Windows do this with WinSCP instead of the command line.

Here created a homeseer backup directory called:

/user/local/homeseerBU

after you copy the directory rename it to date and version of homeseer...

HomeSeer-V435-07072018

an off the side thing...

Noticed that Harris Oil is still around by you. Owner supported my gasoline purchases (habit) when driving my new Trans Am back in the 1970's or new Mustang convertible (driven by Harris Oil owners daughter back then). We would trade cars all of the time....

Last edited by Pete; July 7th, 2018 at 05:07 PM.
Reply With Quote
  #7  
Old July 8th, 2018, 12:28 PM
Al_M Al_M is offline
Seer
 
Join Date: Aug 2016
Location: Kansas City, USA
Posts: 20
Quote:
Originally Posted by Pete View Post
Yeah...1800 plus Mb isn't much. V435 was stable for me and I have not seen any memory utilization issues with my two HS3 boxes in the last year or so.

I understand that 1800 MB isn't much. But on my system that represents almost 50% usage. That combined with the fact that under normal operations usage is averaging 10-15% and the only time the memory utilization increases (and gets "stuck") by almost 4 times is during/after performing the Backup Config leads me to believe there is an issue.


Quote:
Originally Posted by Pete View Post
The wax and wane of memory utilization / CPU utilization is relating to triggers, events and scripts running.

I get it. I realize memory usage will be fluctuating and dynamic. That's why I'm trying to report average values.


Quote:
Originally Posted by Pete View Post
The backup running may be leaking. Use it, shut down HS3 and restart it. Best back up is of the entire Homeseer directory while HS is shut down. I did the same when running Homeseer 2 in Windows. There are 3rd party plugins that will copy the entire directory in vivo.

If it goes up and keeps going up then you have a leaky script or event or plugin running. IE: if you by accident install a circular / endless loop script / trigger or event you will probably abend HS3. This can happen with an multiple checks and balances (nested loops). Here do not use the configuration back up utils. Never have used them.

I'll keep an eye out for leaky scripts, although I don't believe that to be the case. It's possible I'm catching a script or event in progress during the backup, so I'll start performing the backups after shutting down HomeSeer.

The Backup Config function makes copies of three directories:

usr/local/HomeSeer/Config
usr/local/HomeSeer/Data
usr/local/HomeSeer/scripts -- (NOT Scripts)

These directories should be able to help me "rebuild" my setup incase anything ever happened, right? I mean I could wipe the entire SEL box, re-install the OS and HS3, then put these directories in the proper locations and I should be up and running?

I'm a big image/clone guy. I mostly use Macs and Windows (only because I have to for work). I've started messing with Linux on a couple of really old mac laptops for my kids to learn on. I've grown accused to CloneZilla to make exact bit-for-bit copies of these machines. Is there any reason I couldn't use that tool to clone my HomeTroller SEL box and use that image as a backup?


Quote:
Originally Posted by Pete View Post
On the Zee and HS3 Pro boxes there is an update script called updatehs.sh

Any ideas where I might find this script on a HomeTroller SEL PRO?


Quote:
Originally Posted by Pete View Post
sudo wget hxxp://homeseer.com/updates3/hslinux_zees2_3_0_0_449.tar.gz
sudo tar xavf hslinux_zees2_3_0_0_449.tar.gz

Do I need to manually download this from HomeSeer or will this command perform the download itself? (remember, just learning linux...)


Quote:
Originally Posted by Pete View Post
Make sure you make a backup of your homeseer directory while it is off.

Point noted. Actually makes more sense than doing it while HS3 is running!


Quote:
Originally Posted by Pete View Post
If using Windows do this with WinSCP instead of the command line.

I'm on a Mac. I prefer to use FileZilla and sftp. That should work, right? It's the quickest and easiest way I've found to snoop around the file system on the SEL and I've used it in the past to paste my script files in the scripts directory.


Quote:
Originally Posted by Pete View Post
Here created a homeseer backup directory called:

/user/local/homeseerBU

after you copy the directory rename it to date and version of homeseer...

HomeSeer-V435-07072018
So there is no reason that directory can't sit there along with the actual working directory? OK. Kind of a "grab it all" approach. I have plenty of drive space to accommodate or I suppose I can send it to my Synology NAS for storage. What about the /home/homeseer directory? Any other directories I should be backing up?

Thanks, I really do appreciate your help.
Reply With Quote
  #8  
Old July 8th, 2018, 12:51 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 15,430
Finding your issue relating to an increase in utilization can be like looking for a needle in a haystack and this can be related to a plugin, triggers and events, scripts and timing.

It is recommended to test out one plugin or script at a time. Dependencies between one plugin and another can cause you grief.

These directories should be able to help me "rebuild" my setup incase anything ever happened, right?

yes and no.

Here using two methodologies for sure bet DR recovery. One is a copy of the Homeseer directory and the other is a bit copy of the partition. In the Homeseer 2 days created small C drive lite Windows server partitions. Today with Homeseer 3 running in Linux do the same. You can automate the bit copy and directory copy.

That and typically archive the backups from the back up directory on the HS3 box to one of NAS boxes. You can also just mount NAS drives to a directory on your HS3 boxes using FSTAB.

Is there any reason I couldn't use that tool to clone my HomeTroller SEL box and use that image as a backup?

No it is whatever you are most comfortable with. A snapshot or image of the entire Linux drive works but is not really necessary as Homeseer 3 in Linux runs on any Linux with Mono installed on it. Here it is easy to snap shot an 8-16 Gb partition. HS3 Pro is running on a 120Gb SSD and would be a waste space to save an image of said partition. Here you take the Windows hat off and use the Linux hat for this sort of stuff. Even easier these days using a VM and saving it on a NAS or even running the VM from a NAS drive.

Off on a bit of a tangent (wrote the DIY here many years ago).

Here my newest NAS box is a custom job with an 8 drive NAS case, mITX board and an LSi 8 port raid card using NAS4Free. (4TB X 8). Its been fine now for a few years.

About two years ago helped a HS3 user build a similiar box for HS3 Pro, NAS, WeeWx, Media server and a couple of Oracle Windows VBs running on Ubuntu Linux Server.

There is another automation user that purchased a pallet of off lease servers and Cisco Switches and racks and has installed a one rack doo all in his basement. It is power hungry and sounds like a jet in idle in his basement today. (servers are multiple CPU and have 32Gb of RAM or more these days). He paid less than $1000 for the pallet and has sold stuff one by one such that what he has today he got for free and made a little money from his purchases. Low on the WAF when he installed a Cisco POE switch on top of his kitchen refrigerator temporarily. (pallet included a few Cisco POE switches, Dell servers et al).

It is a small tight build do all server. If you install multiple NICs to the box then you can also use it for PFSense (there are users doing this today).

Name:  nas2.jpg
Views: 20
Size:  7.7 KB

Name:  NAS.jpg
Views: 21
Size:  59.1 KB

The NAS runs BSD like PFSense. Main boot drive is a 32Gb fast SSD which is the same as PFSense.

mps0@pci0:1:0:0: class=0x010700 card=0x30201000 chip=0x00721000 rev=0x03 hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
class = mass storage
subclass = SAS
cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0



What about the /home/homeseer directory?

The /home/homeseer directory is just the user directory for the user homeseer.

A while back it did contain a "call home script". I never used the script.

Any other directories I should be backing up?

no. It really is much simplier than Windows.

no.

The meat of Homeseer resides in the /usr/local/HomeSeer directory. Many users put the HomeSeer directory in the /opt/HomeSeer place. Here put it in the root /Homeseer directory. Homeseer will run in any directory. Just make sure the scripts are not hard pointing to any particular directory.

Here create multiple users in Homeseer and the OS. IE: pete, homeseer.

I give these two users sudo rights and RW rights to the HomeSeer directory. Then I match the users in the HS3 GUI configuration.

Understood relating to your Windows and MAC experience. Here old these days (started to tinker in the 1980's).

Last edited by Pete; July 9th, 2018 at 03:18 PM.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Adding memory to HomeTroller S6 Pro pgovotsos HomeTroller™ 13 December 21st, 2017 03:49 PM
How do you set this up on Hometroller SEL with Linux mpovolo iTunes DAAP (3P) 9 August 15th, 2016 10:15 AM
Hometroller Zee S2 is running out of memory Paul32 HomeTroller Zee 10 February 4th, 2016 09:55 PM
Hometroller S3 virtual memory issue Ken LaCapria HomeTroller™ 9 January 19th, 2012 07:07 AM
Upgrade HomeTroller Memory MStan HomeTroller™ 3 July 9th, 2008 08:35 PM


All times are GMT -4. The time now is 04:06 PM.


Copyright HomeSeer Technologies, LLC