HA has a new BASIC light after the latest updates of zwave-js and HA

[novaware-io]

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

Since the latest updates I can see that some sensors devices now have an entity showing as light in HA.

The devices are:

• Fibaro Motion Sensor FGMS001
• Fibaro Door/Window Sensor FGK101
• Fibaro Flood Sensor FGFS101
• Fibaro Smoke Sensor FGSS001

Some are always ON, others always OFF.

Here the diagnostic for one of them: https://pastebin.com/V63Wigjv
I can provide the other ones if needed.

Thanks

Software versions

Driver Version: 12.2.3
Server Version: 1.33.0
Home Assistant version 2023.11

Device information

• Fibaro Motion Sensor FGMS001
• Fibaro Door/Window Sensor FGK101
• Fibaro Flood Sensor FGFS101
• Fibaro Smoke Sensor FGSS001

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

No response

[zwave-js-bot]

👋 Hey @novaware-io!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[novaware-io]

I don't think my log is needed here, correct? it's more about the device configuration that's why I've pasted the device diagnostic, but when somebody reviews this issue, please let me know if a log is still needed, thanks

[asayler]

Adding some additional devices that show up with the new basic control value and probably shouldn't (most of them are sensors with no function to control):

• Zooz ZSE29 Motion Sensor
• Zooz ZEN31 RGBW Controller (adds a bunch of duplicate basic controls for each color channel)
• Ecolink PIR Motion Sensor v2.5
• Ecolink DWZWAVE25 Door Sensor
• Vision ZD2102-5 Door Sensor
• Sensative Strip Guard Door/Window Sensor

[Technodad]

I am seeing this behavior with three elderly switches type “GE - In-Wall Paddle Switch, 300S”. This seems to have shown up in the past couple of weeks. I’ve turned on driver logging per the instructions.

Edit: Added zwavejs_2023-11-05.log.

[AlCalzone]

@asayler the sensors probably use Basic CC to report state. Can you re-interview one or two of those, while making a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

[kpine]

I am seeing this behavior with three elderly switches type “GE - In-Wall Paddle Switch, 300S”.

These Jasco/GE devices are already fixed in v12.3.0. You'll need to wait until the application you are using updates, and then the entities will become unavailable and you can delete them.

• Vision ZD2102-5 Door Sensor

I have this device and it does not have any light entity. I would second the suggestion to re-interview. It just did a re-interview today to make sure I didn't have outdated state and still no entities.

[Idaho947]

I add :

• Aeotec motion multisensor 6 and 3 (ZW100 and
• Fibaro smoke detector (FGSD002)

[AlCalzone]

Everyone who's experiencing this, please re-interview the affected devices. If the issue persists after the re-interview, I'd like to see a driver log, on loglevel debug, attached here as a file (drag & drop into the text field).

[The00Dustin]

I have six ZSENS930's. Four of them were showing the basic set and two of them were not. At 21:30 UTC, I reinterviewed node 020, which was showing it, and it still showed it afterwards. At 21:34 UTC, I reinterviewed node 022, which was not showing it, and then it started showing it afterwards.

I also have 1 VCZ1 which is showing this, and I was able to reinterview it at 23:35 UTC (node 011).

All three of the reinterviews discussed above should be included in this log file:
zwave-js-ui-store.zip

[Technodad]

I re-interviewed my GE switches, and the Basic devices seem to be gone. Regards,Dave L.[Mobile]On Nov 7, 2023, at 10:28 AM, AlCalzone ***@***.***> wrote: Everyone who's experiencing this, please re-interview the affected devices. If the issue persists after the re-interview, I'd like to see a driver log, on loglevel debug, attached here as a file (drag & drop into the text field). —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[novaware-io]

I confirm that by installing the latest updates and re-interviewing the device the BASIC light disappeared for me

Thank you, let me know if I shall close this now

[thecobra666]

Have the same issue with my Fibaro smoke sensors. After re-interview the issue stays.

[AlCalzone]

So far it looks like the issue is limited to sensors. I've checked the specification and for all reporting type devices (this includes multisensors), the spec is pretty clear:

Basic Command Class MUST NOT be supported

At least my Multisensor 6 though does report support for the CC and responds when queried, which is where the entity seems to come from (at least after reporting motion once).

I think the solution would be forcibly marking Basic CC for all sensors as unsupported, and if they issue Basic commands or report support, treat this as controlling Basic CC.

[AlCalzone]

This is now tracked as a bug here