Yeah I went the other direction, so the main driver does the “common” functionality and then the sub-drivers build on that to add features if needed.
Yes, although I can’t recall why I went down that route. I think it was to do with different things being available in the UI / Automations based on what category the device was in (Light vs Switch for example). It might have also been Alexa / Google related, I think there might have been a difference in behaviour there depending on what category the device was from.
Ah, that may have been another reason, I don’t think it was possible to change the icon historically.
Perhaps I should revisit that and test to see what the current situation is, it would knock off a large amount of profiles if I didn’t need to do that!
I did find a mention at Visible condition with Embedded Configs - #3 by blueyetisoftware but that seemed to suggest they didn’t work in profile .yml files. That was a while ago so maybe it’s changed.
Thanks for the pointers, it’s definitely helped!