Coordinate ordered actions across devices, rooms, and subsystems.
GEM automation
Make the property respond as one.
GEM coordinates lighting, climate, shades, access, AV, energy, and other connected systems through automation that runs on the controller at the property.
One engine
More than schedules and scenes.
A macro defines the behavior. A schedule decides when it runs. A trigger reacts when the property changes. Site modes provide the context. Together they turn separate systems into one operating environment.
- 01Event or timeThe property changes, or a schedule becomes due.
- 02ContextConditions, modes, and exceptions decide what applies.
- 03Coordinated actionConnected systems carry out the sequence.
- 04VerificationState and history show what happened.
The building blocks
Behavior with time, events, and context.
Each part stays understandable on its own, while sharing the same devices, spaces, variables, and live state.
Respond to live changes with conditions, active hours, and protection against repeated events.
Use clock times, sunrise and sunset, date ranges, live conditions, and calendar exceptions.
Adapt behavior for states such as Home, Away, Night, Occupied, Party, or Maintenance.
Build
Shape the behavior the property needs.
Combine commands, delays, conditions, loops, variables, notifications, camera snapshots, wait-for-state steps, and—when needed—JavaScript.
Welcome home
Coordinate access, selected lighting, climate, shades, and AV as the property changes state.
After hours
Respond to a door, sensor, temperature, or equipment condition only during the hours that matter.
Close up
Run an ordered routine, wait for devices to report back, and confirm the intended state.
Operating context
The same property can behave differently.
Apply a mode to a home, building, floor, or room. Spaces inherit the mode above them unless they have their own, so a server room can remain always on while the rest of a building goes after-hours—or a guest suite can stay outside a broader home transition.
BuildingAfter hours
Office floorInherits after hours
Server roomAlways on
Holiday, vacation, and event exceptions can skip or substitute normal schedules without rewriting them.
Verification
Test the result, not just the command.
Define the state a macro should achieve, preview it with the same context a trigger or schedule will provide, and watch each step run.
- Live context testing
- Expected-state checks
- Run history and cause chains
Local by design
Local where it matters.
The automation engine, live state, and device drivers run together on the on-site GEM controller. An internet outage removes remote conveniences, not local schedules, triggers, scenes, or control.
Bring the systems into one operating rhythm.
Show us what the property needs to do. We’ll show you how GEM can coordinate it.