Skip to content

Limit a Link’nX scenario to a daily time range

Link’nXAdministratorInstaller

Link’nX web: Time range condition, selected in the scenario’s Time condition field

The Time range condition in Link’nX checks whether the installation’s time falls within a range, for example from 08:00 to 18:00, or from 22:00 to 06:00 across midnight. It is evaluated when the scenario receives a trigger.

Intended for administrators and installers. To cause an event at a given time, use the Timed trigger instead, then add the necessary conditions to the scenario.

  1. In Conditions, click Add, then choose Time range in Select a condition type.
  2. Fill in Name, for example “Reception hours” as a fictitious example.
  3. Click in From - Start time, choose the hours, then the minutes in 24-hour format and confirm with OK.
  4. Do the same in To - End time. CANCEL closes a dial without confirming its choice. Review both times in the form.
  5. Click the floppy disk at the bottom right, then follow the save confirmations.
  6. In the scenario, choose this condition in Time condition, then save the scenario.

The start and end minutes are part of the range.

StartEndRange covered (fictitious examples)
08:0018:00During the day, from 08:00 to 18:00
22:0006:00From the evening to the next morning, across midnight
Identical timeIdentical timeThe condition does not limit the scenario to that single minute: use different bounds to define a limited range

The condition does not automatically start the scenario at the beginning of the range and does not, on its own, stop actions already requested at its end. Delays and interruptions are configured separately.

Reopen the condition and review both saved times. After the scenario has been triggered, check the time of the event in the history and compare it with the range.

  • Issue with field ‘Start time’ or ‘End time’. It requires a value.: reopen both dials and confirm each time.
  • The behavior remains unexpected: check the saved range, any midnight crossing, the condition chosen in the scenario and the time of the event in the history.
  • A time offset is observed: do not change several ranges to compensate for an offset that has not been established.

For a time zone difference or an effect that remains unexplained, contact support@can-nx.com with the date, the configured times, the expected time and the checks already made.