I need some advice on how to setup a Dust Collection automation in HA

[jagged oar]

Hey folks,

I am building a bunch of 3d-printed blast-gates for my shop dust collection system. These gates use an ESP32 and a servo to open/close a gate to maximize suction to a given tool in the shop.

I will have 10 gates in total, each with its own ESP32.

I had some help setting up ESPHome already and so I have the gate entity exposed in HA and have confirmed I can move the servo.

I plan on using Pico remotes at each tool to open the corresponding gate while closing any others that are open.

I also want each remote to turn on my dust collector. I managed to setup my Bond Bridge to turn the collector on/off via RF.

I should mention that I want to be able to set the open/close position each gate/servo independently in any script/automation.

Looking for an efficient way of setting this up. Anyone have any suggestions?

[novel sedge]

Well if you really want to get fancy, put a power sensor on each machine and have that monitor for when you turn it on and switch the gates appropriately

Simple way is to just record a scene for each machine (which gates are open/closed) and have your button activate the scene

Alternatively you might be able to do some sort of compact system - e.g. Press button X, open gate X and close the rest etc, but that will require a bit more work to set up (and some templating)

[jagged oar]

Yah, I've contemplated either using power sensors (like an Emporia Vue with ESPHome firmware), or even vibration sensors, but for now a simple remote will suffice. I'm looking to do the later of your suggestions. I need it to be smart (ie. turn on the dust collector and open the gate for the tool i'm at while also making sure the others are closed)

[novel sedge]

Both of them can do that, you could just make a scene which has:
Dust collector on
Tool gate open
All other gates closed
X however many tools you have set up

[novel sedge]

But to do it dynamically with a template:
Make a label for all your gates
Name them something like "switch.gate_table_saw" and have your buttons be "button.table_saw" (basically have everything after the . in the entity name be in the gate control, could just be 1, 2.. But I find that less helpful)

You can then add a state trigger and include all your buttons in it

You can get your "key string" with the template: {% set key = trigger.entity_id.split('.')[1] %}

Get your gates to turn off:
{% set turn_off = label_entities('gates') | reject('search', key) %}

You can get the gates to turn on with the same but select rather than reject