Z2M v2.0 - Inovelli Blue Series 2-in-1 switch + dimmer

Blueprints Exchange
, , ,
1

Here’s my work-in-progress blueprint for the Inovelli Blue Series switch, model VZM31-SN for use with Zigbee2MQTT. This exposes all the button combinations for you to do with what you please. For example, double press down to turn off every light in the house. Press and hold up to slowly turn the brightness of the entire room up until you release the button. Have fun. Check out my other blueprint for some tips if you need help: Zigbee2Mqtt 2.0 - IKEA five button remote

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

blueprint:
  name: Z2M v2.0 - Inovelli 2-in-1 switch + dimmer Scene Controls 
  description: |
    For Inovelli Blue Series 2-in-1 switch + dimmer, model VZM31-SN
    Allows setting a few different actions such as 2,3,4,5 clicking the up/down and config buttons.
    Updated for use with Zibbee2MQTT v2.0 with Device Actions

  domain: automation
  input:
    switch:
      name: Switch
      description: Inovelli Switch.
      selector:
        device:
          integration: mqtt
          manufacturer: Inovelli
    config_held:
      name: Hold Config
      description: Action to run 
      default: []
      selector:
        action:
    config_release:
      name: Release Config
      description: Action to run (will also stop the "Hold Down" action automatically)
      default: []
      selector:
        action:
    config_single:
      name: Single Click Config
      description: Action to run
      default: []
      selector:
        action:
    config_double:
      name: Double Click Config
      description: Action to run
      default: []
      selector:
        action:
    config_triple:
      name: 3x Click Config
      description: Action to run
      default: []
      selector:
        action:
    config_quadruple:
      name: 4x Click Config
      description: Action to run
      default: []
      selector:
        action:
    config_quintuple:
      name: 5x Click Config
      description: Action to run
      default: []
      selector:
        action:
    down_held:
      name: Hold Down
      description: Action to run 
      default: []
      selector:
        action:
    down_release:
      name: Release Down
      description: Action to run (will also stop the "Hold Down" action automatically)
      default: []
      selector:
        action:
    down_single:
      name: Single Click Down
      description: This will trigger an/some action(s), but also, it will probably turn off the switch locally.
      default: []
      selector:
        action:
    down_double:
      name: Double Click Down
      description: Action to run
      default: []
      selector:
        action:
    down_triple:
      name: 3x Click Down
      description: Action to run
      default: []
      selector:
        action:
    down_quadruple:
      name: 4x Click Down
      description: Action to run
      default: []
      selector:
        action:
    down_quintuple:
      name: 5x Click Down
      description: Action to run
      default: []
      selector:
        action:
    up_held:
      name: Hold Up
      description: Action to run
      default: []
      selector:
        action:
    up_release:
      name: Release Up
      description: Action to run (will also stop the "Hold Up" action automatically)
      default: []
      selector:
        action:
    up_single:
      name: Single Click Up
      description: This will trigger an/some action(s), but also, it will probably turn on the switch locally.
      default: []
      selector:
        action:
    up_double: 
      name: Double Click Up
      description: Action to run
      default: []
      selector:
        action:
    up_triple:
      name: 3x Click Up
      description: Action to run
      default: []
      selector:
        action:
    up_quadruple:
      name: 4x Click Up
      description: Action to run
      default: []
      selector:
        action:
    up_quintuple:
      name: 5x Click Up
      description: Action to run
      default: []
      selector:
        action:

mode: restart
max_exceeded: silent

trigger:
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_double
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_release
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_held
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_quintuple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_single
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: config_triple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_double
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_held
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_quadruple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_quintuple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_release
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_single
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: down_triple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_double
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_held
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_quadruple
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_release
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_single
    trigger: device
  - domain: mqtt
    device_id: !input switch
    type: action
    subtype: up_triple
    trigger: device

action:
  - variables:
      command: "{{ trigger.payload }}"
  - choose:
      - conditions:
          - "{{ command == 'config_held' }}"
        sequence: !input config_held
      - conditions:
          - "{{ command == 'config_release' }}"
        sequence: !input config_release
      - conditions:
          - "{{ command == 'config_double' }}"
        sequence: !input config_double
      - conditions:
          - "{{ command == 'config_quadruple' }}"
        sequence: !input config_quadruple
      - conditions:
          - "{{ command == 'config_quintuple' }}"
        sequence: !input config_quintuple
      - conditions:
          - "{{ command == 'config_single' }}"
        sequence: !input config_single
      - conditions:
          - "{{ command == 'config_triple' }}"
        sequence: !input config_triple
      - conditions:
          - "{{ command == 'down_double' }}"
        sequence: !input down_double
      - conditions:
          - "{{ command == 'down_held' }}"
        sequence: !input down_held
      - conditions:
          - "{{ command == 'down_quadruple' }}"
        sequence: !input down_quadruple
      - conditions:
          - "{{ command == 'down_quintuple' }}"
        sequence: !input down_quintuple
      - conditions:
          - "{{ command == 'down_release' }}"
        sequence: !input down_release
      - conditions:
          - "{{ command == 'down_single' }}"
        sequence: !input down_single
      - conditions:
          - "{{ command == 'down_triple' }}"
        sequence: !input down_triple
      - conditions:
          - "{{ command == 'up_double' }}"
        sequence: !input up_double
      - conditions:
          - "{{ command == 'up_held' }}"
        sequence: !input up_held
      - conditions:
          - "{{ command == 'up_quadruple' }}"
        sequence: !input up_quadruple
      - conditions:
          - "{{ command == 'up_quintuple' }}"
        sequence: !input up_quintuple
      - conditions:
          - "{{ command == 'up_release' }}"
        sequence: !input up_release
      - conditions:
          - "{{ command == 'up_single' }}"
        sequence: !input up_single
      - conditions:
          - "{{ command == 'up_triple' }}"
        sequence: !input up_triple

