Date and Time
Once selected, any actions you associate with this trigger will activate at the time you specify. For example, you might create a meshbot which updates a Google spreadsheet with the latest sales figures from your team every Wednesday at 2pm. Or you could activate your night house-mode between 11pm and 6.30am every day.
- MiOS uses the ISO 8601 standard for representation of dates and times.
‘Date and Time’ contains the following options:
- Custom Time
- Special time of the day
- Days of the week
- Days of the month
- Weeks of the month
- Weeks of the year
- Months of the year
- Combining Date/Time triggers
Activate the trigger before or after a specific time, or between two times. You can also pick whether the trigger activates daily or only on certain dates. This trigger is useful when paired with other date-time triggers as it is the only one that lets you choose an exact time.
- Before — means ‘Start at midnight and run until the time you specify’. For example, ‘Before 8 PM’ will run from 12.00 AM until 11.59.59 PM.
- After — means ‘Start after the time you specify and run it until midnight’. For example, ‘After 8pm’ will run from 8.00.01 PM until 11.59.59 PM.
- Between — Runs the trigger between the two times you specify on your given days. For example, between 6 AM and 7 PM. If you set the start time before the end time then you can create a span over midnight. For example between 7 PM and 6 AM will run the trigger from 7 PM till 6 AM the following day.
Special time of the dayRun the trigger every day from sunrise or sunset in your location until midnight. You can offset this by a specific length of time before or after sunset/sunrise. Special times vary according to your location and the time of the year and are set by your region’s weather service.
Days of the month
Run the trigger on certain days of the month from 12.00 AM until 11.59 PM. You can connect this to a ‘Custom Time’ trigger with an ‘AND’ operator if you want it to run at specific times on those days.
Weeks of the month
Run the trigger on certain weeks of the month starting 12.00 AM on the first day through to 11.59 PM on the seventh day. Week 1 starts on the first calendar day of the month.
Weeks of the year
Run the trigger on specific weeks of the year starting 12.00 AM Monday through to 11.59 PM Sunday. This type of trigger is of particular interest when creating meshbots related to financial/taxation/payroll tasks.
- Week 1 starts on the first Monday of the year at midnight and runs until 11.59 PM on the Sunday afterwards.
- All subsequent weeks also start at midnight Monday. So, for example, ‘Week 22’ starts on the 22nd Monday of the year.
- Some years have 53 Mondays in them, so these are classed as 53 week years.
- This happens if the year starts on a Thursday or is a leap year that starts on a Wednesday.
- You can find the exact start and end dates of any week number at https://www.epochconverter.com/weeks
Months of the year
Run the trigger on specific months starting at 12.00 AM on the 1st of the month through to 11.59 PM on the last day of the month.
Run the trigger on specific years starting at 12.00 AM on the 1st of January through to 11.59 PM on the 31st December.
- Use this trigger in combination with other date/time triggers for longer-term events that occur every other year or so. For example, maintenance on your heating or air conditioning systems. You could create a meshbot to send a notification to building staff to schedule the maintenance on a certain date in a specific year. Or a reminder to replace the light bulbs on a certain floor when they are nearing the manufacturers end-of-life date.
- This trigger can also be used in combination with other date/time triggers to create exceptions. For example, you have a task set to run according to a regular schedule, but don’t want it to happen in a particular year. You would use ‘NOT’
in this case.
Interval causes the meshbot to re-evaluate the rule every X seconds/minutes/hours/days as required. The trigger activates (becomes true) for a brief period at the interval you specify, and deactivates (becomes false) shortly afterwards. This lets you create ongoing/background tasks that aren’t necessarily tied to a particular date and time.
- All intervals are set relative to midnight. For example, a 30 minute timer will run at 00.00, 00.30, 01.00, 01.30 etc, and every half-hour on the half-hour thereafter.
Note – midnight is not the start time — the trigger will run from the moment you activate it, but its run is tied to the midnight-relative blocks just described.
- ‘Interval’ makes the action become true for a brief period then false again right afterwards, rather than leaving it true until told otherwise.
- ‘Interval’ vs. ‘Repeat’. If you simply want to have an action take place at regular times then you are probably better using the ‘Repeat’ function in the ‘Action’ part of the rule instead. For example, you want Alexa to issue voice notifications every 90 seconds if a door is unlocked, but stop issuing once it is closed (i.e. the trigger becomes ‘false’).
- You can link date and time triggers with an ‘AND’ operator to create more targeted triggers. Both triggers must be true before the rule will proceed to the action.
- This example shows a ‘Days of the Week’ trigger linked with a ‘Custom Time’ trigger. The full trigger will become active at 8 PM on Fridays and Saturdays:
Other operators / logic gates you can use to link triggers include ‘OR’ and ‘XOR’. See ‘Operators’ for more details on these.