Modern Security Meets Classic Control:

admin on October 28, 2025

Modern Security Meets Classic Control: Our Ajax & Inner Range Integrations for Crestron Home

Introduction: Security, the Crestron Home Way

Crestron Home provides a dedicated Security System Type—a standardized way for homeowners to view and control alarms inside a familiar interface. Out of the box, users get:

  • A Home Page Tile (with a fixed icon set),
  • An Alarm Summary Page showing all areas (but no global controls),
  • A system-wide Keypad Emulation Page that supports function buttons.

This consistency is a strength for user experience. It also defines a clear set of boundaries for what developers and integrators can—and can’t—expose in the UI.

Where the Framework Helps (and Where It Doesn’t)

Working inside the Security System Type keeps things predictable, but there are constraints that matter in real homes:

  • No “Arm All” control on the Alarm Summary Page, even when the alarm platform supports it.
  • Function buttons can’t be password-protected at the Crestron UI level, which limits how tightly you can secure sensitive actions where they are outwith the standard alarm states that Crestron support.
  • Fixed visuals and flows mean we can’t tailor the UX to modern, software-centric security systems.
  • Event feedback and dynamic controls are narrower than what next-gen platforms can provide.

For homeowners, the experience is simple and consistent. For developers and integrators, it’s a design box we must work within.

Disruptors in a Traditional Space

Our two security drivers—Inner Range and Ajax—reflect the shift from old-school, panel-led alarms to modern, app-first platforms. These systems lean into wireless devices, cloud connectivity, mobile experiences, and rich automation. They’re powerful—and that power doesn’t always map one-to-one into Crestron Home’s fixed security interface. In addition one of the benifits of these systems is that they can provide IO for automation beyond security.

Our Philosophy: Build Natively Where Possible, Extend Where Valuable

Our goal is straightforward: deliver the most capable, stable, and intuitive experience within Crestron Home’s framework, and add value around it where the SDK allows. That means careful mapping of modes, zones, and events into the Security System Type—and selectively using Extension Drivers when they improve clarity or control without confusing the homeowner or the integrator.

Inner Range: Leading With Extension Tools

When we began our Inner Range work, Crestron Home’s Security System Type wasn’t yet sufficiently evolved or stable for what we wanted to deliver. Our approach was deliberate:

  • Primary strategy: build a set of extension tools to surface key functions and statuses outside the fixed Alarm UI.
  • Why: extension drivers gave us flexibility to present information and controls that the native security type couldn’t expose at the time.
  • Outcome: integrators could craft a more complete experience—while still keeping the core interactions intuitive inside the Crestron Home environment.

There’s a trade-off: Extension Drivers are not intrinsically tied to the alarm type. They can enhance the system but won’t replace the built-in flows or override core UI behavior. We designed our tools to complement—not confuse—the native experience.

Ajax: Built for the Security System Type

For Ajax, we’ve focused on building directly against the Crestron Home Security System Type, including robust zone handling. This gives homeowners a native feel: reliable arm/disarm flows and clear status inside the standard Crestron interface.

At the same time based on feedback from users, we see opportunities to improve situational awareness with lightweight status tiles delivered via extension drivers. These tiles can surface at-a-glance information (e.g., area states or noteworthy events) that the fixed UI doesn’t highlight well—without trying to “recreate” the alarm UI outside Crestron’s design.

In other words: native first for core security interactions; extensions where they increase clarity.

Practical Limitations You Should Expect

Crestron (Security System Type constraints)

  • No “Arm All” action in the user interface (except in Function buttons):
    Arming is per-area only.
    Our approach: We provide Arm All as a function button which is by nature not password protected and this can be hidden by the integrator.
  • Function buttons lack password prompts:
    Sensitive actions can’t be locked behind a PIN in the Crestron UI.
    Our approach: We leave this up to the integrator to hide the sensitive functions if there system should not expose them.
  • Fixed UI look/feel & iconography:
    Limited ability to customise visuals, layout, or flows.
    Our approach: Clear labelling, grouping by area/zone, and concise copy to keep complex systems intuitive.
  • Constrained event representation:
    Not every granular event maps neatly into the native screens.
    Our approach: We use function buttons and extension tiles/pages for at-a-glance summaries which partially duplicates the Alarm UI.

