Why doesn't porch light turn off at 11:30 PM?

🧰 Built-In Apps and Drivers Basic Rules
23

What you likely mean is that you moved your Kasa devices from using a cloud-dependent integration with Hubitat to using a fully-local integration.

Either way, these devices are always connected via WiFi.

FWIW, I’m pretty sure that @zbernie123’s Kasa devices are connected locally.

1 Like
24

image
image1600×900 159 KB

Turn off Cloud binding and Use Kasa Cloud for device control on the preferences page.

25

Yes, locally.

26

Thanks! We will see tonight at 11:30 PM!

27

My stupid mistake -- The porch light switch is one of the few Z-Wave devices that came with the house. I have Kasa on the brain!

1 Like
28

Does basic rule allow almanac offsets? Ie sunset + or - If so sunset minus x hours so it will trigger at a more convenient time. But your issue is not the on at sunset trigger but the off after waiting. Get it working then modify it to suit. Just trying to save you some time.

29

Yeah, this is how I test something like this too.

Although, the trigger isn't the problem here. Run Actions is identical to the rule being triggered, but for the trigger itself. So there's really no reason to mess around with the trigger.

30

This is a new term for me -- please explain "almanac offsets".

31

Here my reference to an almanac refers calculating events in this case sun rise and set. But also moon phases, Ebb and flow of tides, and the changing of seasons. So sun(set/rise) offset. Turn on the outside lights at Sunset +15 minutes and turn them off at Sunrise -15 minutes.

32

Got it! Thanks!

33

I believe the issue was that I was testing this rule AFTER sunset, so that initial trigger never fired off, as someone in this thread suggested. It's working now!

3 Likes
34

Another strategy is to trigger at the on time and another trigger at the off time with a little test in the rules to sort out what to do. That way there is no running timer to get canceled. But you got it working and know how not to break it. The more we do with hubitat the more we learn.

35

There is no such thing as a 'running timer'. There is a scheduled job resulting from the Wait. Your solution also involves a scheduled job, for the second trigger, but then burdens the rule with extra logic to figure out what is going on.

36

This topic has reached it's logical conclusion and solution.

2 Likes