Synchronize
Sign in, select the eligible location, synchronize its V8 transmitter, and keep the runtime open on the local network.
Bridge cloud paging requests to local V8 hardware
Connector runs at the site, synchronizes authorized V8 transmitters, discovers the local paging device, and forwards paging requests from LRS Waitlist or from a partner integration to the hardware.
1. Overview
Where Connector fits
Dashboard owns Service Plans, API keys, locations, areas, and transmitter records. Waitlist creates paging requests during daily operation. Connector is the local bridge that receives an authorized request and writes it to a supported V8 transmitter on the location network.
2. Eligibility
Confirm access before installation
| Requirement | What to confirm |
|---|---|
| Authorized user | Sign in with a verified Dashboard account that can manage the target organization or location, or with a Partner Hub account. Staff-only accounts are not eligible for Connector administration. |
| Active location | The location must be active and have a current billed Service Plan with API Access enabled. |
| API key binding | The location must be associated with an active API key. The Connector receives scoped configuration, never the API key secret. |
| V8 transmitter | The transmitter must use the canonical V8 identity and be reachable on the same local network as the Connector runtime. |
| Partner Hub accounts | A partner account needs an integration app and a license that is active and inside its validity period, with transmitter capacity still available on that license. The Service Plan and API key requirements above apply to Dashboard accounts, not to partner accounts. |
A stored location-to-key association does not grant access by itself. Connector eligibility follows the active charged plan; a future scheduled plan does not activate API Access early.
3. Runtime
Use a supported packaged origin
Choose the packaged runtime approved for the location workstation. Production API access uses an exact origin allowlist, so changing the local host or port can prevent sign-in and synchronization.
| Runtime | Production origin |
|---|---|
| Bun / Bun Window | Uses http://127.0.0.1:4000. Keep the default host and port in production. |
| Electrobun | Uses http://127.0.0.1:4100. Keep the default host and port in production. |
| Neutralino | Uses http://127.0.0.1:4300. Keep the default host and port in production. |
| Tauri | Uses the packaged Tauri origin and native commands instead of a local HTTP server. |
Do not replace
127.0.0.1 with localhost or override the production port unless the API allowlist is updated and deployed at the same time.4. Sign in and sync
Prepare the local paging connection
- Connect the workstation to the same local network as the V8 transmitter.
- Start the approved Connector runtime and sign in with a verified manager account.
- Select the context Connector offers for your account. A Dashboard account selects the eligible account, organization, and location; a Partner Hub account selects an Integration App instead.
- Run local discovery and confirm the expected transmitter appears.
- Synchronize the transmitter and review the area assignments returned by the cloud configuration.
- Send a controlled test page and verify both Connector status and the physical pager before live use.
- Keep Connector running while the location expects V8 paging requests.
On a Partner Hub account the discovery window also asks for a Destination license. Choose the license the transmitters belong to before saving them — the save action stays disabled until a license is selected, and the saved transmitters count against that license's transmitter allowance.
Connector continuously watches every synchronized V8 transmitter and shows it as Online or Offline in the saved transmitters list. A transmitter that stays unreachable for about five minutes is automatically taken out of service to free its capacity. Once it is back on the local network, use the Active toggle in Connector's saved transmitters list to bring it back into service.
5. V8 identity
Use the canonical transmitter serial
The canonical V8 serial format is T7470-#####, where the final five characters are digits. Connector also accepts the bare five digits and expands them to this format. Legacy T747X values are not converted and will be rejected by V8 synchronization and paging.
| Input | Result |
|---|---|
| T7470-12345 | Canonical V8 identity; accepted. |
| 12345 | Expanded by Connector to T7470-12345. |
| T747X-12345 | Legacy alias; rejected. |
| T7471-12345 | Not a V8 identity; use the workflow for its actual hardware model. |
6. Paging status
Interpret local delivery status correctly
| Status | Meaning |
|---|---|
| Received | The cloud request reached Connector and is waiting for local processing. |
| Accepted | The local transmitter answered the paging request. This confirms the request reached the transmitter and was answered; it does not prove that the page was transmitted or that the pager received it. |
| Expired | The request passed its allowed delivery window before local transmission completed. |
| Unavailable | No eligible synchronized transmitter was available for the request. |
Always verify a new installation with real hardware. A successful local protocol response is not confirmation that a guest's physical pager vibrated, lit, or sounded.
7. Troubleshooting
Resolve common Connector problems
Location is missing after sign-in
Confirm the location is active, its current charged plan includes API Access, and an active API key remains bound to it.
V8 serial is rejected
Use T7470 followed by a hyphen and five digits. T747X is no longer an alias. Entering only five digits in Connector expands to the canonical T7470 form.
Packaged runtime cannot reach the API
Use the runtime's default 127.0.0.1 port. Production accepts only the packaged origins listed in this guide; custom ports require a coordinated API change.
Request is accepted but the pager does not react
Accepted only means the transmitter answered Connector. Start with the transmitter itself — its configuration and its own status display — and then recheck the pager number, pager type, signal coverage, and the physical pager.
Local history disappears after restart
Connector rebuilds its synchronized state after sign-in. Confirm the location and transmitter resynchronize before sending another test page.
A synced transmitter turns Inactive on its own
Connector automatically takes a V8 transmitter out of service after it stays unreachable on the local network for about five minutes. Reconnect the hardware, confirm it appears in a fresh scan, then use the Active toggle in the saved transmitters list to bring it back into service.