Docs / Using Rotorloop
Schedules
Plan when rooms are in use and equipment runs, with holidays and special days.
A schedule sets a group of points to one value during the times you choose, and to another value (or back to the building's own control) the rest of the time. Use it for when rooms are in use, when equipment runs, a boiler's night setback, or anything else on a timer.
Schedules are kept and run by the site's Connector, not the cloud, so they keep working if the internet drops and continue after a restart.
Make a schedule
- Open Schedules and choose New schedule. Admins can create and change schedules; everyone can see them.
- Name it, then choose what it controls. Only points an admin has made adjustable are listed. Everything in one schedule takes the same values, so the points must be the same kind: all temperatures, all on/off, or all with the same options.
- Set during scheduled times (for example 70°, On or Occupied) and the rest of the time, or tick Hand back to the building's own control.
- Plan the week, add any special days, and Save.
Plan the week
| To | Do this |
|---|---|
| Add time | Drag across a day. On a phone, tap a day to add two hours, then adjust. |
| Move a block | Drag it. Blocks snap to 15 minutes; exact times can be typed in 5-minute steps. |
| Make it longer or shorter | Drag either end. |
| Exact times, remove, copy | Click or tap the block. Copy that day to any other day, or to every weekday at once. |
| Keyboard | Arrow keys move a block, Shift with arrows changes its end, Delete removes it. |
A block that ends at midnight and one that starts at midnight the next day work as one overnight period, such as Friday evening to Saturday night.
Holidays and special days
Add a date or a range of up to a month. Each is either Not in use all day or has its own hours, and replaces the normal week on those dates. Past dates do nothing; remove them to tidy up.
How schedules and people work together
- A person's change always wins. If someone holds a room at 66° for two hours, the schedule waits, then takes over again when the hold ends.
- Same limits as people. A schedule can only set values a person could: within the point's range, with the same wait between changes and the same minimum on and off times for equipment. Life-safety points are never written.
- One schedule per point. Two schedules can't fight over the same point.
- On BACnet, schedules write at priority 12 and people's holds at 8. Turning a schedule off, deleting it, or handing a point back clears priority 12, so the controller's own logic takes over.
- On Modbus, points need a release rule before they can be adjusted at all. When a schedule hands a point back, that rule restores the value that was there before.
When a schedule can't make a change
A yellow note on the schedule says why, for example a point was made read-only or its limits no longer allow the schedule's value. The refusal is in the activity log once, and the schedule tries again when the problem is fixed.
Time zone
Schedules follow the site's time zone, including daylight saving: 7:00 stays 7:00 when the clocks change.