Streaming Hub 0.1

Stream Deck

Connect compatible controller applications to Streaming Hub through the local bridge. This article uses an Ajazz Stream Dock as the working example.

Alpha
Verified withStreaming Hub: 0.1.3.0Plugins: Stream Deck 1.1.2

Capabilities

  • Receive button, encoder and touch events from compatible controllers.
  • Create queued UI choices and handle the selected response.
  • Run independent choice queues in multiple UI Zones.
  • Write text and status to configured information panels.
Signals7 items
NameDescription
StreamDeck Button DownTrigger when a Stream Deck Signal button is pressed.
StreamDeck Button UpTrigger when a Stream Deck Signal button is released.
StreamDeck Encoder DownTrigger when a Stream Deck encoder is pressed.
StreamDeck Encoder RotateTrigger when a Stream Deck encoder is rotated.
StreamDeck Encoder UpTrigger when a pressed Stream Deck encoder is released.
StreamDeck Touch TapTrigger when a Stream Deck touch control is tapped.
StreamDeck UI Choice SelectedTrigger when a UI Choice button selects an option from the active request.
Steps3 items
NameDescription
StreamDeck: Set Info PanelWrite text or status to one or more information panels.
Choice CreateQueue a set of choices for Dynamic buttons in a UI Zone.
Choice DismissDismiss queued or visible UI choices in a UI Zone.

Integration signals can start automations. Integration actions are added as steps.

Requirements

  • A supported Stream Deck-compatible controller application or device. The example below uses Ajazz Stream Dock.
  • The matching Streaming Hub controller plugin installed in the Ajazz application.
  • The same local bridge URL and token configured on both sides.

Connect

  1. Install the Streaming Hub plugin in the Ajazz Stream Dock application.
  2. In Streaming Hub, open Services → StreamDeck / Local.
  3. Enable the bridge. Keep the default port and path unless they conflict with another local service, and replace the placeholder token with a private value.
  4. Select Apply, then use Copy URL + Token or copy both values separately.
The screenshot shows an example token. Replace it with a private value, then use the same URL and token in the Ajazz Connection action.
  1. In Ajazz Stream Dock, add Streaming HUB → Connection to a key.
  2. Paste the WebSocket URL and token, save the action, then select Test.
  3. Wait for the connection key to display HUB_OK. If the action reports a socket or token error, correct it before creating signal buttons.
The HUB_OK key confirms the Ajazz application has reached the bridge. The token shown here is only an example; replace it with a private value.

Verify the connection

Run Run Self-test in Streaming Hub. The report should confirm the bridge connection and test-message exchange. The Ajazz Connection key should display HUB_OK.

Create an Ajazz signal button

Add Streaming HUB → Signal to an Ajazz key and give it a stable Button ID. In Streaming Hub, create an automation with StreamDeck Button Up or StreamDeck Button Down and enter exactly the same ID.

The Ajazz Signal action sends its Button ID to Streaming Hub.
The Streaming Hub signal must use the same Button ID, including capitalization.

Interactive choices

Choice Create assigns options to Dynamic buttons in a UI Zone. It can pause the current automation or continue immediately and report the answer through StreamDeck UI Choice Selected.

Define the zone in Services → StreamDeck / Project. Its ID must match the UI Zone on each Ajazz Dynamic key. Set Start index and Button count to cover the keys reserved for choices.

This project defines a four-button UI Zone named mod. An old diagnostics error line was removed from the documentation image.
In Ajazz, assign Dynamic actions to the zone and give each reserved key a unique index within its configured range.

Each zone has an independent priority queue. Choice Dismiss can close the current request, clear a zone or remove requests by Prompt ID.

Build an interactive UI Choice on Stream Deck explains the complete setup, execution modes, timeout, priority and dismiss behavior.

Limitations

The bridge is local but still requires matching URL, token and plugin versions. Device capabilities vary between controller models. One UI Choice is visible per UI Zone; additional requests wait in that zone's queue.

Troubleshooting

Check the service status and filter the Log panel by the integration source. Reopen the integration settings to check connection details, enabled options and required external-service permissions.