Announcement

Collapse
No announcement yet.

DS10 recognizes device but not command

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

  • DS10 recognizes device but not command

    Any thoughts on why the command is not being recognized?

    Aug-04 9:00:25 AM SimpleRF Checking Security triggers for matches against Device Unit Code: 14279, X-10 Command: UNKNOWN
    Aug-04 9:00:25 AM SimpleRF Received Security Message from Receiver 1: UNKNOWN
    Aug-04 9:00:25 AM SimpleRF Received: P14279 UNKNOWN

    W800 Serial receiver and an x10 ds10 motion sensor. Same response with other ds10's.

  • #2
    Same here. Anyone know how to overcome this?

    Originally posted by acalbear View Post
    Any thoughts on why the command is not being recognized?

    Aug-04 9:00:25 AM SimpleRF Checking Security triggers for matches against Device Unit Code: 14279, X-10 Command: UNKNOWN
    Aug-04 9:00:25 AM SimpleRF Received Security Message from Receiver 1: UNKNOWN
    Aug-04 9:00:25 AM SimpleRF Received: P14279 UNKNOWN

    W800 Serial receiver and an x10 ds10 motion sensor. Same response with other ds10's.

    Comment


    • #3
      may have a solution

      It appears that the DS10a protocol allows for a variety of bytes to be sent for the function/key value. What that means is that our DS10's can send various data depending on various criteria. See https://bfocht.github.io/mochad/x10_...d_address.html for details. Check out the function/key section for DS10's.

      What I have determined is that the DS10 must be set to max mode (slide switch behind the cover of the DS10) for the SimpleRF plugin to recognize the commands. That is the case based upon my testing. Not sure if that is by design or if there is a bug in my version of the plugin (1.3.3.0).

      Hope that helps.

      Oh, by the way; if your DS10 reports a low battery condition, that also is an unknown state to the plugin. Instead of sending 0x04 & 0x84 for alert and normal state, when the battery is low, the DS10 sends 0x05 and 0x85. That causes my system to report "UNKNOWN" and the plugin ignores the sensor.

      Best,
      Frank

      Comment


      • #4
        Checking Security triggers for matches against Device Unit Code: 13765, X-10 Command: UNKNOWN
        Jan-23 2:50:11 PM SimpleRF Received Security Message from Receiver 1: 1st. Floor Cellar Basement Door X10 Magnetic Switch UNKNOWN
        Jan-23 2:50:11 PM SimpleRF X-10 Debug: CAPI.CAPIControl count: 0
        Jan-23 2:50:11 PM SimpleRF X-10 Debug: SetDeviceValue, devRef: 601, command: UNKNOWN
        Jan-23 2:50:11 PM SimpleRF Received RAW: 0xa3 0xac 0x85 0x7a from Receiver 1
        Jan-23 2:50:11 PM SimpleRF Received: P13765 UNKNOWN
        Jan-23 2:50:10 PM SimpleRF Checking Security triggers for matches against Device Unit Code: 13765, X-10 Command: UNKNOWN
        Jan-23 2:50:10 PM SimpleRF Received Security Message from Receiver 1: 1st. Floor Cellar Basement Door X10 Magnetic Switch UNKNOWN
        Jan-23 2:50:10 PM SimpleRF X-10 Debug: CAPI.CAPIControl count: 0
        Jan-23 2:50:10 PM SimpleRF X-10 Debug: SetDeviceValue, devRef: 601, command: UNKNOWN
        Jan-23 2:50:10 PM SimpleRF Received RAW: 0xa3 0xac 0x05 0xfa from Receiver 1
        Jan-23 2:50:10 PM SimpleRF Received: P13765 UNKNOWN

        If I read correctly this is an issue for the plugin ,, is it going to be corrected ??

        The tamper switch on the ds11a is also unknown
        Last edited by dem5867; January 23rd, 2018, 03:37 PM.

        Comment

        Working...
        X