Z-Wave JS to MQTT - DSB05 (Aeotec 4 in 1 Multisensor) via Aeotec Z-stick motion sensor not working

[mhendu]

An unfortunate lightning strike appears to have knocked out my aging VeraLite, so I spent last night and part of today transitioning devices over from the VeraLite to my Z-stick on Home Assistant with Z-Wave JS to MQTT.

I managed to get (I think) all the devices working, including some pretty finnicky locks and sensors, but the DSB05 / Aeotec 4 in 1 Multisensor refuses to cooperate. I can get temperature, lux and humidity readings with no issue after some configuration changes, but the motion sensor is just always ‘on.’

I tried setting the reporting method per this thread:

Aeotec DSB05 Gen2 MultiSensor + ZW090 Gen5 USB Stick

So I have been struggling with this for the last several days and I am trying to find a stable solution. A bit of background… I have 3 MultiSensor Gen2s from a SmartThings setup last year. It all worked really well but then the ST cloud started getting wonky and I wanted something more within my control. After some other HA iterations I ended up with HomeAssistant. I made the move and got the ZW090 Aeotec USB Stick. Current problem, openzwave is able to easily see the devices, and I am able to…

But that didn’t solve the issue. There are no hidden entities that I can find that expose a different way of accessing the motion sensor. Would appreciate any help in configuration.

[mhendu]

Some relevant logs when I went into the room and waved my arms:

2022-06-04T00:21:37.308Z CNTRLR   [Node 061] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2022-06-03 19:21:37.308 INFO ZWAVE: Node 61: metadata updated: 48-0-Any
2022-06-04T00:21:37.308Z CNTRLR   [Node 061] [~] [Binary Sensor] Any: true => true                  [Endpoint 0]
2022-06-03 19:21:37.308 INFO ZWAVE: Node 61: value updated: 48-0-Any true => true
2022-06-04T00:21:37.309Z SERIAL » [ACK]                                                                   (0x06)
2022-06-04T00:21:37.318Z DRIVER « [Node 061] [REQ] [ApplicationCommand]
                                  │ type: multicast
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true
2022-06-04T00:21:37.327Z SERIAL « 0x010b0004003d033003ffbc00be                                        (13 bytes)
2022-06-04T00:21:37.332Z CNTRLR   [Node 061] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2022-06-03 19:21:37.332 INFO ZWAVE: Node 61: metadata updated: 48-0-Any
2022-06-04T00:21:37.333Z CNTRLR   [Node 061] [~] [Binary Sensor] Any: true => true                  [Endpoint 0]
2022-06-03 19:21:37.334 INFO ZWAVE: Node 61: value updated: 48-0-Any true => true
2022-06-04T00:21:37.336Z SERIAL » [ACK]                                                                   (0x06)
2022-06-04T00:21:37.337Z DRIVER « [Node 061] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true

[mhendu]

Strangely, after setting the log level to ‘Silly’ to post the above, and waving my arms around in the room, the device detected motion, then reported as ‘off’ after a minute. When I changed the log level back to ‘Info’ and repeated the action it detected motion again, then finally reported as ‘off’ about four minutes later. So, I didn’t change any configuration settings, but for whatever reason it seems to be working now, more or less.

[PeteRage]

Go into device configuration and look for disabled entities. There may be one called “any”, enable that, it may work more consistently.