Node-RED Nodes — Reference

Detailed reference for all Wonder Controlz Node-RED nodes. For an overview, see the main Node-RED Nodes page.

The nodes are distributed in two packages:

• node-red-nevo-er — CAN bus nodes (I/O modules)
• node-red-er-audio — audio nodes (bundled with er-audio)

Shared configuration node for the CAN bus connection.

All CAN device nodes reference this config node. Multiple nodes can share the same interface.

Type: Input (no inputs, 1 output)
Category: function
Palette label: digital-in

Listens for state changes on a digital input channel of an I/O module.

Configuration:

Output message:

Status indicator: green dot = ON, grey ring = OFF, red ring = error.

Type: Output (1 input, no outputs)
Category: function
Palette label: digital-out

Sets a digital output on an I/O module.

Configuration:

Input message:

Status indicator: reflects actual state received as feedback from the device.

Type: Output (1 input, no outputs)
Category: function
Palette label: pwm-out

Sets a PWM output value on an I/O module.

Configuration:

Input message:

Status indicator: shows percentage (e.g., “50%”).

Type: Output (1 input, no outputs)
Category: function
Palette label: servo-out

Moves a servo to a target position with a configurable motion profile.

Configuration:

Input message — simple:

Input message — advanced (object):

msg.payload = {
    targetValue: 750,   // position 0–1000
    rampTime: 15,       // 0–255 (×100 ms = 1.5 seconds)
    rampType: 3         // 0=Linear, 1–5=Smoothstep
};

All fields are optional — missing values fall back to the node's configured defaults.

Type: Input (no inputs, 1 output)
Category: function
Palette label: usb

Receives keyboard and mouse events from a USB HID device connected to an I/O module.

Configuration:

Output — keyboard event:

{
    topic: "keyboard",
    payload: {
        keyCode: 65,    // ASCII key code
        state: 1        // 1 = pressed, 0 = released
    }
}

Output — mouse event:

{
    topic: "mouse",
    payload: {
        buttons: 1,     // button bitmask
        x: 10,          // X delta (-128 to +127)
        y: -5           // Y delta (-128 to +127)
    }
}

Bundled with the er-audio project. Pre-installed on devices delivered with er-audio. The ER-Audio category appears in the Node-RED palette.

Shared connection to an er-audio instance.

If er-audio runs on the same Main PC, use localhost. For a dedicated audio machine, use its LAN IP.

Type: Input/Output (1 input, 1 output)
Category: ER-Audio
Palette label: player
Icon: music note

One node = one audio track. Each player node manages a single audio file on a specific output device.

Configuration:

Commands — send as msg.payload or msg.command:

Runtime overrides — send alongside any command:

Output message:

Status indicators:

Built-in testing in the editor:

The node's edit panel includes Start, Pause, and Stop buttons for immediate playback testing without deploying the flow. Volume and pan can be adjusted live during testing. The test player is automatically cleaned up when the panel is closed or saved.

Lifecycle:

• On deploy/restart (with Auto Init enabled): player is automatically created in er-audio with the configured file, device, volume, and pan
• On node deletion: player is removed from er-audio
• On redeploy: player is reinitialized with current settings

[Inject: "start"] → [er-audio-player]

[Game Reset trigger] → [Function: msg.payload="reset"] → [player: ambience]
                     → [Function: msg.payload="reset"] → [player: music]
                     → [Function: msg.payload="reset"] → [player: effects]

[Dashboard Slider 0-100] → [Function: msg.volume = msg.payload/100; msg.payload="start"] → [player]

[Trigger Zone A] → [player: Device=hw:0,0]
[Trigger Zone B] → [player: Device=hw:1,0]
[Trigger Zone C] → [player: Device=hw:2,0]