HS-FS100+ light detection no longer works

[PeteRager]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?

The Home Seer HS-F100+ flex sensor can be used to detect an LED turning on or off. In zwavejs 9.9.1, the status of the LED was reported into the "Any" sensor. In zwavejs 9.14.2 the status change does not get reported anywhere - in that I can look at zwavejsui at Binary Sensor V1 and Notiifcation V8 and see no changes; even though data is being reported by the device. Note: the notification state for this device has always reported "Light Detected" regardless of whether light is detected; hence the only sensor that worked was the Any sensor

#6959 -

Excerpts from the 9.9.1 logs

2024-06-19T19:50:42.245Z SERIAL « 0x01110004000f097105000000ff140100b500c7                            (19 bytes)
2024-06-19T19:50:42.246Z SERIAL » [ACK]                                                                   (0x06)
2024-06-19T19:50:42.247Z CNTRLR   [Node 015] [~] [Notification] alarmType: 0 => 0                   [Endpoint 0]
2024-06-19T19:50:42.248Z CNTRLR   [Node 015] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2024-06-19T19:50:42.249Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Light sensor
                                      notification status: 255
                                      notification state:  Light detected
2024-06-19T19:50:42.250Z CNTRLR   [Node 015] [~] [Notification] Light sensor[Light detection status [Endpoint 0]
                                  ]: 1 => 1
2024-06-19T19:50:42.426Z SERIAL « 0x010b0004000f033003ffb50085                                        (13 bytes)
2024-06-19T19:50:42.427Z SERIAL » [ACK]                                                                   (0x06)
2024-06-19T19:50:42.427Z CNTRLR   [Node 015] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2024-06-19T19:50:42.429Z CNTRLR   [Node 015] [~] [Binary Sensor] Any: false => true                 [Endpoint 0]
2024-06-19T19:50:42.430Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true

2024-06-19T20:23:41.858Z SERIAL « 0x01110004000f097105000000ff140100b600c4                            (19 bytes)
2024-06-19T20:23:41.860Z SERIAL » [ACK]                                                                   (0x06)
2024-06-19T20:23:41.861Z CNTRLR   [Node 015] [~] [Notification] alarmType: 0 => 0                   [Endpoint 0]
2024-06-19T20:23:41.862Z CNTRLR   [Node 015] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2024-06-19T20:23:41.863Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Light sensor
                                      notification status: 255
                                      notification state:  Light detected
2024-06-19T20:23:41.864Z CNTRLR   [Node 015] [~] [Notification] Light sensor[Light detection status [Endpoint 0]
                                  ]: 1 => 1
2024-06-19T20:23:41.923Z DRIVER   all queues busy
2024-06-19T20:23:41.924Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2024-06-19T20:23:41.924Z DRIVER » [REQ] [GetBackgroundRSSI]
2024-06-19T20:23:41.934Z SERIAL « [ACK]                                                                   (0x06)
2024-06-19T20:23:41.934Z SERIAL « 0x0105013ba4b8dc                                                     (7 bytes)
2024-06-19T20:23:41.935Z SERIAL » [ACK]                                                                   (0x06)
2024-06-19T20:23:41.935Z DRIVER « [RES] [GetBackgroundRSSI]
                                    channel 0: -92 dBm
                                    channel 1: -72 dBm
2024-06-19T20:23:41.937Z DRIVER   all queues idle
2024-06-19T20:23:42.040Z SERIAL « 0x010b0004000f033003ffb60086                                        (13 bytes)
2024-06-19T20:23:42.040Z SERIAL » [ACK]                                                                   (0x06)
2024-06-19T20:23:42.041Z CNTRLR   [Node 015] [Binary Sensor] Any: metadata updated                  [Endpoint 0]
2024-06-19T20:23:42.042Z CNTRLR   [Node 015] [~] [Binary Sensor] Any: false => true                 [Endpoint 0]
2024-06-19T20:23:42.043Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true

9.14.2

2024-06-25T12:06:36.058Z SERIAL « 0x01110004000f097105000000ff140200b800c9                            (19 bytes)
2024-06-25T12:06:36.059Z SERIAL » [ACK]                                                                   (0x06)
2024-06-25T12:06:36.061Z CNTRLR   [Node 015] [~] [Notification] alarmType: 0 => 0                   [Endpoint 0]
2024-06-25T12:06:36.063Z CNTRLR   [Node 015] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2024-06-25T12:06:36.064Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Light sensor
                                      notification status: 255
                                      notification event:  Light color transition detected
2024-06-25T12:06:36.066Z CNTRLR   [Node 015] [Notification]
                                    type:  Light sensor
                                    event: Light color transition detected
2024-06-25T12:06:40.657Z SERIAL « 0x01110004000f097105000000ff140200b600c7                            (19 bytes)
2024-06-25T12:06:40.658Z SERIAL » [ACK]                                                                   (0x06)
2024-06-25T12:06:40.660Z CNTRLR   [Node 015] [~] [Notification] alarmType: 0 => 0                   [Endpoint 0]
2024-06-25T12:06:40.661Z CNTRLR   [Node 015] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2024-06-25T12:06:40.663Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Light sensor
                                      notification status: 255
                                      notification event:  Light color transition detected
2024-06-25T12:06:40.664Z CNTRLR   [Node 015] [Notification]
                                    type:  Light sensor
                                    event: Light color transition detected

15-48-0-Any just reports false (this sensor used to work in 9.9.1)
15-48-0-Aux just reports true (this sensor did not exist in 9.9.1)
15-113-0-Light sneosr-Light dection status] always reports Light Detected (this was also true in 9.9.1)

What did you expect to happen instead?

Steps to reproduce the behavior:

Setup the device, place the sensor on a lit LED; remove the sensor from the lit LED and cover with thumb. Reports get sent to zwavejs.

Anything else we should know?

Software versions

Driver (node-zwave-js): 12.11.2

Z-Wave JS UI: 9.14.2.fb41d4c

Home Assistant Z-Wave Integration: 2024.6.3

Home Assistant Z-Wave JS Addon: N/A running in docker

Device information

Manufacturer: Home Seer Technologies
Model name: Flex-Sensor HS-FS100+
Node ID: 15

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwavejs 9.14.2 log file

zwavejs_2024-06-25.log

zwavejs 9.9.1 log file

zwavejs_2024-06-19.log

node 15 diagnostics from 9.14.2

node 15 diagnostics.json

[PeteRager]

From the testing I was doing in #6950, i can see the light sensor appears to be working in this version also.

zwave-js-ui: 9.13.3.61d406e
zwave-js: 12.9.1

[AlCalzone]

Technically Any isn't a real sensor type, but it can be used in queries to ask the device for the first supported sensor type. However, some devices use it to report, although the specifications don't allow this.
There was a recent fix/workaround for Binary Sensor CC (#6933), which is why you're seeing the behavior change. Now, reports with Any get treated as if they were reports with the first supported sensor type, in this case Aux.

I can see this happening in your 9.14.2 logfile, so you should see this status change:

2024-06-25T11:39:00.891Z CNTRLR   [Node 015] [~] [Binary Sensor] Aux: false => true                 [Endpoint 0]
2024-06-25T11:39:00.892Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true

The Notification CC implementation is just borked. It sometimes sends Light detected (stateful, 0x01), sometimes Light color transition detected (stateless, 0x02), and sometimes sends an idle notification for Light color transition detected, which does not make sense.

[PeteRager]

You are correct. It is reporting through the aux sensor, not sure why I didn't see that.