Presence Simulation

Presence Simulation learns the real weekly pattern of the lights and shades you already control from RTI, then replays that genuine pattern while you're away so an empty home looks occupied — no hard-coded on/off timers, no obvious loop. It runs entirely on the RTI processor: no cloud service, no account, nothing leaves the site.

Key Features

• Learns your own routine: watches the on/off state variables of your existing lighting/shade drivers and records when each load actually switches, day by day.
• Realistic replay: plays back the learned pattern while armed, with a configurable random jitter so timing is never a perfect repeat — and naturally tracks sunset and the season because it's replaying what you really did.
• Up to 25 loads: each load points at its own on/off state variable and its own Turn-On / Turn-Off macro; slots reveal progressively as you name them.
• Exclude from Simulation: per-load flag to keep learning a load (e.g. a motion-triggered garden light) without ever replaying it.
• Snap to last week on arm: optionally sets every load to the state it was in at this time last week the instant the simulation starts, so the house looks right immediately.
• Flexible arming: auto-start/stop from an existing Away/Armed boolean system variable (with an optional arm delay), or arm/disarm/toggle from any macro or keypad button.
• Learning progress feedback: Recorded Events, Days Recorded and a Pattern Ready flag/event show when there's enough data for a realistic weekly replay.
• Runs 100% on the processor: the learned pattern is saved locally and survives reboots — no cloud dependency at all.

Requirements

• RTI XP processor (runtime 24+, Integration Designer 11.4+).
• The lights/shades to be simulated must already be under RTI control via their own driver(s), each exposing a boolean on/off system variable plus Turn-On / Turn-Off macros — Presence Simulation orchestrates existing drivers, it doesn't talk to hardware itself.
• About a week of normal, occupied use after install so the driver can learn a representative pattern before you rely on it while away.
• Optional: an existing Away/Armed boolean system variable (alarm panel, guest-mode flag, etc.) for automatic arm/disarm.

How It Works

Point each Load at the on/off variable and On/Off macros of a light or shade you want simulated, then leave the system running normally for about a week. The driver quietly records every switch and, once enough days are captured, is ready to replay that same pattern on demand. When you go away, arm the simulation — either automatically via your existing Away variable (with an optional delay) or with a macro/button — and it fires your existing Turn-On / Turn-Off macros at the times you genuinely used them, jittered slightly so it never looks scripted. Disarm it (or let the Away variable go false) and the house goes back to being controlled normally, while the driver keeps quietly learning in the background.