This is my automation for my outside lights. The dashboard says they are on but they are not.
If I go to the dashboard turn them off then back on then they come on… Not sure what I missed here.
It does fire every night but no lights.
BTW, the syntax you are using is a bit dated (for example, data_template was deprecated in favor of data many versions ago). Here’s the current syntax:
Thank you! I cannot edit automations directly from the automation screen or debug them they are not in the automations.yaml file they are all seperate files in an automation directory Even when I put them in the automation.yaml I still cannot debug or ‘trace’ them as they have no unique id.
All my automations are also created with a text editor and I add a unique_id so the automation will have traces (there’s also an option to control how many traces are stored; the default is ten). However, ensure the value of unique_id is a valid slug. In other words it’s the same naming rules as for entity_id (alphanumeric characters with no spaces or hyphens, underscore is permitted).
Couldn’t use h or hue went with xy that works… there is no brightness so it fails… tried saturation and it says ‘NO’… so not sure how I’m going to get that part… hummmmmmmm
Glad to hear it helped to solve the problem. Please consider marking my post above with the Solution tag.
Regarding the brightness attribute, it might be something specific to the model of light bulb you are using. I say that because I just tested it with a Philips Hue bulb ( setting both xy_color and brightness in the same service call) and it worked.
WOW Thank you. I’m not a programmer know just about enough to be dangerous but as I read through that it makes perfect sense to me! Yes I will use that! Thank you! It’s gripping about the - is part but I’m assuming that’ll be okay. “Property is not allowed” LOL