Replies: 1 comment
-
|
Okay, I figured this out by looking through the logs. For the lights that weren't working the trigger being sent wasn't being recognised as a light turn on. It was a device identity being sent and so AL ignored it. Then the light turned on and it assumed it was being done by another service and marked it as manually controlled. The issue was that in the automation I had selected the light as a device rather than an entity. For anyone else having a similar issue, double check this as it is easy to do. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have three nanoleaf A19 bulbs in my hall. The colour/brightness are controlled by Adaptive lighting, in the same integration entry. I recently added a presence sensor to trigger them and configured this to turn on the middle-hall light. This works as it should with Adaptive lighting changing the colour with each turn on.
I was then able to add zones to the presence sensor, and set up other zones to trigger the lower and upper hall lights. But when they turn on via the presence sensor they aren't adapted by AL, they are when I activate them manually in home assistant.
I have even tried setting them up in separate but identical integration entries, however they still behave the same way.
The presence automation is just the standard HA blueprint one so shouldn't be sending brightness/colour information which might overide the AL commands.
If it was an issue with the command only being sent to one light I would have thought that splitting to multiple integration entries might fix it, and if it was a problem in the configuration then I don't understand why one light works but the others don't.
Any help would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions