Home Automation - Smartkit

I use HA for my pool, gives better control, e.g. don't want to run the pump when it's overcast in summer.
 
SAguy said:
Are you setting a schedule with your Home Assistant for on/off?
I've got mine on HA, but using the Tasmota's own scheduler for on off - just using it in HA to manually switch on/off and to view power consumption.
Click to expand...
Took an. Hour or so last night and set the schedule up on ha... Was a bit of a mission but I want it all centralized.
 
One thing that frustrates me is that Home Assistant requires a separate automation for turning **** off.

Should really be in the same automation that turns it on and even better if you could simply state a duration.
 
SauRoNZA said:
One thing that frustrates me is that Home Assistant requires a separate automation for turning **** off.

Should really be in the same automation that turns it on and even better if you could simply state a duration.
Click to expand...

Guys, start using AppDaemon :p
 
Appdaemon is a proper script based object oriented automation tool for HA.
 
SauRoNZA said:
One thing that frustrates me is that Home Assistant requires a separate automation for turning **** off.

Should really be in the same automation that turns it on and even better if you could simply state a duration.
Click to expand...
I just used a delay on the automation.. Goes on at 4am and then delays for 6 hours and turns off
 
rorz0r said:
Could you paste some yaml for us noobs?
Click to expand...

Something along these lines..

I hacked it a little bit

automation:
- alias: 'Water Heater Schedule'
trigger:
platform: time
at: '04:00:00'
action:
- service: switch.turn_on
entity_id: switch.water_heater
- delay: '02:00:00'
- service: switch.turn_off
entity_id: switch.water_heater
Click to expand...
 
ToxicBunny said:
I just used a delay on the automation.. Goes on at 4am and then delays for 6 hours and turns off
Click to expand...

Why the hell call it delay then? No wonder I’ve missed it as I assumed delay would do as it says and delay the trigger.

Duration is a far more sensible word.

Would make a world of difference to my life for when I trigger things manually now.
 
SauRoNZA said:
Why the hell call it delay then? No wonder I’ve missed it as I assumed delay would do as it says and delay the trigger.

Duration is a far more sensible word.

Would make a world of difference to my life for when I trigger things manually now.
Click to expand...

In the context of how the automations are hung together, delay makes sense though...

You are stringing actions together, so similar to a powershell script of sorts.
 
ToxicBunny said:
In the context of how the automations are hung together, delay makes sense though...

You are stringing actions together, so similar to a powershell script of sorts.
Click to expand...

Not really as it doesn’t only that it will turn itself off after the time elapses.

Duration tells me it will be in it’s “switch stage” for the time given until it reverts to original state.
 
SauRoNZA said:
Not really as it doesn’t only that it will turn itself off after the time elapses.

Duration tells me it will be in it’s “switch stage” for the time given until it reverts to original state.
Click to expand...

I see it differently...

Within the "Action's" portion, you do X... then Delay and then do Y... in this case X is turn on, delay for period then Y is turn off.

Granted it could be done considerably neater and cleaner, but with how generic Automations is structured to be, it kind of makes sense.
 
ToxicBunny said:
I see it differently...

Within the "Action's" portion, you do X... then Delay and then do Y... in this case X is turn on, delay for period then Y is turn off.

Granted it could be done considerably neater and cleaner, but with how generic Automations is structured to be, it kind of makes sense.
Click to expand...

I agree with your way.

I have an automation that kicks off a script - give it time to execute (moving files) - then do another action. Duration won't make sense, its a Delay before executing the next step - which might have no connection to the first step.
 
Tinuva said:
Cool.

Now what if, there is mostion again, does that reset that 2:00:00 delay, or will the delay kick in, even if there was other motion since the first motion?
Click to expand...

Honestly I dunno if it would reset the delay... or merely institute a new delay on a different thread, where you may get some strange strange behaviour out of things.
 
ToxicBunny said:
I see it differently...

Within the "Action's" portion, you do X... then Delay and then do Y... in this case X is turn on, delay for period then Y is turn off.

Granted it could be done considerably neater and cleaner, but with how generic Automations is structured to be, it kind of makes sense.
Click to expand...

Looking at this page the way it's explained implies that the "delay" will simply pause the script and let it trigger later based on the time which is the way I read it.

https://www.home-assistant.io/docs/scripts/

So not sure how that is supposed to imply that it will trigger on and then off later based on the delay terminology and this is why I never used it as it didn't make sense the way people discussed it.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X