Skip to content
OAOpenAppPhysical Security as a Service
Login

6. Create a virtual opener and light

A device is a physical or virtual unit that belongs to a single integration. An entity is the controllable or readable capability on that device. For example, a single device can expose a door opener entity and a light entity.

Create two demo devices under the Virtual Demo Devices integration:

  1. Create a device named Demo opener.
  2. On that device, create a door entity named Demo door.
  3. Create a device named Demo light.
  4. On that device, create a light entity named Demo light.

Open the integration page. The virtual demo panel shows the door as open or closed and the light as on or off. Use Open, Close, Turn on, and Turn off to see entity actions update the virtual device state. Here each entity is driven on its own so you can learn the actions; that is not how the access screens behave later.

At this point you have a working integration → device → entity stack: an API key, Virtual Demo Devices, and a demo door plus lobby-style light you can drive from the dashboard as an org member. That is enough to prove OpenApp can reach your hardware (or its stand-in), but it is not yet an access-control product. The next step is a longer checklist. In plain language you are still missing a visitor-facing entry, a building directory or call surface, guest links, and rules that govern who may open the door and map that to Demo door. Demo light stands in for entry lighting the product can switch with a door open; permissions stay centered on the door. That step adds Virtual Access to build that.


← Demo integration · Create demo access control →