Announcement

Collapse
No announcement yet.

Running HS3 as a service with NSSM stopped working after .435

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

    Running HS3 as a service with NSSM stopped working after .435

    I've been running HS3 with NSSM since I started using HS3 with no problems.


    Now, for reasons I don't understand, HS3 seems to get stuck and stops responding to event requests.


    Anyone else have this problem, or even better, a workaround?


    Thanks!




    Current Date/Time: 6/2/2018 8:02:05 PM
    HomeSeer Version: HS3 Standard Edition 3.0.0.435
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 0 Days 0 Hours 11 Minutes 21 Seconds
    IP Address: 192.168.1.13
    Number of Devices: 238
    Number of Events: 82
    Available Threads: 800
    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.22.0: BLOccupied
    3.0.0.47: EasyTrigger
    3.0.0.103: LutronCaseta
    3.0.1.190: Z-Wave

    #2
    I gave up fighting it.


    I now have HS3 running using the task scheduler and I turned on HSSentry.


    I think it's bizarre that every user has to go through hoops setting up a way to start on boot.

    Comment


      #3
      I upgraded to .435 from .318 almost a month ago and it works fine with Fire Daemon as before. So nothing different that way with .435 for me.

      Robert
      HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

      Comment


        #4
        Originally posted by langenet View Post
        I upgraded to .435 from .318 almost a month ago and it works fine with Fire Daemon as before. So nothing different that way with .435 for me.



        Robert


        Which W10 build are you on? I use NSSM for another product and am holding off on upgrading to W10 1803 because of it.


        Sent from my iPhone using Tapatalk

        Comment


          #5
          I run on windows 2016 server.
          I wouldn't suspect it being overly different in that respect.

          Robert
          HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

          Comment


            #6

            Comment


              #7
              No issues here...latest 2016 / .435 with AlwaysUp...

              Comment


                #8
                Originally posted by AgentGladstone View Post
                I've been running HS3 with NSSM since I started using HS3 with no problems.

                Now, for reasons I don't understand, HS3 seems to get stuck and stops responding to event requests.

                Anyone else have this problem, or even better, a workaround?
                HS3: .435
                NSSM
                W10 1803 (17134.48)

                All good.

                Comment


                  #9
                  Well now I'm wondering if I should switch back to running HS3 as a service.

                  Right now I have it set to run on startup and then trusting HSSentry to keep it running.

                  Anyone have a recommendation one way or another?

                  I wonder how the HomeTrollers do it.

                  Comment

                  Working...
                  X