Virtual Demo Devices
Virtual Demo Devices is a built-in provider for tutorials and product demos. It creates virtual opener and light entities whose state is stored in OpenApp, so you can learn the integration → device → entity → action model before connecting real hardware.
Demo resources are temporary. OpenApp assigns a cleanup time automatically to the virtual demo integration and resources created beneath it.
What It Provides
Section titled “What It Provides”- A virtual opener that supports
switchable.open,switchable.close, andswitchable.toggle. - A virtual light that uses the same switchable actions, where open means on and close means off.
- Timed auto-close / auto-off after
switchable.open: when policy and delays call for it (request payload, entity or device metadata, or deploy defaults), the backend schedulesswitchable.closeso demo doors and lights line up with portal and API flows the same way as production switchable gear. - A dashboard panel that shows door and light state.
- Compatibility with Virtual Access demo mode, so portals, intercoms, and invitations can be tested without real devices.
Recommended Use
Section titled “Recommended Use”Use this provider for the first pass through Getting started. After that, repeat the same flow with a real provider from the integrations catalog.
Do not use Virtual Demo Devices for production access control. Demo resources are designed to expire.
Demo Access Control
Section titled “Demo Access Control”When using Virtual Demo Devices with Virtual Access, create the Virtual Access integration in demo mode. Demo mode keeps the whole getting-started setup temporary and blocks unsafe mixes:
- Demo access integrations can link only temporary demo opener/light entities.
- Persistent access integrations cannot link temporary demo opener/light entities.
This prevents a real access-control setup from being deleted because it accidentally referenced a temporary demo device.
Policies
Policies restrict access on top of roles — they never grant it. The following apply to this integration:
Invitation curfew
Blocks invitation-based opens during a forbidden time window (for example nights).
Invitation curfew
Blocks invitation-based opens during a forbidden time window (for example nights).
Admins and residents are never curfewed; existing invitations are evaluated live, not modified.
- Type
- invitation_curfew
- Enforced at
- Access-time
- Tiers
- OrgIntegration
- Default
- Not configured — no hour restrictions on invitation-based access.
- Enforcement
- Enforce
User sharing control
Restricts whether non-admins may share access or create invitations out of band — block outright or require admin approval.
User sharing control
Restricts whether non-admins may share access or create invitations out of band — block outright or require admin approval.
- Type
- user_sharing
- Enforced at
- Authoring-time
- Tiers
- OrgIntegration
- Default
- Not configured — non-admins may share access freely.
- Enforcement
- EnforceRequire approval