You just type the value you need in and save.
Blacky
There’s a bit more to it. The best way is to use a template sensor to handle “unavailable” states. For example: if the sensor is 'off'
or 'unavailable'
, treat it as OFF, otherwise treat it as ON.
{% if states('sensor.your_christmas_sensor') in ['off', 'unavailable'] %}
off
{% else %}
on
{% endif %}
Blacky
I’m having an issue where restarting HA triggers lights to turn on, even when they were off before the HA restart. Any idea what the underlying condition in the BP is that might trigger that given the trigger entity was only unavailable or off?
If you restart HA and the light comes ON it is because your trigger is ON. Check to see what happens to your “Front Door Activity” when you restart HA.
Blacky
When using a script as target to turn on lights - how do I pass data? For example, I have a script to turn on a random light given a light group entity id. I want to call this script with a specific entity id from this automation.
Thanks but as you can see from the previous screenshot that is not the case. What does happen is the trigger becomes “unavailable” for a period during startup but that is it.
Your probably best to ask this in the forum creating a new topic or search for one similar. There are many people that can help you on that. I try to keep my blueprint posts bout the blueprint so they stays on topic.
Blacky
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
Blacky
Hi Blacky - since last week your blue print became unresponsive. I tried reimporting your blue print which gave an error. Then I deleted the blueprint and tried to import it again manually, but that also gave an error.
I’m using:
Installation method
Home Assistant Container
Core
2025.9.1
Frontend
20250903.3
The homeassistant/motion_light.yaml is working just fine with my devices. Any ideas on what might be causing this issue and how to fix it?
Kr,
Marco
I was able to re-import the blueprint. But the blueprint still doesn’t work. The same devices do work with other blueprints. Really puzzled about this, because for now I only use the trigger and the devices and leave all other options unused.