Gaming pods (POD) in IZI

Gaming pods (POD) in IZI CRM

A pod (POD) is a distinct device type in IZI. Unlike a regular PC, a pod is a standalone point on the club’s mobile map with its own address, coordinates, and schedule. The pod controller manages the door lock, lighting, ventilation, and privacy glass, while sensors report door state and player presence in real time.

For a pod to work, it must be added as a POD device type, assigned to a zone, and given coordinates and an address. Without these, booking is unavailable.

How a pod differs from a regular PC

	PC	Pod (POD)
Device type	PC / Console	POD
Mobile app map	No	Yes — address, photos, schedule
Presence sensor	No	Yes — door + motion
Lock control	No	Yes — open/close cycle
Auto-renewal	No	Required for booking
Booking without a card	Yes	No — a linked card is required

Adding a pod

Add a pod through Devices → Add device with device type POD. Required fields:

• Zone — required; a pod without a zone cannot accept bookings
• Coordinates and address — required; displayed on the map in the mobile app
• Name — shown in the Control Center and in the app

Optional: schedule, contact phone, description, and photos (logo, cover image, gallery).

After creating the pod, link a physical controller to it. A pod without a paired controller cannot accept bookings — the system returns an error indicating the pod has no paired device yet.

Door and lock cycle

This is the core mechanism of a pod — understanding it makes diagnosing most session-end problems straightforward.

How the lock works

The pod lock is mechanical: it latches automatically when the door is pushed firmly shut. When the system “opens” the lock, it only releases the latch — the door itself does not move. To seat the latch after the release:

1. Open the door — pull it toward you
2. Close the door — push it shut until it clicks

This is called a “door cycle.” The door sensor records both events independently of the lock motor.

Player-initiated session end

When a player ends their session, the system checks in order:

1. Door cycle for the current session — the door was opened and closed after this session started. If a cycle is present, the exit is confirmed and the session ends.
2. Presence sensor — motion with the door closed. If motion is detected: the pod is still occupied (door open or motion in the last 30 seconds).
3. Controller snapshot — if the controller is not responding, the system cannot confirm the pod is empty.

An operator can force-end a session, bypassing all these checks.

Session-end errors

POD_DOOR_NOT_CLOSED

Message: “Lock released but door was never opened — the pod is still unlatched. Ask the player to open the door and let it click shut, or force-end the session.”

This error appears when the latch was released during the current session but the door was never subsequently opened or closed. The latch is still in the released position, meaning the pod is physically unlocked.

What to do:

1. Ask the player to open the door once and let it click shut — the latch will engage.
2. The player can then retry ending the session in the app.
3. If closing the door is not possible, force-end the session from the Control Center.

Pod occupied (POD_OCCUPIED_CANNOT_END)

Message: “Pod still occupied: door is open or motion detected in the last 30 seconds.”

The sensor shows someone is inside — either the door is open or motion was detected. If this is a stuck door, confirm with the player and force-end if necessary.

Pod state unavailable (POD_PRESENCE_UNKNOWN)

Message: “Cannot confirm the pod is empty: controller is offline or has not sent data. Force-end if you are sure the pod is empty.”

The pod controller has not sent current data. Check the controller’s power supply. If the pod is definitely empty, force-end the session.

Pod controls in the Control Center

Where to find: Control Center → pod card → POD states section.

Controls are available with the equipment permission.

Open Door

The Open Door button releases the latch immediately. Clicking it shows a confirmation prompt:

Open the pod door? The latch will be released immediately. If nobody is inside, the pod stays open to anyone until the door is closed.

Use this when a player cannot open the door themselves, or when staff need to enter the pod after a session.

Pod sensors

The pod card displays live sensor readings:

Sensor	Values
Door	open / closed
Occupancy	occupied / free
Smoke	detected / —

State controls

The POD states section has toggles for:

• Privacy — controls the privacy glass tint
• Light power — interior lighting
• Ventilation — cooling and airflow

Ventilation turns on automatically during an active session and off when idle — operators can override it manually.

Player intro screen

The first time a player books a pod, the mobile app shows an intro screen. The system records that the player completed it (podIntroSeenAt). On subsequent bookings the intro is not shown again. For the full booking and return flow from the player’s perspective, see Pod flow in the mobile app.

Auto-renewal

Pod bookings require auto-renewal to be enabled with a linked card. Without auto-renewal, paid time runs out and the occupied pod cannot be released automatically — the system returns an error indicating that pod booking requires auto-renewal with a card.

Access permissions

Action	Permission
View club pod list	DEVICE_READ
Create a pod	POD_CREATE
Edit a pod	POD_EDIT
Delete a pod	POD_DELETE
Restore a pod	POD_RESTORE
Control states (door, light, ventilation)	Equipment permission

See also

• Devices overview — device types and card structure
• Add a device — registering a new device in the club
• Pod flow in the mobile app — the booking and return flow from the player’s perspective