It’s the tier. A board control only sends commands that are in the profile’s catalogue, Basic tier, and not high impact. Privileged, Critical and anything marked high impact get refused from a board on purpose (“send it from the device console”), so the picker doesn’t offer them.
We run a loading-bay door the same way. Set gate.pulse to Basic and untick high impact, then leave “Ask before running” on in the button’s action, so the operator still gets a confirm dialog (the server enforces it too, nobody skips it from another client). Bind a status line to door_closed so people see what the door is doing, not what they pressed. Who may press it is down to permissions: Run widget commands plus permission to send basic commands. Night shift gets those, people who only look at the board don’t.
And one thing on the ESP32 side: a command can arrive twice. Keep the last 32 request ids for 10 minutes and don’t run the same id again. For a gate that toggles on each pulse this matters, a duplicate means it opens and closes again.
Page with the board rules: Control cards.