You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m encountering an odd behavior that I’m unsure how to resolve or even troubleshoot effectively.
I’m running six Adaptive Lighting services, and everything has been working great for a while. Recently, I decided to rename my Home Assistant entities to adopt a new naming convention. However, this has turned into a nightmare for two of the six services, as they stopped working after the renaming, and it took me a while to figure out why—or at least what’s causing the problem.
Here’s what I discovered:
If I rename the default entity ID (e.g., switch.adaptive_lighting_sleep_mode_dining_room) to my desired format (e.g., switch.dining_room_sleep_mode), the integration stops working (e.g., toggling sleep mode has no effect).
Reverting the entity ID back to its original name makes the integration work again.
This behavior applies to all four entities of the two affected services.
As a temporary workaround, I’m avoiding modifying the entity IDs, but I’d like to understand what’s causing this behavior and how I can fix it. Sticking with the original names is disrupting my naming convention, and having these last eight entities outside the standard is stressing my OCD quite a bit.
Any insights or suggestions would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
I’m encountering an odd behavior that I’m unsure how to resolve or even troubleshoot effectively.
I’m running six Adaptive Lighting services, and everything has been working great for a while. Recently, I decided to rename my Home Assistant entities to adopt a new naming convention. However, this has turned into a nightmare for two of the six services, as they stopped working after the renaming, and it took me a while to figure out why—or at least what’s causing the problem.
Here’s what I discovered:
As a temporary workaround, I’m avoiding modifying the entity IDs, but I’d like to understand what’s causing this behavior and how I can fix it. Sticking with the original names is disrupting my naming convention, and having these last eight entities outside the standard is stressing my OCD quite a bit.
Any insights or suggestions would be greatly appreciated!
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions