TIGR live-feed emulator

disconnected not logged in no role no token no channels delivery untested 0 frames

Log in

The emulator holds no credential of its own, so log in as a real principal. What you choose here decides which channels the socket can hold — the two role gates are disjoint, so no one token holds both sides. The password or PIN is forwarded once to the API and never stored, not here and not on the server. When the token expires this form comes back.

Not retried on failure, deliberately: five failures arm lock:operator:* and every login here reaches the API from the emulator's single address, so that budget is shared by everyone using this panel.

Real incident — writes to Odoo

A tablet can accept or decline this one. It goes through the API's own POST /incidents + /reassign, so it is a genuine Odoo row with the ACK window armed — unlike everything below, whose ids start at 900001 and name no row at all.

Scenarios

Step gap

Denials

Run control

Single events

Region

Crew