Central Scene values are not set as "stateless"

[kpine]

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?

Testing out some new HA functionality to represent value notifications as event entities. These support Central Scene devices. An entity should be created for each key attribute (at least I think that's how it works). These entities are not being created. The discovery schema for these relies on the event values to have a stateful: false value. I am seeing the CS values has having stateful values, despite #6424. These is even after re-interviewing the device.

        "39-91-0-scene-001": {
          "endpoint": 0,
          "commandClass": 91,
          "commandClassName": "Central Scene",
          "property": "scene",
          "propertyKey": "001",
          "propertyName": "scene",
          "propertyKeyName": "001",
          "ccVersion": 3,
          "metadata": {
            "type": "number",
            "readable": true,
            "writeable": false,
            "label": "Scene 001",
            "min": 0,
            "max": 255,
            "states": {
              "0": "KeyPressed",
              "1": "KeyReleased",
              "2": "KeyHeldDown",
              "3": "KeyPressed2x",
              "4": "KeyPressed3x",
              "5": "KeyPressed4x",
              "6": "KeyPressed5x"
            },
            "stateful": true,
            "secret": false
          }
        },

What did you expect to happen instead?

The CS values should show "stateful": false.

Steps to reproduce the behavior:

1. Have a device that supports Central Scene
2. Examine the value information, either with HA device diagnostic or ZUI debug
3. See CS values are set to "stateful": true,, but should be false.

Anything else we should know?

Software versions

zwave-js-ui: 9.2.3.1454eca
zwave-js: 12.2.1

Device information

Manufacturer: HomeSeer
Model name: HS-FC200+
Node ID: 39

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

zwave_js.log

zwave_js-3aea29d0aede8f900a111601a3df8501-Scene Capable Fan Control Switch-8b51f41930b70c0513fccf92d223bb4f.json.txt

node_debug.json.txt

[zwave-js-bot]

👋 Hey @kpine!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

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

[AlCalzone]

Fixed by #6457 and #6458