Novastar H Series Api May 2026
NovaStar H Series video wall splicers (models H2, H5, H9, H15) support two primary methods for third-party control: TCP/UDP-based JSON protocol HTTP-based OpenAPI
. Because specific protocol details are often restricted by NDA, it is highly recommended to contact NovaStar Support directly to request the latest full documentation. 1. Enabling API Access
Before you can send commands, you must enable and configure the API connector through the device's web-based management interface.
: Access the web console by entering the device's IP address into a web browser. Default credentials are typically Enable OpenAPI : Navigate to Settings > OpenAPI Management Create Project
to create a new third-party control project. The system will generate a (Requestor ID) and a 2. Communication Methods
The H Series supports multiple communication layers depending on your integration needs: HTTP OpenAPI : Uses standard requests with
formatting. This is ideal for web-based controllers or high-level software integration. UDP Protocol
by default. Commands are formatted as JSON strings enclosed in square brackets
: Standard TCP communication is used for more persistent connections with the control software. RS232/Serial : Physical control is possible via the port on the H_Control card. 3. Command Structure (JSON Example)
Most commands use a structured JSON packet. A typical execution command looks like this: "CommandName" "deviceId" : value }] Use code with caution. Copied to clipboard Successful Execution : The device returns "ack": "Ok" "ack": "Error" if the format is incorrect or unsupported. 4. Common API Capabilities novastar h series api
The API allows for real-time control of the following functions: Novastar H series open API control options?
The NovaStar H Series API is a specialized toolset designed for third-party developers to programmatically control NovaStar's flagship all-in-one video splicing processors. By leveraging the NovaStar H Series OpenAPI, integrators can automate complex video wall tasks such as preset switching, layer management, and device status monitoring. Core Integration Protocols
The H Series supports multiple communication methods to fit different system architectures:
UDP Protocol: Most control systems (like Crestron or Bitfocus Companion) use UDP port 6000 for high-speed command delivery. Commands are typically sent as JSON strings wrapped in square brackets (e.g., ["cmd": "..."]).
HTTP/JSON API: Modern web-based integrations often use the Open API connector, which provides a structured HTTP interface for cross-platform control via Windows, Mac, or mobile devices.
RS232 Serial: For legacy systems, the H Series retains support for serial communication, allowing direct wired control from specialized AV hardware. Key API Capabilities
The API allows for deep manipulation of the hardware's internal functions: H Series - Global leading LED display control solution
NovaStar H Series video wall splicers utilize a JSON-based control protocol for third-party integration, allowing developers to manage layers, presets, and device settings over a network. API Connection Methods TCP/IP (Network) : Commands are sent as UDP packets to of the device. RS232 (Serial)
: Standard serial communication using a DB9 or RJ45 adapter, with configurable baud rates through the device web page. Data Format & Syntax NovaStar H Series video wall splicers (models H2,
The API uses a specific JSON structure where each command starts with and ends with
. Multiple sub-commands can be nested within a single request using Command Structure Example ["cmd":"W0605","deviceId":0,"screenId":0,"presetId":0] Authentication : Third-party developers must often configure Open API Management in the device's web interface to generate a Project ID Secret Key for authorized requests. Key API Capabilities Layer Operations
: Open, close, move, scale, bring to front, send to back, and switch input sources. Preset Management : Recall saved configurations (presets) by or save the current state as a new preset. Device Status
: Read detailed information, check output lists, and monitor fan speed or voltage. Display Adjustments
: Set brightness, gamma, image quality, and output resolutions. Developer Resources Connection - novastar-h-series - Bitfocus
The NovaStar H Series supports comprehensive third-party integration, offering an OpenAPI for HTTP-based control and a JSON-based protocol via UDP/RS232 for automation tasks. These interfaces enable control over video wall presets, layer management, and system monitoring. For full technical details, refer to the NovaStar H Series OpenAPI Instructions. H Series Video Wall Splicers User Manual - NovaStar
The blue glow of the server room was the only light in the arena as Elias sat huddled over his laptop. In six hours, the World Championship opening ceremony would begin, but the massive 360-degree LED wrap—the centerpiece of the show—was dark.
He wasn’t just dealing with a simple screen; he was managing a massive cluster of NovaStar H-Series processors. The hardware was capable of handling tens of millions of pixels, but the creative team had just thrown a curveball: they wanted the visuals to react in real-time to the crowd’s noise levels.
"Manual switching won't work," Elias muttered. "I need the API." Unlocking Advanced Control: The Comprehensive Guide to the
He pulled up the H-Series API documentation. He needed to bridge the arena’s sound sensors with the H-Series' powerful layer management. Using a simple Python script, he targeted the H-Series IP address and crafted the JSON payloads. POST /api/v1/scene/switch
His first attempt failed. Connection refused. He checked his port—8000. Correct. He realized he hadn't authenticated the session. He quickly wrapped the request with the proper headers.
The fan noise of the processors hummed in sync with his heartbeat. He wrote a logic loop: if decibels exceeded 90, the API would trigger Scene 2—a high-energy "Voltage" preset. If they hit 110, Scene 3—the "Champion’s Gold" layer—would activate. He hit "Run."
High above, a single pixel line flickered. Then, like a digital sunrise, the entire H9 processor chassis responded. The API command slid the layers into place with zero latency. Elias clapped his hands near the sensor.
Immediately, the massive screen shifted from a deep blue to a pulsing electric violet. "It's alive," he whispered.
When the gates opened and 50,000 fans roared, Elias didn't touch a single button. The H-Series API caught the wave of sound, switching scenes and adjusting brightness automatically. The arena didn't just show a video; it breathed with the crowd, all thanks to a few lines of code and a very powerful processor.
If you'd like to turn this into a technical guide or a specific project, let me know: Which H-Series model are you using (H2, H5, H9, H15)?
6.3 Firmware Compatibility
Novastar occasionally updates command sets. Drivers should check the firmware version upon connection to ensure the command codes being sent are supported by the specific hardware revision.
Unlocking Advanced Control: The Comprehensive Guide to the NovaStar H Series API
In the world of professional LED display control, NovaStar has long been synonymous with reliability and cutting-edge technology. While their popular VX series and MX series dominate the all-in-one controller market, the H Series (specifically the H2, H5, and H9) represents a different beast entirely: a modular, high-performance sending card controller designed for large-scale, mission-critical LED installations.
However, for system integrators and software developers, the most exciting feature of the NovaStar H Series isn't just its 4K/8K processing power—it’s the NovaStar H Series API.
This article dives deep into what the H Series API is, why it matters, how to access it, and the specific commands that allow you to move beyond the physical control panel and into the realm of automated, third-party, and remote management.
1. Prerequisites
- Hardware: H Series sender (H2, H5, H9) with Ethernet port.
- Firmware: v1.3.0+ (API stability improved after this).
- Network: Static IP for the H Series (default:
192.168.1.10). Your controller must be on the same subnet. - Port: TCP
5000(command port), UDP6000(status broadcast, optional).