Fibaro dimmer 2 S2 functionality

[RutgerJoosten]

I created this blueprint on the basis of vbflo’s blueprint I found (Inovelli LZW36 Fan/Dimmer Scenes)

This blueprint creates an automation for the fibaro dimmer 2 functions of the S2 switch.
Select witch device you want to use and than create actions for all S2 functions:

• 1 press
• 2 presses
• 3 presses
• hold

In order for this to work, you got to turn on parameter 28 in the zwave device settings

Edit: I loaned some code from: ZWaveJS - Fibaro dimmer 2 - S1 and S2 scenes to get it properly working again with ZWaveJS. If you want to include scene activation for S1 aswell you can use this automation. I wanted this one to remain clean and only add support for the S2

Thanks @ankabout for pointing me to this.

Edit: Typo in the yaml fixed, so it worked again. Also added a import button

blueprint:
  name: Fibaro Dimmer 2 S2
  description: |
    Use this blueprint to create automations based on button presses for the Fibaro Dimmer 2
  domain: automation
  input:
    fibaro_device:
      name: Fibaro Dimmer
      description: The Fibaro Dimmer that will trigger the scenes
      selector:
        device:
          integration: zwave_js
          manufacturer: Fibargroup

    s2_button_once:
      name: S2 Button Once
      description: Pick an action for when the s2 button is pressed once.
      default: []
      selector:
        action:

    s2_button_twice:
      name: S2 Button Twice
      description: Pick an action for when the s2 button is pressed twice.
      default: []
      selector:
        action:

    s2_button_trice:
      name: S2 Button Three Times
      description: Pick an action for when the s2 button is pressed three times.
      default: []
      selector:
        action:

    s2_button_hold:
      name: S2 Button Hold
      description: Pick an action for when the s2 button is hold.
      default: []
      selector:
        action:

mode: single

trigger:
  - platform: event
    event_type: zwave_js_value_notification
    event_data:
      device_id: !input fibaro_device

variables:
  scene_id: "{{ trigger.event.data.scene_id }}"

action:
  - choose:
      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.value == 26 }}"
        sequence: !input s2_button_once

      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.value == 24 }}"
        sequence: !input s2_button_twice

      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.value == 25 }}"
        sequence: !input s2_button_trice

      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.value == 22 }}"
        sequence: !input s2_button_hold

[tvdmoosdijk (Twan)]

I love this blueprint. Could you make the double/triple/gold optional?

[RutgerJoosten]

tnx
Good question. I dont know if this is possible.
Some things you can do:

• Put a delay of 1 sec in the buttons you do not want to use.
  
• Edit the blueprint yaml (remove the button presses you dont want to use).

[MarvinS]

@RutgerJoosten Setting the default value for each action to [] should make all the actions optional. Then people can override them whenever necessary.

[RutgerJoosten]

Aah cool tnx!
@tvdmoosdijk I adjusted the blueprint. I think you need to import it again to get the changes.

[tvdmoosdijk (Twan)]

I get an error when importing:

Invalid blueprint: expected a dictionary for dictionary value @ data['blueprint']['input']['s2_button_hold']['selector']. Got OrderedDict([('action', [])]) expected a dictionary for dictionary value @ data['blueprint']['input']['s2_button_once']['selector']. Got OrderedDict([('action', [])]) expected a dictionary for dictionary value @ data['blueprint']['input']['s2_button_trice']['selector']. Got OrderedDict([('action', [])]) expected a dictionary for dictionary value @ data['blueprint']['input']['s2_button_twice']['selector']. Got OrderedDict([('action', [])])

[RutgerJoosten]

Hmm this is very strange. I restarted mij HA and now I get the same error. It worked before my restart…
I could just select 1 action and save the automation.

For now I removed the [] after the action. It is no longer optional, but it should work again.
I will look for a solution for this, but I see someone else also having trouble with this as well in another topic not giving me much hope for now.

[Ctyd (Karl koch)]

very nice!!!

big thx!

[Roodwang]

My entiteit drop down says “Geen overeenkomende entiteiten gevonden”. But i do have multiple Fibaro 2 dimmers installed ? Do you know how to fix this?

thanks
M

[RutgerJoosten]

Hmm that is strange. I got the whole list of zwave devices, lights and sensors.
I’m can’t think of anything on how to fix this unfortunately. I don’t think this is due to the blueprint, because it just searches for all zwave devices.

“Have you tried turning it off and on again? ” (Maybe a restart can help, I also had some strange behaviour that fixed itself after a restart of HA).
Sorry that I can’t be of more help.

[gilius (Olle Hammar)]

I have the same problem, empty dropdown for choosing my dimmers.

Br
Olle

[RutgerJoosten]

Could it be a bug?
For test sake I imported this blueprint again to check if I got the same problem. This is not the case, so I don’t think the blueprint is wrong.

I am not a dev, so I don’t know what else I can do.
You can try to report this as a bug, then they can look into it.

[Soccs]

did anyone ever found a solution to why we cant add a entity? i t hink this could fix my issue with the parameters! can anyone assist on making an automation? mu problem is that i have to press 2 times to togle the light on and again click twice to turn of the light.

Kind Regards,

[Roodwang]

I fixed this by installing de “Zwave” integration in stead of the Beta version.

[gilius (Olle Hammar)]

@RutgerJoosten

      selector:
        entity:
          integration: zwave

This selector that pick the dimmers is the problem, what name is the Beta integration using ?

[RutgerJoosten]

I wouldn’t call it a problem than, because some are using another zwave integration. But good that there probebly is a solution.
I use the zwave integration from the integration panel (installed with the ui)
I haven’t used the beta persoon, but more info can be found here: https://www.home-assistant.io/integrations/ozw/

In an example they use ‘ozw.scene_activated’.
So I assume the integration needs to be ozw, but I dont know if it works if you replica all the zwave with ozw. Maybe someone who is using the beta integration can test this.

[Daniel_Liebst]

im using zwave js, and i dont either find my entities, otherwise would be great if this would work with all zwave integrations.

[bubbzy]

Would love it with JS aswell

[ronnyandre]

Has anyone found a solution for this? I am also using zwave js

[ronnyandre]

Okay, I actually fixed this. I edited the blueprint yaml file and replaced line 12 with:

integration: zwave_js