Aeotec DSB05 motion sensor created by ZwaveJS not detected by blueprint input device

Configuration Z-Wave
1

Hello,

The inclusion of a Zwave 4 in 1 sensor DSB05 ( motion , temp , humidity , lux ) has been done successfully with HA version 2021.7.2 and Zwave JS addon + zwaveJS integration as per the entities list created:

DSB05 Entity
DSB05 Entity1395×777 49.8 KB

  1. The issue is that the motion sensor “4 in 1 Multisensor: Any” cannot be found by this blueprint input selector :
blueprint:
  name: camera snapshot when motion
  description: >
    This automation blueprint creates a camera snapshot if motion is detected 
    and sends a notification to your phone with the picture.
  domain: automation
  input:
    motion_sensor:
      name: Motion sensor
      description: The sensor wich triggers the snapshot creation
      selector:
        entity:
          domain: binary_sensor
          device_class: motion
  1. The motion sensor is working properly :
2021-07-15T06:22:33.030Z CNTRLR   [Node 003] [~] [Binary Sensor] Any: false => true                 [Endpoint 0]
2021-07-15T06:22:33.034Z SERIAL » [ACK]                                                                   (0x06)
2021-07-15T06:22:33.038Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
                                  │ type:        multicast
                                  │ target node: 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 
                                  0, 0, 0, 0, 0, 0, 0, 0
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true
2021-07-15T06:22:33.055Z SERIAL « 0x010c00a8000103033003ff00cf59                                      (14 bytes)
2021-07-15T06:22:33.057Z CNTRLR   [Node 003] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2021-07-15T06:22:33.059Z CNTRLR   [Node 003] [~] [Binary Sensor] Any: true => true                  [Endpoint 0]
2021-07-15T06:22:33.061Z SERIAL » [ACK]                                                                   (0x06)
2021-07-15T06:22:33.063Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true
2021-07-15T06:22:34.634Z SERIAL « 0x012900a8080003033003001d01000000000000000000000000000000000000000 (43 bytes)
                                  00000000000000000c891
2021-07-15T06:22:34.637Z CNTRLR   [Node 003] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2021-07-15T06:22:34.638Z CNTRLR   [Node 003] [~] [Binary Sensor] Any: true => false                 [Endpoint 0]
2021-07-15T06:22:34.640Z SERIAL » [ACK]                                                                   (0x06)
2021-07-15T06:22:34.644Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
                                  │ type:        multicast
                                  │ target node: 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 
                                  0, 0, 0, 0, 0, 0, 0, 0
                                  └─[BinarySensorCCReport]

==>> Any idea on the blueprint issue , the DSB05 motion sensor being correctly displayed in Development Tools as a binary sensor ( binary_sensor.4_in_1_multisensor_any) ?

Thank you

2

You have a binary_sensor there called “Any” that should be your motion sensor.

3

yes @firstof9 , that’s correct and i have corrected the first Post following my last testing.

The issue now is on the blueprint side
Thanks a lot

4

remove this line and it should work.

5

The workaround ( delete the “device_class: motion”) works.

1 Like