As I said in github, I think you would need to persuade each binding maintainer about use of per-channel “veto”, as the best place to make that decision.
The only place I am currently sure that gets used is Zigbee binding, and has of itself led to surprises. Long tale about that -
The binding can work in command-response mode (hurrah! let’s veto autoupdate)
or can work in command-silence-eventual poll mode (oh - now I want autoupdate!!)
and this presents a conundrum.
