Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ceedee]

I have a device that turns on at sunset.  Another device turns on 5 minutes before sunset.  Tonight’s log shows the "sunset" device turning on at 8:05, which suggests that the other device should turn on at 8:00. It did not.  It turns out that I have a third device that turns on nightly at 8:00. That turned on. So, tonight, two commands were sent at exactly 8:00, and only one command succeeded.

Is this an issue?

[HA Dave]

….. So, tonight, two commands were sent at exactly 8:00, and only one command succeeded.

Is this an issue?

It would be for me! But if you have dusk/dawn triggers as well as similar triggers set at a static time within the dusk/dawn window.... that should happen maybe twice a year. One solution would be to set a secondary ON (and likely also OFF). So that it would turn ON exactly at 8. Then turn ON (or OFF) again at 8:03. That way on the one or two times a year when dusk/dawn interacts with your static timer.... at least the static time will get a second chance. But then again.... the static timer could always interfere with the dusk/dawn trigger too.

[ceedee]

Yea, the static timer worked, and the D/D timer did not.  I will have to regroup.  Thanks.

[Brian H]

There are other threads here on Dusk Dawn.
There is a reported Dusk Dawn being addressed in the next APP release. That is waiting for IOS approval before Android and IOS versions are released.

[Tuicemen]

I reported this to Authinx so maybe the developer can have a look at the code.
It is possible the next update will not have this issue as the dusk dawn timer code did get an overhaul as Brian stated.