Devices
Every box the hub talks to. Capture the MAC while the unit is in your hands — it keys the DHCP reservation and it is how you find a device whose IP moved.
| ID | Name | Model | Host | Port | MAC | Serial | Location |
|---|
dbx object map
Object IDs are per unit and per loaded configuration — not portable, not
guessable. Discover them with Get Object List (0x011E) or a ZonePRO Designer trace.
Enter as hex (0x0105001E) or decimal.
Audio
Zones are listed alphabetically, not in dbx output order — staff think in rooms, and the output number is an implementation detail of the amplifier. Each maps to one ZonePRO output router.
Every probe on this tab runs from the hub, and its finding is reported up the cloud uplink and stored against the venue — so remote support reads results from the cloud instead of asking whoever is standing here to copy hex out of a browser.
Discover NEXT endpoints
Asks the NXT-CTL what is on the network. Endpoint hostnames are
<Model>-<MAC>, so this reads MAC addresses off the wire instead of off box labels.
dbx ZonePRO — import a Designer project
The .zpd is currently the only route to a ZonePRO’s
object map: the unit answers Get Object List with silence, probed on real hardware.
This is a heuristic, not a format parser. A .zpd is a .NET
BinaryFormatter graph with no specification, so what comes back is a shape that was recognised,
shown with the evidence for it. Read the counts before you apply anything.
dbx ZonePRO — get object map
Sends Get Object List (0x011E) to the unit, open-loop and
ack-requested. Read-only. The reply’s payload shape is undocumented, so the
hex capture is the finding — guessed ids below it are a hint, not an answer.
“No reply” is a real result: it means the object map comes from the ZonePRO
Designer project instead.
Raw TCP peek
Connects, sends nothing, and captures what the device volunteers
first. Answers protocol questions a driver cannot ask — e.g. whether a controller opens
with Telnet IAC bytes (ff ..) that a bare-socket client never answers.
Rooms
A room is a place: one audio zone, the screens in it, and what it shows when nobody has asked for anything. This is the layer staff actually think in — nobody standing in a bar thinks “dbx output 2”, they think “the front room is too loud”. The three lists below stay the source of truth for what each thing IS; a room just says where it is.
Audio zones
Each zone maps to a dbx router object. Volume is 0–100 everywhere in TavernSync; the driver maps it to the dbx fader range.
| ID | Name | Device | Router object | Mixer object | Default input | Default level |
|---|
Sources
Things that can be tuned or sent — DIRECTV receivers, NEXT encoders.
| ID | Name | Device |
|---|
Displays
Screens. Output is the switcher output (out1) for a WyreStorm
switcher, or the NEXT decoder alias for a NEXT system.
| ID | Name | Device | Output / alias |
|---|
Inputs
Every source in this venue's config. Select one to tune it, drive its on-screen menus, and — where an encoder is linked — see what it is putting on the wire. These are real commands to real receivers.
Diagnostics
What this hub is, and what it believes about each device. Reachability here is a belief, not a live reading. It records how the last real command went, because polling these device families costs more than it buys — the WyreStorm document warns an unexpected parameter can lock a unit. Press Check on a device to ask it something read-only, right now.
Test against real hardware
Fires a real command at the real device. No device in v1 has readback worth trusting — so use your eyes and ears, not this screen, to decide whether it worked.
Raw configuration
Everything, including favorites and schedules. Validated on save with the same rules the hub applies to a cloud push — a bundle rejected here would be rejected there.