Gaming pods (POD) in IZI
Ce contenu n’est pas encore disponible dans votre langue.
Gaming pods (POD) in IZI CRM
Section titled “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
Section titled “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
Section titled “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; may contain letters, digits and spaces, up to 20 characters
Optional: schedule, contact phone, description, and photos (logo, cover image, gallery). The description can be edited later in the device editor.
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
Section titled “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
Section titled “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:
- Open the door — pull it toward you
- 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
Section titled “Player-initiated session end”When a player ends their session, the system checks in order:
- 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.
- Presence sensor — the pod counts as free only if the controller is powered on, the sensor sees no motion and the door is closed. An open door means occupied (door open or motion in the last 30 seconds).
- Controller snapshot — if the controller is powered off or not sending data, the system cannot confirm the pod is empty and the session cannot be closed.
An operator can force-end a session, bypassing all these checks.
Session-end errors
Section titled “Session-end errors”POD_DOOR_NOT_CLOSED
Section titled “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:
- Ask the player to open the door once and let it click shut — the latch will engage.
- The player can then retry ending the session in the app.
- If closing the door is not possible, force-end the session from the Control Center.
Pod occupied (POD_OCCUPIED_CANNOT_END)
Section titled “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)
Section titled “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 is powered off or has not sent current data. Check the controller’s power supply. If the pod is definitely empty, force-end the session.
Cancelling a pod booking as an operator
Section titled “Cancelling a pod booking as an operator”A pod booking that has not started yet is cancelled from the session card like any other. If the controller is silent, the system cannot check that the pod is empty and will not accept the cancellation. The cancel dialog then shows a Cancel without the pod check button. It requires the permission to force-end on devices. The money for the tariff bought with the booking is refunded on cancellation.
Pod controls in the Control Center
Section titled “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
Section titled “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
Section titled “Pod sensors”The pod card displays live sensor readings:
| Sensor | Values |
|---|---|
| Door | open / closed |
| Occupancy | occupied / free |
| Smoke | detected / — |
State controls
Section titled “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, when idle, runs in a 30 minutes on / 30 minutes off cycle (see below) — operators can override it manually.
Pod lighting
Section titled “Pod lighting”Pod lighting is controlled through Yandex smart lamps. In the pod card, in the Pod lighting block, add a smart home token and choose lamps from your Yandex account: the Top lamp and the Selfie light. One lamp can be bound to one place only.
What happens to the light:
- Idle. While the pod is free, the lamps show the “marketing light”. It is set for each lamp separately: Off, White (temperature and brightness), Color (RGB) or Scene, depending on what the lamp supports.
- Session start. A bright white technical light comes on for a short time (45 seconds), which makes it easy to inspect and photograph the pod. Then the “Work” light turns on.
- Session end. The light goes straight back to the “marketing light”. If a player turned the light on during the inspection and the session never started, the light also returns to normal when the inspection time runs out.
- During a session. The player picks a light mode in the app: Work, Zoom, Lounge or a custom one (brightness, temperature and color of the top and side lights), and can turn the light on and off.
A lamp used for pod lighting is not offered when binding power sockets and relays.
Idle ventilation
Section titled “Idle ventilation”While the pod is free, ventilation runs in a cycle: 30 minutes on, 30 minutes off. During an active session it is always on. An operator can override it manually in the “Pod states” block.
Player intro screen
Section titled “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
Section titled “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
Section titled “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
Section titled “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
Questions fréquentes
What is a pod (POD) in IZI?
A POD is a distinct device type in IZI. Unlike a regular PC, a pod is a standalone point on the club's mobile map — it has an address, coordinates, photos, and its own schedule. It is equipped with a controller that manages the door lock, lighting, ventilation, and a presence sensor.
Why can't a player end their pod session?
The most common reason is an unclosed door. The system prevents accidental session endings if someone is still inside. Ask the player to open the door and let it click shut — the latch will engage automatically. If that does not work, use force-end from the Control Center.
What does the error 'Lock released but door was never opened' mean?
This is the POD_DOOR_NOT_CLOSED error. The latch was released at session start, but the door was never opened or closed afterward — so the latch is still in the unlatched position. The player needs to open the door once and let it click shut to seat the latch.
How do I open a pod door from the CRM if it is stuck?
In the Control Center, open the pod card, go to the POD states section, and click Open Door. The system shows a confirmation prompt — confirm it. The equipment permission is required.
IZI LLC (ООО «ИЗИ»), TIN 7842227686, OGRN 1257800012249, office 1, premises 3-N, lit. A, 15-17 Perekupnoy lane, Saint Petersburg, 191024, Russia, admin@izi.is · Cookie settings