#Automation - Notify
1 messages · Page 1 of 1 (latest)
Can you explain in more detail what the goal of this automation is?
- By the action aliases it seems like it is supposed to be stuck in a series of multiple hours-long Waits (which is not a good idea)... but for some reason, maybe for testing purposes, all the Waits are actually minutes-long.
- Then there's the input boolean that you turn on then check multiple times if it's off... then in the repeat, if it's off you turn it back on, wait for it to be turned off, and if it's not turned off you notify. It would be better to change the Wait for Trigger to just a Delay... you're already going to check the boolean, requiring the event to happen right then is excessive.
- All the wait's are based on a Tag trigger, but there should be some action linking the tag being scanned to the input boolean that you are using as the main condition throughout the automation.
My suggestion would be to set up a Local Calendar and have a repeating event for your trash day. This will allow you to setup Calendar Event triggers with different offsets from the event's start, so your automation isn't stuck in long waits. If you can clarify what you are trying to do we will be happy to help you restructure the automation.
If you want to send a notification 8 hours after 8:00, why not trigger it @ 16:00?
8am, notification to home assistant
2 sec delay before turning on a helper - delays for 8 hours. then its hour long delays.
The last block is hit at 8am.
My goal is to not have more then one automation to complete one task. simply remind my incompetent ass to stop forgetting to take the trash out lol
In the morning to start the process, mid way throughout the day to keep it in my mind, then annoy me later in the day( at night) if i still haven't done it.
Im sure hour long waits are not ideal but not sure how to do it wihtout creating 3 to 4 automations to complete this one task
I dont really want to mess with creating a local calendar yet
I got to this point from this discord... it was delays then was told to use wait for trigger, maybe miscommunication
Scanning of a tag is used to turn the boolian off and to advance the automation to make sure its just not sitting there when the task is done.
Then there's the input boolean that you turn on then check multiple times if it's off... then in the repeat, if it's off you turn it back on, wait for it to be turned off, and if it's not turned off you notify. It would be better to change the Wait for Trigger to just a Delay... you're already going to check the boolean, requiring the event to happen right then is excessive.
I dont see where it turns back on, there is an if garbage changes to off, i do see that last part is not actually finished to focused on the rest of it on why it skips
Then there's the input boolean that you turn on then check multiple times if it's off... then in the repeat, if it's off you turn it back on, wait for it to be turned off, and if it's not turned off you notify. It would be better to change the Wait for Trigger to just a Delay... you're already going to check the boolean, requiring the event to happen right then is excessive.
There is one more automation linking the tag to turning off the helper, so 2 automations to complete one task i guess
All the wait's are based on a Tag trigger, but there should be some action linking the tag being scanned to the input boolean that you are using as the main condition throughout the automation.
I originally wanted to use set times to trigger but from what i could find out that will require multipul automations.
for 1 hour delays - there is 5 total, each one sending me a notification - to phone( and brother phone when i get this figured out) the last block is hitting all my alexas
set a timer on your phone No. i dont want to.
plus, i hardly have my phone on me.
Goal: Remind me in the morning and a few times throughout the day then annoy me at night if i hadn't scanned the tag
More automations for the same task, from what ive could figure out.
I originally wanted to use set times to trigger but from what i could find out that will require multiple automations.
I think there is a big misunderstanding here... an automation can have multiple triggers. In a case like this where the actions are essentially the same it is possible to make your automation more efficient and more readable with only a few changes.
As I understand it you want the following schedule of actions:
8am: Reset Input boolean to 'on'
4pm: Send notification if boolean is still on
5pm: Send notification if boolean is still on
6pm: Send notification if boolean is still on
7pm: Send notification if boolean is still on
8pm: Send notification if boolean is still on
9pm: Send annoying repeating notification until boolean is 'off'
Here's one way to do that: https://dpaste.org/ieHtE
I would even prefer multiple automations above a very long wait. But you can also just add the trigger to this automation and use logic in the actions. For example a choose based on the trigger id.
That is exactly what i was looking for!
I do use the UI to make automations so i would have never figured that out