Figaros Dimmer 2

Configuration Z-Wave
1

Why do we get two levels? The second button or scene is activated without one as it seems

2

The device database entry is usually based either on the user manual or other manufacturer supplied documentation. This question appears to be better directed at the vendor support department.

3

With not so many dimmers around i would guess that at least 20% of the community here uses them. Several topics i’ve found addressed that the level2 was for the second button. But seems it works even disabling.

4

If you wire the second button up to it then you can adjust it with the button. However, you can also use the scene events to get button presses. I have found it is just simpler to use the second level in some cases than to deal with scenes. (I really just see it as added flexibility.)

5

Thats the point. I dont get it. Scene functionality now gets called directly on the node and it works with level2 disabled

- platform: event
    event_type: zwave_js_value_notification
    event_data:
      node_id: 3
      value_raw: 26
6

I’m afraid don’t quite follow.

If I understand you correctly, you have a physical switch hooked up to the second switch input and you get a scene event when it is physically activated? But you have it disabled. What do you mean by disabled?

7

As you can see in the example above the event is called with a node_id and raw event value.
Fibaro dimmer creates 2 entities in the HA.
fibaro_dimmer_level
and
fibaro_dummer_level2

So the second entity is disabled via the integrations page in HA.

8

I’m still confused as to what you are trying to achieve. If I press on switch 1 I get one scene and if I press on switch 2 I get another scene. When I do switch 1, then dimmer 1 changes, and when I do switch 2, dimmer 2 changes. (Dimmer 2 isn’t a real dimmer since the physical device only has one dimmer, though.)

The values are the same as in the instruction manual.

Here is the scene I get when I press on switch 2 (and it changes the second switch if it is a single press):

{
    "event_type": "zwave_js_value_notification",
    "data": {
        "domain": "zwave_js",
        "node_id": 43,
        "home_id": 4110823651,
        "endpoint": 0,
        "device_id": "94d636c8a8cf5b52227c5dbd6d93f048",
        "command_class": 43,
        "command_class_name": "Scene Activation",
        "label": "Scene ID",
        "property": "sceneId",
        "property_name": "sceneId",
        "property_key": null,
        "property_key_name": null,
        "value": 26,
        "value_raw": 26
    },
    "origin": "LOCAL",
    "time_fired": "2022-01-16T16:26:24.076722+00:00",
    "context": {
        "id": "fb3c406c58aab6c702d71d0fde5dbcb4",
        "parent_id": null,
        "user_id": null
    }
}

And here is what I get when I press on switch 1 (and it changes switch 1 if it is a single press):

{
    "event_type": "zwave_js_value_notification",
    "data": {
        "domain": "zwave_js",
        "node_id": 43,
        "home_id": 4110823651,
        "endpoint": 0,
        "device_id": "94d636c8a8cf5b52227c5dbd6d93f048",
        "command_class": 43,
        "command_class_name": "Scene Activation",
        "label": "Scene ID",
        "property": "sceneId",
        "property_name": "sceneId",
        "property_key": null,
        "property_key_name": null,
        "value": 16,
        "value_raw": 16
    },
    "origin": "LOCAL",
    "time_fired": "2022-01-16T16:26:21.560285+00:00",
    "context": {
        "id": "8a485961acfcac912ba5958011c0e237",
        "parent_id": null,
        "user_id": null
    }
}

This is what I would expect from the setup.

Is there something different you were expecting, or (more likely) I’m not understanding what you are trying to do.

-David