1. Business Value & Problem Statement

Currently, the Omada Hotspot Manager requires staff intervention to distribute Wi-Fi vouchers (printing, cutting, and handing them out to guests). This creates an administrative burden for hotel receptions, cafes, and coworking spaces.

To automate this process and ensure security (only guests physically present in the venue can see the password), we need a "Voucher Kiosk Mode". This feature will allow a dedicated display (e.g., a tablet or a monitor with a mini-PC running a full-screen browser) to automatically fetch, present, and cycle through single-use vouchers without human interaction.

2. Feature Description & User Story

As a network administrator, I want the Omada Controller to host a simple, built-in web page that displays only one active voucher at a time.

When a guest connects to the Wi-Fi using the displayed voucher, the controller should immediately detect the status change and cycle the web page to show the next fresh voucher from the pool.

User Scenario (Step-by-Step):

1. A tablet is mounted on the wall near the reception desk, displaying a full-screen browser pointed to a local Controller URL (e.g., https://<Controller-IP>:<Port>/html/vouchers).

2. The screen shows:

   • Short connection instructions.

   • The current Voucher Code (plain text).

   • A QR Code containing the direct login payload (scanning it connects and authenticates the user instantly).

3. Guest A comes in, scans the QR code or types the voucher code, and successfully connects to the guest network.

4. The Omada Controller detects that the voucher is now bound to Guest A's MAC address.

5. Through an active websocket/push connection, the web page on the tablet automatically refreshes within seconds to show a brand-new voucher for Guest B.

3. Technical Requirements

A. Dedicated Endpoint / Kiosk URL

• The controller should expose a lightweight, public (or locally restricted) endpoint, for example: https://<Controller-IP>/kiosk/vouchers?site=<Site_ID>&pool=<Pool_ID>.

• Access to this URL should optionaly be protectable by a dedicated "Kiosk View" token/password so that unauthorized users cannot guess the URL and harvest vouchers remotely.

B. Automated Voucher Generation (Just-In-Time)

• Administrators should define a Voucher Specification Template (e.g., duration: 24h, rate limit: 10Mbps, max devices: 1).

• Instead of manually pre-generating thousands of codes, the Omada Controller should automatically maintain a dynamic buffer of e.g., 5 unassigned vouchers. Once the active one is used, it moves the next one up and generates a replacement in the background.

C. UI Elements on the Display Page

The page hosted by the controller should be clean, responsive, and customizable:

• Instruction text: Custom HTML/Text field managed in the Omada Controller.

• Voucher Code: Large, highly readable font.

• QR Code Generation: Dynamic QR code generation incorporating the current voucher payload for frictionless mobile onboarding.

• Real-time Updates: Implementation of WebSockets or Server-Sent Events (SSE) so the page reacts instantly when a voucher status changes from Unused to Activated.

4. Benefits

• Zero Staff Intervention: Complete automation of guest Wi-Fi onboarding.

• Eco-Friendly: Eliminates the need to print paper voucher slips.

• Geofenced Security: Only people physically standing in front of the screen inside the building can access the internet.

• Hardware Agnostic: Works out-of-the-box on any device capable of running a browser (iPad, Android Tablet, Smart TV, Raspberry Pi, Intel NUC).