I have been successful in configuring the integration BUT it seems to trigger first thing in the morning! Not sure why this is happening.
I’d post the code but it’s only 4 lines with no options so I’m thinking it’s broken?
Thanks!
I have been successful in configuring the integration BUT it seems to trigger first thing in the morning! Not sure why this is happening.
I’d post the code but it’s only 4 lines with no options so I’m thinking it’s broken?
Thanks!
Id love to see the code, some of my third partie integrations will try to overtake some of my automation.
What device and automation are you using?
Here is the code.
# Trigger lights based on sun light
device_sun_light_trigger:
light_group: group.livingroom
light_profile: soft
disable_turn_off: true
It’s turning on the lights at 5:30am.
Did you want the “whole” configuration.yaml file?
What integration is this from? And it would helpful to see the entire automation, not just four lines out of context. I can’t even tell if what you posted is a trigger or an action. Or maybe it’s a scene?
A very generic answer based mostly on guessing is that if you’re using the Sun device, then it has a bunch of different triggers, and there is a difference between dawn and sunrise. So you might be using the wrong trigger.
This is the Presence-based Lights integration
built-in to Home Assistant. The description says it does this automatically after sunset when people are present.
I’m not using any triggers based on the documentation. If you’re saying that I have this done wrong, I will add an automation. But for now, I have have what is in the config. yaml file.
I’d not seen that integration before, but at least the helps understand what to look for. My bet is that one or more of your device trackers or person entities are going “away” or unavailable and then back to “home.” At 5:30am that will most often be “after sunset,” so once the device tracker or person “comes back” it triggers the integration and turns the lights on. I’d suggest looking at the entities for your device trackers and people and see if one of them is going away and coming back right before the integration triggers.
This is the reason I do stuff like this in automations. It’s easier to track down the problem because you get actual traces of the automation running.
Thanks for the idea. I will look into that.