Announcement

Collapse
No announcement yet.

Homeseer SEL Pro crashing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Homeseer SEL Pro crashing

    This is a brand new out-of-the-box never used installation. Following Plugins installed: ZWave, Lutron Caseta, Nest, WeatherWU (all enabled), and disabled Yamaha, MyQ.

    Nest and WeatherWU are configured, Lutron has one Pico test event, and one Pro bridge configured, that works nicely. Nest has two thermostats, besides a single too-many-call API event on Nest side, works. WeatherWU pulls in some test data of temp and rain.

    Symptom is that with nobody logged in, Mono crashes after a couple of hours to two days. All Mono threats are gone. "go" does not restart HS, need to reboot. Mono crashes typically sometimes during the night with nobody using the Lutron Pico.

    On a freshly booted system, with nobody logged into WebUI, I am seeing both cores hovering around 35-40% on HSConsole.exe. I am seeing sometimes six of these HSConsole threads running, with one at 80% and the second at 40% CPU. Memory around 350MB.

    My console is the only inbound connection (sshd). There are three outbound connections to WU, Nest, and HS. HS on flat network on Juniper switch with DHCP from SonicWALL perimeter firewall. Lutron and Nest in same bcast domain.

    Essentially just got the box, and did a little lab setup on the weekend.

    HS3 version is 368. Box is licensed and registered.
    Last edited by sbrunner; December 13, 2017, 01:10 PM.

    #2
    Filtered for mono and main process:

    1 [||||||||||||||||||||||||||| 41.5%] Tasks: 63; 3 running
    2 [|||||||||||||||||||||||||| 39.5%] Load average: 0.93 1.03 1.02
    Mem[||||||||||| 373/3945MB] Uptime: 02:23:46
    Swp[ 0/0MB]

    PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
    1090 root 20 0 160M 91884 33036 S 85.4 2.3 1h35:03 mono HSConsole.exe
    1430 root 20 0 120M 86380 25780 S 0.7 2.1 0:36.92 /usr/bin/mono /usr/local/HomeSeer/HSPI_Nest.exe
    1364 root 20 0 106M 64516 24904 S 0.7 1.6 0:18.53 /usr/bin/mono /usr/local/HomeSeer/HSPI_LutronCaseta.exe
    1405 root 20 0 116M 70320 28160 S 0.0 1.7 2:19.97 /usr/bin/mono /usr/local/HomeSeer/HSPI_ZWave.exe
    1389 root 20 0 107M 68608 26384 S 0.0 1.7 1:01.82 /usr/bin/mono /usr/local/HomeSeer/HSPI_ULTRAWEATHERWU3.exe

    Within the first few minutes after reboot, CPU hovers between 1 - 3 %.
    Last edited by sbrunner; December 13, 2017, 01:57 PM.

    Comment


      #3
      Try disabling Auto Discover of Foscams. The Console process CPU usage was high until I did this on my SEL.

      Tools > Setup > Cameras

      Also recommend installing Webmin. Makes administering the SEL much easier.

      Comment


        #4
        I did not make a difference. What I am observing is that HSConsole races up consuming more and more CPU. It went from 2% to 134% on htop, consuming 60% on both cores, and almost 500MB, starting out with 130MB of memory use.

        Comment


          #5
          Do you have any recurring events enabled?
          HS4Pro Running on a Raspberry Pi4
          79 Z-Wave Nodes, 131 Events, 383 Devices
          Z-Wave, UPB, WiFi
          Plugins: EasyTrigger, weatherXML, OMNI, Z-Wave, Tuya, Device History
          HSTouch Clients: 3 Android, 1 Joggler

          Comment


            #6
            We have a couple of other users SEL crashing when using the Nest plugin. Can you disable this plugin and see the results.
            -Rupp
            sigpic

            Comment


              #7
              My SEL was crashing like that. By process of elimination turning plug-ins on and off I found it was the Nest plug-in. Mine works great when Nest is turned off. I hate that because I have a lot of Nest products and I haven't found a way to get any help to fix it. HS won't help because its not their product. No other way to get support except posting in forums. I think I lost $40 lol.

              Comment

              Working...
              X