#I tried to fix the condition to remove
slim heath
So, those selects can flip back if they don't get set "properly" (error on the inverter or whatever), right?
Ok, so you want the automation to run only on weekdays between 05:00 and 22:00?
This condition is fine:
- condition: time
after: "05:00:00"
before: "22:00:00"
weekday:
- mon
- tue
- wed
- thu
- fri
tardy sleet
Hello
They can get rejected I think
I am not sure if they can fail to get set properly but that might be what the rejected means but I have only seen that with the Solar Assistant device that is USB connected to the inverters, it rejects these changes sometimes.
I wanted to delete the 0500 and 2200 thing. I was able to delete them in the YAML but not the UI so I solved that I think
The 0500 was a holdover from a prior version of this automation when I had a smaller battery and had to get more creative
slim heath
Ahhh, gotcha.
Ok. So, I see what you're doing... it should work.
But, I would strongly encourage you to change from device actions to entity actions.
tardy sleet
oh..
all i care is that the UI gives me one of the options and doesn't make me type in a string
too much room for error
slim heath
I get it and you can still use the UI, but entities are a lot safer than devices.
The doc I linked can explain why.
tardy sleet
okay looks like entity still gives me a drop down.
slim heath
It does 🙂
tardy sleet
yea I think I've had the issue with devices breaking my automations before
tardy sleet
yea im not one of the cool kids 🙂
slim heath
You'll get there.
tardy sleet
i do the bare minimum in HA. I'm only doing this because Solar Assistant doesnt have a day of week automation
slim heath
lol fair enough.
tardy sleet
it lets me change these things based on time of day, but not day of week.. the programmer told me to just turn it off on weekends
so glad i paid for that 🙂
though i need solar assistant to make home assistant possible so i shouldnt complain too much
slim heath
lmao... "just turn it off"... oh man... some people...
slim heath
Nope. You want the select.select_option service call.
It'll look like this: https://imgur.com/a/TYIrMWT
tardy sleet
from the yaml it looks like thats what i am doing, but it still using the IDs
okay that looks different. I'll try that
slim heath
And use the "Choose entity" button and not the device.
tardy sleet
damn that makes me use a string, i dont see my options populating
slim heath
It'll look like this in YAML:
service: select.select_option
data:
option: "Off"
target:
entity_id: select.attic_light_1_power_on_behavior
It does, but unless you REALLY fat finger it, you'll be fine.
You have the values already in your automation, just copy them from there..
tardy sleet
any idea why the entity isnt working there? do i need to format the numeric value differently