#Motion Sensor stopped exposing Occupancy

1 messages · Page 1 of 1 (latest)

alpine pivot
#

Hey,

I've had multiple automations using a MOSZB-140 (Frient Motion Sensor Pro) device's Occupancy work like a charm for a long time, only to see them come to a screeching halt a couple of weeks ago. After diving in, I saw that the devices no longer expose the Occupancy sensor in the automations editor where you can pick the triggering entity, even though it seems to still be there when I check the devices. I've reconfigured the devices (Occupancy shows as a Bindable attribute) and even completely removed and re-added them. Unfortunately, all to no avail.

Occupancy for the devices used to be available, but it unfortunately no longer is. It also no longer shows on the device overview, even though it used to.
Reconfiguring the device does show the OccupancySensing and Occupance as a bindable attribute (see attached for screenshot).

Here's part of the device config.

"34": {
  "profile_id": 260,
  "device_type": {
   "name": "OCCUPANCY_SENSOR",
   "id": 263
  },
  "in_clusters": [
   {
      "cluster_id": "0x0000",
      "endpoint_attribute": "basic",
      "attributes": [
        {
          "id": "0x0004",
          "name": "manufacturer",
          "zcl_type": "string",
          "value": "frient A/S"
        },
        {
          "id": "0x0005",
          "name": "model",
          "zcl_type": "string",
          "value": "MOSZB-140"
        }
      ]
    },
    {
      "cluster_id": "0x0003",
      "endpoint_attribute": "identify",
      "attributes": []
    },
    {
      "cluster_id": "0x0406",
      "endpoint_attribute": "occupancy",
      "attributes": [
        {
          "id": "0x0000",
          "name": "occupancy",
          "zcl_type": "map8",
          "value": 0
        }
      ]
    }
  ],
  "out_clusters": []
}

I haven't been able to find a similar issue either on GitHub or here. Apologies if that means I didn't search well enough.

Any ideas?