Ajax (within the Security System Type)

  • Per-area arming model in Crestron:
    Even if Ajax supports broader actions, Crestron requires per-area control.
    Our approach: Native per-area flows, plus optional overview tiles for clarity.
  • Advanced Ajax features not fully surfaced in Crestron:
    Some rich capabilities (e.g., deeper device insights or advanced automations) aren’t natively exposed via the fixed UI.
    Our approach: Prioritise reliable arm/disarm and zone status in the Security Type; add lightweight status tiles via extension drivers for key summaries.
  • Function-button safeguards limited by Crestron:
    Crestron lacks PIN prompts on functions, regardless of Ajax configuration.
    Our approach: Keep function-button mappings conservative; push sensitive tasks to the Ajax app/panels where appropriate.
  • Limitations on using Zone actuators for Automation and feedback
    • Zone Limitations
      By Default, devices such as MotionProtect, DoorProtect do not report alarm events to the CMS unless the system is in an ARMED state.
      If you want these devices to always report state changes, it needs to be set to “Always Active” and “Instant Alarm” which makes the device always armed. More info here
    • Turning off Alarm notifications in the Ajax App (Optional)
      This is so devices don’t activate the alarm notification (If you choose to set any Devices to Always Active)
      You can turn off Alarm notifications by going to Hub >> Settings >> Users >> Select the User >> Notification settings >> Turn off Alarms. More info on notifications here
    • Turning off Siren Alerts (Optional)
      This is so devices set to “Always Active” does not trigger any Sirens.
      NOTE If the device is a critical security device and the Siren needs to sound when in Alarm, do not turn this off.

The Integrator’s Role: Turning Capability into Experience

Great outcomes depend on great deployments. Integrators have a unique role to explain the capabilities and expectations of any integration.

  • Map areas and zones with consistent, human-friendly names,
  • Decide when to use extension tiles for clarity (and when not to),
  • Educate homeowners on what the Crestron interface can and cannot do versus the native Ajax or Inner Range apps,
  • Configure function buttons with low-risk actions and lean on platform-side security for sensitive tasks.

The result is a system that feels native, predictable, and respectful of security best practices.

Extending the Fixed UI—Carefully

Crestron’s Extension Drivers let us augment the experience with extra tiles, pages, or indicators. They’re great for:

  • Summarizing multi-area states,
  • Highlighting exception conditions,
  • Providing quick links to common, low-risk actions.

But because extensions aren’t bound to the Security System Type, we use them sparingly and intentionally—to inform, not overwhelm. The fixed Crestron flows remain the homeowner’s anchor.

Its possible in many cases to use our range of UI Tiles to extend the user interface with connections made in Crestrons Events and Actions system. However where this is limiting we will work with integrators to provide custom solutions.

Sustainable Progress: Innovation with ROI

We’re committed to evolving our drivers as Crestron’s SDK grows. That said, we also have to responsibly invest: prioritize features that meaningfully improve homeowner outcomes, deliver stability for integrators, and make commercial sense. This ensures we can keep shipping updates, provide support, and push the ecosystem forward.

What Homeowners Get Today

Whether you choose Ajax or Inner Range with Crestron Home, you get:

  • A reliable, native control experience for everyday arming/disarming,
  • Clear area/zone feedback aligned to the Security System Type,
  • Thoughtful extensions where they add clarity (e.g., status tiles),
  • Deployment practices that emphasize security, simplicity, and predictability.

What’s Next

As Crestron expands the Security SDK and manufactures expand their SDK architecture , we’re ready to:

  • Deepen zone and event visibility,
  • Explore safe patterns for aggregate actions if/when supported,
  • Improve status summarization and exception handling,
  • Iterate on extension tooling that enhances, not duplicates, the fixed UI.

Our aim is steady progress: a modern security experience that respects Crestron’s design, makes integrators’ jobs easier, and keeps homeowners confident in their system—day one and year five.

Look out for the next article when we will discuss how the above ties up with the new Lock Type for Crestron Home and the new functionality this brings.