Novastar H Series Api [NEW]

To monitor an H Series device via SNMP, follow these steps:

: Modify a layer's X/Y coordinates, width, and height in real time.

This article provides a comprehensive overview of the NovaStar H Series API ecosystem. It will explain the core communication protocols, explore the commands used for preset recall, delve into the available tools and resources, and guide you through best practices for seamless integration.

Once enabled, your client software connects to: ws://[Device_IP]:8088/novastar/api novastar h series api

The H Series processors combine video scaling, multi-window processing, and sending card functionality. While NovaStar’s proprietary software (SmartLCT, V-Can) provides GUI control, system integrators require programmatic access. The H Series exposes a documented ASCII-based protocol over TCP port 5000 and an HTTP API on port 80.

Historically, NovaStar control protocols use a structured packet format consisting of a header, command length, command ID, data payload, and a checksum to ensure data integrity.

The repository also includes a ( novastar.lua ) that enables deep packet inspection of the NovaStar protocol on TCP ports 5200, 5201, and 5203, which is invaluable for debugging and reverse engineering. To monitor an H Series device via SNMP,

"jsonrpc": "2.0", "method": "layers/layer_a/source", "params": "token": "session_token_abc123", "source": "HDMI_1" , "id": 2

The API provides deep control over the individual windows and sources (layers) being displayed on the LED screen.

PUT http://192.168.1.100:8001/api/v1/device/screen/brightness Content-Type: application/json "params": "token": "session_token_abc123"

Here are the most valuable endpoints for developers working with the H series API. Use these to control your LED wall programmatically.

: State tracking updates immediately across multiple control terminals without polling lag. The Security & Access Routine

| Error Code | Description | |------------|-------------| | 0 | Success | | 1 | Invalid parameter | | 2 | Failed to send | | 3 | Internal error | | 4 | Data parsing failed | | 5 | Device busy | | 6 | Function not supported |