Tuya Motion Sensor _TZ3000_msl6wxk9 TS0202 no motion in HA

Hi hi,

I have a few Tuya Motion Sensors that I have seen here and in github already.
For some reason, Home Assistant doesn’t show if any motion is detected.
Since a DDF was already developed for _TZ3000_msl6wxk9, I hoped it would work with that, but so far no joy.
I can see the status change in deCONZ when motion is detected, I have that id in the binding too, but HA doesn’t seem to pick it up.
The sensor is available, but the status remains unchanged at “clear”.
Any thoughts on where I should be looking to see if anything is communicated properly between deCONZ and HA?

My DDF is:

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZ3000_msl6wxk9",
  "modelid": "TS0202",
  "product": "TS0202",
  "sleeper": true,
  "status": "Silver",
  "path": "/devices/_TZ3000_msl6wxk9_ts0202_take2.json",
  "subdevices": [
    {
      "type": "$TYPE_PRESENCE_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0500"
      ],
      "fingerprint": {
        "profile": "0x0104",
        "device": "0x0107",
        "endpoint": "0x01",
        "in": [
          "0x0000",
          "0x0001",
          "0x0500"
        ]
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/battery",
          "awake": true,
          "read": {
            "at": "0x0021",
            "cl": "0x0001",
            "ep": 1,
            "fn": "zcl"
          },
          "parse": {
            "at": "0x0021",
            "cl": "0x0001",
            "ep": 1,
            "eval": "Item.val = Attr.val / 2",
            "fn": "zcl"
          }
        },
        {
          "name": "config/duration"
        },
        {
          "name": "config/enrolled",
          "public": false,
          "description": "State of IAS enrollment process."
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/battery",
          "refresh.interval": 3600
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/lowbattery",
          "description": "True when the device battery runs low."
        },
        {
          "name": "state/presence",
          "awake": true,
          "parse": {
            "fn": "ias:zonestatus",
            "mask": [
              "alarm1",
              "alarm2"
            ]
          }
        },
        {
          "name": "state/tampered",
          "description": "True when the device tampered alarm was triggered."
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 0,
          "max": 0
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0500",
      "report": [
        {
          "at": "0x0002",
          "dt": "0x19",
          "min": 0,
          "max": 0
        }
      ]
    }
  ]
}

On m yside I don’t use “mask” in state/presence and I don’t realy like min= max = 0 for the report on the cluster 0x0500, but if it work on phosocn, it need to work on HA too, as they are using the same API.

You can check the device json using phoscon / help / API information / sensors to check the state/presence, you can too see websocket event in real time.