Switch manager is a centralised component to handle button pushes for your wireless switches. This includes anything passed through the event bus. The component relies on switch blueprints which is easily made to allow GUI configuration of your switches and their button pushes. This helps remove clutter from the automations.
[ ] You ordered the actions as stated in the README action order
[ ] All filenames are lowercase and uses '-' for spaces and not '_' while using {service-name}-{switch-name-or-type}.yaml format
[ ] Images are png
[ ] Image backgrounds are transparent and is cropped to the device boundries
[ ] Images has a maximum width of 800px and maximum height of 500px
[X] There are no missing buttons or actions
[X] Your integration/service is running on the latest version
[X] You have tested your blueprints and made sure each button and action works
Zigbee2MQTT
[X] (older devices) You have ensured legacy is off/false for the device in the Z2M devices Settings (specific) page and that your actions matches those with legacy off?
Correct the issue #64, action keys previously on the blueprint were the ones with the legacy parameter set to true in Zigbee2mqtt.
Sian-Lee-SA
commented
9 months ago
Blueprint Checklist
Zigbee2MQTT
Correct the issue #64, action keys previously on the blueprint were the ones with the
legacyparameter set totruein Zigbee2mqtt.