The blueprint should survive a restart. I test it again when everyone is sleeping. If you can provide me you YAML of your settings so I can test your exact set up that would be great.
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.
When binary_sensor.con_badtuer_inverted is turned ON, the blueprint will stop running.
The only action it may still perform is the Restore Dim Before OFF option, but only if the light is currently ON. Since you are not using this option, it will have no effect.
If the light is OFF, it will remain OFF.
If the light is ON, it will remain ON.
While the bypass is ON, the blueprint is effectively disabled. The only functionality that would continue to work is other bypass options, but since you are not using any, nothing else will run.
Close, the time condition is to only allow the automation to run at this time. If the lights are ON then it will turn them OFF because we are saying to only allow the lights to be ON between these times.
You can use a LUX sensor that is in the room and the blueprint has options for this.
Yes you can do this
NO - My Ambient Light Sensor is not affected by the Lights
Ambient Light - Low Lux Value = 80
Ambient Light - High Lux Value = 180
and you have 2 time delays for your low and high to slow down the lights if they turn ON / OFF to quickly. Example if it goes above 180 for 30 seconds and then drops below 180, if you set a Ambient Light - High Lux Time Delay to 1 min then the light will stay ON but if it goes above 180 for over 1 min then the light will go OFF.
You need to use a diffrent blueprint. Have a look at this one Manual light control with auto OFF. You also have options so once you turn it ON manually the motion sensor can keep it ON. You also have a grace option that is handy.
I have seen this before. You need to make sure you set the Shelly correctly (Device type) and wire them correctly. Have a look at this YouTube video at the 2:50 mark to 5:40 mark. This has helped another member in the past.
I tested it here using a script to turn the light ON and a scene to turn the light OFF with a Scenes & Scripts - Toggle Helper. The helper turn ON when the automation is triggered and OFF when the light turn OFF.
If you like you could 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.
Youâre right, I thought it wasnât because of a poor design choice. When I put in a value of 9 or lower the text field would be underlined in red which I thought was an error because the number is out of the range. Turns out it was red for any number and saved without issues which I didnât initially try.
Thanks for the suggestion. I wired and configured the rgbw2s more than 5 years ago and they were working as they should with shelly4hass integration. The problem started after migrating to official integration, but that isnât the main reason for my request. I would like to have an option for âstaggered effectâ for my lights if itâs not too much work.
An option for a staggered effect when they turn ON. What you could do is have a script that does this. Then use the script in the Lights - Switches - Scenes - Scripts.