systime, again!

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
GG42
New user
Posts: 3
Joined: 12 Apr 2021, 19:45

systime, again!

#1 Post by GG42 » 26 May 2021, 23:35

Why this condition does not work any more?

" if %systime%>00:40:00 and %systime%<21:14:00 "

My script works within and OUT of this time condition. It seems it works well in the past, what happens?
Thank you for your help.

User avatar
ThomasB
Normal user
Posts: 1064
Joined: 17 Jun 2018, 20:41
Location: USA

Re: systime, again!

#2 Post by ThomasB » 27 May 2021, 06:07

The rule condition you posted requires system time to have been retrieved (e.g. WiFi successfully connected to NTP). Also Tools->Advanced->Timezone Offset UTC must be correctly set. Otherwise %systime% value won't be valid.

FWIW, In case there is a logic issue I suggest posting the entire rule page so the experts can review it.

- Thomas

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: systime, again!

#3 Post by TD-er » 27 May 2021, 08:58

Apart from Thomas' suggestion about the time which must be set (e.g. this check will probably not work at the boot event), can you try to split the line in two lines and create a logentry to check the time check is working for at least one compare?

See: https://espeasy.readthedocs.io/en/lates ... .html#time

Another check could be to check with the %syssec_d% variable (number of seconds of today)
Just to see if there may be an issue with the time parsing.

What build are you running?

Post Reply

Who is online

Users browsing this forum: No registered users and 39 guests