Announcement

Collapse
No announcement yet.

Keyboard and Mouse Sensor plug-in - HS2 User Guide

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

    #16
    I haven't found a Hs log entry and I will try to get the time period after the
    kms server fails.
    I have the kms server running on the same machine like HS2.

    Regards, F.

    Comment


      #17
      Originally posted by Fischi View Post
      I have the kms server running on the same machine like HS2.
      did you mean kms client?
      if you want to run a sensor on your HS2 machine, add the following lines to Config/KMS.ini, then restart HS

      Code:
      [GENERAL]
      embeddedSensorEnabled=True
      this way the plugin will act as both a server and a client, and you won't have to run the KMS client on your HS2 machine

      Comment


        #18
        Thanks Spud,

        I wrote kms server but I mean the kms client.
        I will try your tip and add the two lines to the kms.config.

        Best regards,

        Fischi

        Comment


          #19
          Hi Spud,

          my \config\KMS.ini contents this entry:
          [DELAY]
          FRANK-PC-2=10
          localhost=10
          [GENERAL]
          embeddedSensorEnabled=True


          and there was a new device named localhost _98 created.
          Is this right?

          Regards, F

          Comment


            #20
            yes this is right
            you can delete the other device

            Comment


              #21
              Thanks Spud,
              I will see if the KMS fails after a time period again.
              I have another question:
              The KMS plugin only works for my mouse, not for the keypad, is this right ?

              Regards,
              Fischi

              Comment


                #22
                Originally posted by Fischi View Post
                Thanks Spud,
                I will see if the KMS fails after a time period again.
                I have another question:
                The KMS plugin only works for my mouse, not for the keypad, is this right ?

                Regards,
                Fischi
                no, it should work with both mouse and keyboard.
                what's your OS?

                Comment


                  #23
                  Spud,
                  The KMS plugin is working now for keypad and mouse since I added the
                  two lines to the \config\kms.ini and run the plugin as server and client.
                  Before it was running only for the mouse.
                  I have win7 professional.

                  Fischi

                  Comment


                    #24
                    Originally posted by PhTMan
                    I cannot location this KMS from the HS Updater.

                    Can you give more detailed directions how to DL the plugin?
                    I guess you are looking for a HS3 version of this plugin, right?
                    It's only HS2 right now, and until recently there was almost zero demand for this plugin so I didn't port it to HS3. I may reconsider

                    Comment


                      #25
                      Spud,
                      I have the keyboard/mouse monitor on my HS2 setup and have yet to switch to HS3. HS3 license bought, just waiting for some key plug ins that are finally coming about before upgrading.
                      You can count on me buying your keyboard/mouse monitor for HS3 if you develop it.

                      Ken J.

                      Comment


                        #26
                        FYI, I have ported the "Keyboard and Mouse Sensor" plug-in to HS3
                        see there: http://board.homeseer.com/showthread.php?t=172552

                        Comment


                          #27
                          Installed - doesn't work

                          I installed this on my HS2 setup and it will not detect the mouse/keyboard status properly on my remote PC. Everything looked proper on the server and client PC during install. The status on the remote PC shows as ON all the time with no physical activity on that PC.
                          Any ideas what's wrong.
                          Dick
                          HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

                          Comment


                            #28
                            Originally posted by RAM View Post
                            I installed this on my HS2 setup and it will not detect the mouse/keyboard status properly on my remote PC. Everything looked proper on the server and client PC during install. The status on the remote PC shows as ON all the time with no physical activity on that PC.
                            Any ideas what's wrong.
                            did you start the client as Administrator?
                            what does it say at the bottom of the client's window? i9s the status correct?

                            what's your inactivity delay? try to lower that down

                            Comment


                              #29
                              Dick
                              HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

                              Comment


                                #30
                                cool, what was the problem?

                                Comment

                                Working...
                                X