edited the order of inputs

Added missing import button

Edit 1/5/25 updated to use Zigbee2MQTT v2.0 Device Actions
Edit again - Fix config_held & release missing

5 Likes
2

Thanks for sharing! I got this working but had to remove line #150 (attribute: action). My blue switches don’t report state under that attribute.

1 Like
3

Ah, yes, that may be the Z2M setting “Home Assistant legacy entity attributes” I have enabled still. I’ll take that line out, too. Thanks!

4

This is great, thank you! Any chance you could order the commands more logically, something like Hold Config, Release Config, Config x1, Config x2, Config x3, Config x4…, Hold Up, Release Up, Up x1, Up x2 … ? It’s really hard to find the command you’re looking for currently.

Thanks!

1 Like
5

@smenzer Good feedback! I sorted them in VS code alphabetically, and that’s probably not the best way to do that. I like your idea much better.

6

Looks much better, thank you very much!

7

Thanks OP for creating this blueprint. Apologies for the noob question. I’ve only ever used blueprints where I can import them and customize them in the UI. If I understand correctly, I’m supposed to copy and paste the above yaml into an automation by selecting “Edit in YAML”, correct?

I already have the switch working directly via direct bind with some bedside lamps in Z2M. What I’m trying to do is just use OPs script so that when I double tap on the switch, some accent lighting turns on or off.

However, despite adding my switch name, the sensor.dimmer_switch_action, and the action for ONLY the double up and double down, I’m getting an error Message malformed: required key not provided @ data['action''] – Does this mean I need to map every button press not just the one I’m trying to enhance?

Any chance someone can provide some help or an example so I can better understand how this works? Thanks

8

Hey @ThatTallGuy, I did forget to include the markdown for the “import” button in my post, it is there now! I would go ahead and create the blueprint using that versus the Edit As Yaml method you mentioned, then create the automation using that blueprint.

I’m including a screenshot of what my automation looks like from the blueprint. After you re-create both your blueprint and automation, let me know if you see something similar to this.

Screenshot_20221122-210901
Screenshot_20221122-2109011152×2496 229 KB

Hopefully this also fixes your error message.

9

That did the trick! Super easy to configure now. Thanks a ton!

1 Like
10

@starbuck93 which sensor is supposed to be used to trigger this blueprint?

I’ve got some ikea buttons and they create a sensor.buttonname_action entity. But my VZM31’s do not.

11

For me, it works the same as the IKEA remote. Are you using legacy entity attributes in Z2M?

12

I’m not. Should that be enabled to create the entity?

EDIT: Correction, I guess I do have it enabled. Will try disabling

13

@starbuck93 What’s your action for hold to dim/brighten? Are you calling a stop action on release as well to stop the loop? Have an example by chance?

14

@sdholden28 at the moment I’m using the switch’s default settings for hold to dim/brighten. Otherwise I’d call a script from one of the “hold” actions in the blueprint and have the script watch for the “release” action. Or something similar to that.

1 Like
15

Any chance you could elaborate on this? I’m fairly new to HA and would LOVE to get this dim/brighten while paddle is held situation figured out before the spouse kills me.

16

Haha, sure thing. The switch, by default when you install it in the wall with dimmer mode, lets you push and hold up or down to slowly change the brightness. I have mine set to “OutputMode” = Dimmer in Z2M settings, which probably does something, as well.

Additionally, I do not have anything in the blueprint fields for “hold up” or down.

17

so would that only work if your controlling lights via Z2M? I’m trying to control lights outside of Z2M, using HA itself.

18

It’s just the logic built into the switch. If I unplug home assistant or something, the switch will still dim up or down

19

right. I guess this doesn’t apply to me since I’m using the switch to control lights outside of Z2M and via HA, not direct to the switch.

I’m looking for an automation solution using loops to get brightness/dimming via holding/releasing the paddle. I’m just not well versed in looping scripts and was hoping to get some help.

20

Hey folks, this blueprint has been updated to use Zigbee2MQTT v2.0 device actions, so if you’ll need to re-import it to update it.

3 Likes