Skip to content

HTTP Server

HTTP Server

The HTTP Server device allows OnlyView to receive HTTP requests from external systems, enabling integration with web applications, control panels, and other HTTP clients that need to trigger actions or send data to OnlyView.

Setup

To configure an HTTP Server device:

  1. Access the Devices section
  2. Click Add Device and select HTTP server
  3. Configure the device settings:
  4. Device name: Enter a descriptive name for this HTTP server
  5. Port: The TCP port to listen on (up to 66000)

The HTTP server will listen on all network interfaces (0.0.0.0) on the specified port, making it accessible from any device on the network.

ActionGraph Node

The HTTP Server device provides an ActionGraph node for handling incoming HTTP requests in automation workflows:

HTTP Server Receiver Node

Properties: - Device: Reference to the HTTP Server device configuration - Endpoint (regex): Regular expression pattern to match incoming request paths - Example: /.* matches all paths - Example: /test matches exactly "/test" - Example: /test/.* matches "/test" and any sub-paths

Output Slots: - Endpoint: The full path of the received HTTP request (string) - Verb: HTTP method of the request (GET, POST, PUT, PATCH, DELETE) (string) - Body: Request body content (string)

Output Events: - Message received: Fired when an HTTP request matching the endpoint pattern is received

The node monitors incoming HTTP requests to the configured server device. When a request is received that matches the endpoint regex pattern, the node outputs the request details and triggers the "Message received" event.

Custom UI

The HTTP Server node displays helpful information in the ActionGraph editor: - Shows example endpoint patterns - Displays regex syntax help - Shows any regex validation errors

Use Cases

The HTTP Server device is commonly used for:

  • External Control: Allow web applications or control panels to trigger OnlyView actions
  • API Integration: Receive data from external systems and process it in ActionGraphs
  • Remote Triggering: Enable HTTP-based remote control of show elements
  • Status Updates: Receive status information from external devices or services
  • Webhook Handling: Process webhooks from third-party services

Technical Notes

  • The server uses a single thread for handling requests to maintain performance
  • Each ActionGraph node can filter requests using regex patterns on the endpoint path
  • All HTTP methods (GET, POST, PUT, PATCH, DELETE) are supported
  • The server automatically handles the low-level HTTP protocol details
  • Request processing is handled synchronously to ensure ActionGraph responses are sent properly