For example, 1) I have group of clever lams, everything works good, but turn off has lag, when I turn off classical wall switch is about 40 seconds. But I have accessed router API, and can monitor no link to lamps in one or two seconds. So, it will be nice to take lamp group and override turn on/turn off state, and use custom command line sensor. Templates lamps have many parameters, it will take a lot of time to make my own lamp, but I only need to fix one parameter 2) I have broadlink switch, and also have usb arduino sensor (when I have 5 volt usb - I have TV turn on). I have broadlink switch, and also template switch. But it will be better to override native broadlink switch parameter, (state on /off) and have only one switch 3) I have smart tv, but shutdown time in smart app and smart tv component too large. It will be better, if I could override tv state and use my sensor 4) Media player component has wrong next track / previous track button. But I found correct broadlink codes for such buttons. And it will be nice to replace such buttons in native webos tv component.
- I also have yeelight lamps, when they have bright less than one percent, I have automation to turn off broadlink wall switch. But I can’t turn them on. I need to use another switch in lovelace. But it will be better to override state of lamps from unknown to off, when I will be able to write automation, when bright more then zero, turn on broadlink wall switch. // In fact, everything can be done old way, but a mountain of unnecessary switches and timers are created, which then still fall into the Google assistant. They also spoil cpu and use database for unnecessary states. //// Maybe template lamp format is nice, but only for one parameter, with opportunity to override
Maybe blueprint now will fix something, but I can’t put lamps, created in yaml to areas, why in is not possible?
Override parameters can be achieved in universal Media player, using “child” attribute, but we need same attitude in lamps.