-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't automatically prefix entity name with circadian_lighting_
#18
Comments
Yes, I plan on making this change. My entities are all the same, with If I have enough time to make change #4 then I will definitely make the change then, as that would be equally breaking. |
Have you had time to begin working on this change? I just installed Circadian Lighting today and was disappointed that the configuration's |
Unfortunately not, along with this change I also need to update the integration to add everything to the entity registry to allow for changing the entity_id. Really, though, I want to implement this breaking change along with #4 as that would also greatly enhance functionality, but that's a significant amount of work that I unfortunately don't have time for currently. |
@frenck 👍 +1 |
Please don't prefix generated entity_id's with
circadian_lighting_
, this is not how Home Assistant does this in general.In my case, it screws with my naming schemes. e.g., I use a naming schema
<domain>.<area>_<name>
When adhering to my scheme, the switch for my hall would end up being:
switch.circadian_lighting_hall_circadian_lighting
😔The text was updated successfully, but these errors were encountered: