Announcement

Collapse
No announcement yet.

DS10A's Unrecognized

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    DS10A's Unrecognized

    about a month ago my pc running homeseer had strange values for all my door and window sensors. When I run the 32 bit data decoder all my motion sensors are showing up fine, but all my DS10's show Unrecognized/Corrupt Packet.

    This is driving me batty. I even broke out a fresh sensor and it shows the same..

    Any help anyone??

    Thanks

    #2
    Please post some detailed log entries and version numbers for HomeSeer, the plug-in, Windows version, etc.

    Jon


    Originally posted by scanman717 View Post
    about a month ago my pc running homeseer had strange values for all my door and window sensors. When I run the 32 bit data decoder all my motion sensors are showing up fine, but all my DS10's show Unrecognized/Corrupt Packet.

    This is driving me batty. I even broke out a fresh sensor and it shows the same..

    Any help anyone??

    Thanks
    Jon Ort
    JonOrt@The--Orts.com
    (Remove the dashes in the address, spam is getting out of hand)

    Comment


      #3
      Sorry...

      It was late..

      Windows XP
      Homeseer 1.7.25
      W800rf plugin 2.1.0

      Homeseer Log:
      2/9/2007 9:53:55 AM~!~X10 Received~!~C6 (?) C On
      2/9/2007 9:56:00 AM~!~Event Trigger~!~Condition Trigger (ResetMotion) \1 Off (Living Room Motion Detector)
      2/9/2007 9:56:47 AM~!~X10 Received~!~\8 (House test) \ Off
      2/9/2007 9:56:48 AM~!~X10 Received~!~\8 (House test) \ On
      2/9/2007 9:56:48 AM~!~Info~!~Exec command: C6 Off dim: 0 extra: 0
      2/9/2007 9:56:48 AM~!~X10 Received~!~C6 (?) C Off
      2/9/2007 9:56:49 AM~!~X10 Received~!~\8 (House test) \ Off
      2/9/2007 9:56:49 AM~!~X10 Received~!~\8 (House test) \ On

      Ok so the log is showing Off and On like it should but the web interface is showing a status of:
      32767 House test -- C/RF Supervised Door/Win/Glass Sensor Today at 9:56:49 AM

      Comment


        #4
        Fixed it. Uninstalled the plugin and re-installed. Works fine.

        Comment

        Working...
        X