Announcement

Collapse
No announcement yet.

Not sensing

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

    Not sensing

    Included no problem but it doesnt seem to work. It shows motion sensed when I first included it but not since that point in time...


    Current Date/Time: 2/2/2018 6:50:10 PM
    HomeSeer Version: HS3 Standard Edition 3.0.0.399
    Operating System: Microsoft Windows 10 Home - Work Station
    System Uptime: 1 Day 23 Hours 22 Minutes 13 Seconds
    IP Address: 192.168.1.33
    Number of Devices: 175
    Number of Events: 9
    Available Threads: 200
    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
    3.0.0.25: ImperiHome
    3.1.0.0: LimitlessLED
    30.0.0.36: RFXCOM
    3.1.0.22: Sonos
    3.0.1.130: Z-Wave
    Attached Files

    #2
    It should have 3 devices rather than the five you got. I had to grab the available beta version of the Z-Wave plug-in to get mine to include correctly. Give that a try and you should have better luck...

    Comment


      #3
      I tried the Beta, still no dice although I did only get 3. It shows motion from when I first installed it but none since.

      Comment


        #4
        You should remove this device from HS3, then update your Z-Wave plugin to the latest release, then re-add the device and it should work.
        💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

        Comment


          #5
          That is exactly what I did but I will try it again

          Comment


            #6
            Receiving Tamper Event but not motion events

            I'm seeing very similar behavior. The only motion event I receive is when the device is Included. And then the only events I receive are tamper events. Wasn't expecting to have to shake my lights on...

            Comment


              #7
              same problem, using HomeAssistant. Any solution?

              Comment

              Working...
              X