rdeangel

blueprint:
  name: Zigbee2MQTT - Sonoff 1-Button Switch (MQTT Subscribe Any - Filters Multiple Devices) - rdeangel
  description: "Blueprint Version: 12-01-25\n
    Blueprint Name: Zigbee2MQTT - Sonoff 1-Button Switch (MQTT Subscribe Any - Filters Multiple Devices) - rdeangel\n\n
    This blueprint subscribes to all Z2M Action topic `zigbee2mqtt/+/action`
	  and then filters the correct MQTT topic.\n
    It takes multiple dropdown as the main filter condition to decide if the trigger should be considered for actions or ignored.\n
    The fact that the automation triggers even when other mqtt devices actions are received it's not ideal, it does however
    allow for multiple buttons to be driven by the same automation if that's what you are looking for.\n
    Also If you want minor differences betweem multiple buttons and the buttons are mostly doing the same thing but you want to 

rdeangel

blueprint:
  name: Zigbee2MQTT - Sonoff 1-Button Switch (MQTT Device Trigger) - rdeangel
  description: "Blueprint Version: 12-01-25\n
    Blueprint Name: Zigbee2MQTT - Sonoff 1-Button Switch (MQTT Device Trigger) - rdeangel\n\n
    This blueprint uses MQTT `device` based triggers and it will be triggered
    only when the selected Device MQTT messages are received."
  domain: automation
  input:
    mode:
      name: Automation Modes

rdeangel

blueprint:
  name: Zigbee2MQTT - Tuya 4-Button Switch (MQTT Subscribe Any - Filters Multiple Devices) - rdeangel
  description: "Blueprint Version: 11-01-25)\n
    Blueprint Name: Zigbee2MQTT - Tuya 4-Button Switch (MQTT Subscribe Any - Filters Multiple Devices) - rdeangel\n\n

    This blueprint subscribes to all Z2M Action topic `zigbee2mqtt/+/action`
    and then filters the correct MQTT topic.\n
    It takes multiple dropdown as the main filter condition to decide if the trigger should be considered for actions or ignored.\n
    The fact that the automation triggers even when other mqtt devices actions are received it's not ideal, it does however
    allow for multiple buttons to be driven by the same automation if that's what you are looking for.\n

rdeangel

blueprint:
  name: Zigbee2MQTT - Tuya 4-Button Switch (MQTT Device Trigger) - rdeangel
  description: "Blueprint Version: 11-01-25\n
    Blueprint Name: Zigbee2MQTT - Tuya 4-Button Switch (MQTT Device Trigger) - rdeangel\n\n
    This blueprint uses MQTT `device` based triggers and it will be triggered only when the selected Device MQTT messages are received."
  domain: automation
  input:
    mode:
      name: Automation Modes
      description: https://www.home-assistant.io/docs/automation/modes/

rdeangel

blueprint:
  name: Aqara Buttons All-In-One [Zigbee2MQTT] (MQTT Device Trigger)
  description: "Blueprint Name: All-In-One package for Aqara Switches.\n Blueprint
    Version: 12/01/2025\n\n Updated to use device specific `mqtt device actions` (rather
    than previous wildcard version )\n Aquara action types posted by nwootton [here](https://community.home-assistant.io/t/aqara-wireless-switch-zigbee2mqtt-single-double-and-hold-action/275984/27)"
  domain: automation
  input:
    mode:
      name: Automation Modes
      description: https://www.home-assistant.io/docs/automation/modes/

rdeangel

blueprint:
  name: Only One Switch "On" At Any One Time
  description: '## It ensures "only one" entity (from the linked entities) is "On"
    at any given time (v1.0.2)

    Select multiple entities to link their single "On" exclusive state.


    If any selected entity is turned on, all the other entities in the group are turned
    off (allowing only one entity to be on at any one time)