Generic MQTT scene state switch

moshess · February 1, 2021, 1:14am

This blueprint was inspired by the work of @troy on their Inovelli LZW31-SN Dimmer post. I liked that integration enough to modify the blueprint for the Zooz ZEN34 when I realized the configuration mappings were identical and the blueprint itself could remain very generalized.

I started using ZwaveJs2Mqtt which required a modification to the previously modified OpenZwaveMqtt blueprint. Thought others may appreciate having a one stop shop for the various scene selections without writing custom automations to intercept the events.

I suspect this blueprint would work with all MQTT devices but I’m using ZwaveJs2Mqtt and am requiring that all devices were configured with a nodeName and nodeLocation.

Notes

It’s not guaranteed that your switch has all of theses events. Please refer to any literature from the manufacturer for clues on what is/is-not capable
All configurations are optional, so you only need to wire up the events you care about
Have fun! Let me know of any suggestions/improvements/etc.

github.com

moshess/homeassistant-blueprints/blob/master/mqtt/mqtt-scene-state-switch.yaml

blueprint:
  name: MQTT scene state switch
  description: Automation blueprint for many z-wave switches with up/down button
    and multiple key presses. Designed with Inovelli LNSW31 and Zooz ZEN34 mappings in mind.
  domain: automation
  input:
    node_name:
      name: Name of the zwavejs entity
      description: Enter the name configured to the device in zwavejs
    mqtt_device:
      name: MQTT switch
      description: List of available MQTT entities. This list is intended for reference only.
        At this time, it is not known how to or if we can obtain the nodeName
        and nodeLocation from the device used to filter the events.
      selector:
        device:
          integration: mqtt
          entity:
            domain: sensor
    node_location:

This file has been truncated. show original