Open alexiri opened 11 months ago
Why not just use a substitution?
I guess I could, but this would force me to define it in all the other devices that already have a pin alias. Kind of defeats the purpose of aliases, then. I guess it wouldn't matter if I could define define the status_led
pin as pin: LED || $LED
or something like that.
Describe the problem you have/What new integration you would like
All of my devices include a basic yaml with general configuration, like
api
,ota
, etc. This configuration also includesstatus_led
withpin: LED
. This works fine with commercial boards which have a LED alias defined, but it doesn't work for custom boards.I'd like to be able to define custom pin aliases, something like this:
Please describe your use case for this integration and alternatives you've tried:
I can't reuse my common yaml templates unless the board has a defined LED alias already.
Additional context
This might also be solved by something like https://github.com/esphome/feature-requests/issues/2348, but this solution might be simpler.