Series Api — Novastar H

: Query device status such as temperature, voltage, and connection health .

, designed for third-party control of video wall splicers (H2, H5, H9, and H15). 1. Core API Overview

Generate or retrieve your (Requestor ID) and secretKey . These are essential for authenticating your JSON requests. Core API Capabilities novastar h series api

Note: index corresponds to the numbered preset slot (0-7).

| Return Code | Meaning | Action | |-------------|---------|--------| | 0 | Success | Continue | | 1 | Invalid command | Check spelling | | 2 | Parameter out of range | Verify bounds (e.g., input 1–4) | | 3 | Command not allowed in current mode | Disable genlock or PGM preview | : Query device status such as temperature, voltage,

The demand for massive, high-resolution video walls requires powerful hardware and intelligent, automated control. The NovaStar H Series enterprise-grade video wall splicers stand at the forefront of this technology. However, the true power of these processors lies in their integration capabilities. By leveraging the , systems integrators, AV developers, and IT administrators can bypass manual web control interfaces to build bespoke, automated, and highly responsive AV ecosystems .

: Read currently played presets, edit preset groups, or overwrite existing ones . Core API Overview Generate or retrieve your (Requestor

Session-based authentication token acquired via a initial POST request containing admin credentials. 3. Core Capabilities Handled via the API

Note: While Novastar does not publicly document the full binary protocol for the H Series as openly as the older S Series, reverse engineering and SDK agreements are common in the integration industry.

The NovaStar H series API is powerful but can be dangerous if exposed to the wrong network. A malformed command can black out a $500,000 LED screen.

The H Series API categorizes commands into three primary functional groups: