Two separate dimmers of the same model report scenes differently breaking blueprint based automation

[young spoke]

I have two Inovelli LZW31-SN Zwave dimmer switches set up to control lights. Both support sending scenes back to Home Assistant using multi-taps of the switch. Recently one of the switches has changed how its scene data is reported/read.

The switch that is working as intended shows a message of KeyPressed2x when sending a double tap scene. The switch that no longer works correctly is show as 3 for the same double tap scene. I've attached a couple of screenshots of the automation traces of these devices. They are both using the same automation blueprint.

I also checked the Zwave logs in ZWave-JS-UI and they are both sendin the same data for the scene action. It appears to be the way its interperted once reicieved by Home Assistant. I found a thread from a couple of years ago when this was reports as a bug but appear to have been fixed pretty quickly. https://github.com/home-assistant/core/issues/47331

I am running HA Core 2025.3.4, Supervisor 2025.03.3, HAOS 14.2. I am using a Zooz ZST39 LR Zwave stick on FW 1.50.

Any help would be appreciated.

[hardy rover]

Re-interview the non-working one

[young spoke]

Yup, that fixed it. Any idea why that works? It doesn't seem like there was any change in the incoming Zwave data accoring to the logs.

2025-03-24 20:11:10.935 INFO Z-WAVE: [Node 024] Value notification: 91-0-scene-001 3
2025-03-25T00:11:10.936Z CNTRLR « [Node 024] received CentralScene notification {
                                      "nodeId": 24,
                                      "ccId": "Central Scene",
                                      "ccCommand": "0x03"
                                  }

[hardy rover]

The node was missing the required metadata. Why, not sure. Could have been an error at some point.

The device diagnostic will show you what is expected

        "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": false,
            "secret": false
          }
        },

Sometimes the "states" field is missing, so the value isn't translated

[young spoke]

Thank you so much for the detailed response. I truly appreciate it!

[hardy rover]

I tend to use value_raw in these specific automations, and just hardcode the number. Guess not an option if you're using a pre-built blueprint.

[young spoke]

That was actually recommendation in the blueprint thread while the bug I mentioned wasn't yet resolved: