Registry / iot / node-red-contrib-chirpstack-enqueue

node-red-contrib-chirpstack-enqueue

library0.2.0jsnpmunverified

Node-RED nodes (v0.2.0) for sending multicast and unicast downlinks to ChirpStack v4 via gRPC. Supports confirmed downlinks, automatic payload encoding (hex/base64/UTF-8/Buffer), and secure API token storage. Designed for LoRaWAN automation workflows within Node-RED. Requires Node.js >=16 and a ChirpStack v4 gRPC endpoint. Released as part of the node-red-contrib-chirpstack-enqueue package.

iot

npm install node-red-contrib-chirpstack-enqueue

package ↗

INSTALL

IMPORT

SIG · NODE-RED-CONTRIB-C

node-red-contrib-chirpstack-enqueue

iotjavascriptv0.2.0

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

chirpstack-enqueue

✓ Use the node in Node-RED palette after installing the package; no JavaScript import needed.

✗ Attempting to require('node-red-contrib-chirpstack-enqueue') in a script

These are Node-RED nodes, not a programmatic library. Install via Manage Palette or npm install in your Node-RED user directory.

chirpstack-multicast

✓ Use the node in Node-RED palette after installing the package; no JavaScript import needed.

✗ Attempting to require('node-red-contrib-chirpstack-enqueue/multicast')

Nodes are loaded automatically by Node-RED when the package is installed.

chirpstack-server-multicast

✓ Use the node in Node-RED palette after installing the package; no JavaScript import needed.

✗ Trying to import the config node programmatically

Config nodes are managed in Node-RED flows, not via direct import.

Creates a ChirpStack server config node and an enqueue node, triggered by an inject node with devEui, fPort, and hex payload.

// This is a Node-RED flow, not a script. Import the following JSON into Node-RED: [ { "id": "server1", "type": "chirpstack-server-multicast", "name": "ChirpStack Server", "server": "chirpstack:8080", "apiToken": "${API_TOKEN}" }, { "id": "node1", "type": "chirpstack-enqueue", "z": "tab1", "name": "Enqueue Downlink", "server": "server1", "x": 400, "y": 300, "wires": [["helper1"]] }, { "id": "inject1", "type": "inject", "name": "Trigger", "props": [ {"p": "devEui", "v": "0102030405060708"}, {"p": "fPort", "v": 10}, {"p": "payload", "v": "48656C6C6F"} ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "x": 200, "y": 300, "wires": [["node1"]] }, { "id": "helper1", "type": "debug", "name": "Result", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "true", "targetType": "full", "x": 600, "y": 300, "wires": [] } ]

Debug

Known issues

gotchaAPI Token must be stored in Node-RED credentials. The token is not visible in flow exports.

fix

Use Node-RED's credential system; do not hardcode token in the flow JSON.

affects: >=0.1.0

gotchaThe gRPC server address must include the port (e.g., 'chirpstack:8080'). Default port is 8080.

fix

Always specify the port when configuring the chirpstack-server-multicast node.

affects: >=0.1.0

gotchaPayload encoding: If payload is not hex, base64, or UTF-8 string, it must be sent as a Buffer. The node does not auto-detect arbitrary object payloads.

fix

Convert your payload to a supported format (hex string, base64 string, UTF-8 string, or Buffer) before passing to msg.payload.

affects: >=0.1.0

deprecatedChirpStack v3 is not supported. This package only works with ChirpStack v4 gRPC API.

fix

Ensure your ChirpStack server is v4 or later.

affects: >=0.1.0

gotchaThe multicast node requires a multicast group ID. If you are not using multicast, use the enqueue node instead.

fix

For unicast downlinks, use the chirpstack-enqueue node with a devEui.

affects: >=0.1.0

Errors

Common errors & fixes

Error: 12 UNIMPLEMENTED: method not implemented

ChirpStack server version is not v4 or the gRPC service is not enabled.

fix

Verify ChirpStack version >=4 and that the gRPC interface is configured correctly.

Error: 14 UNAVAILABLE: Connection refused

The gRPC server address is incorrect or not reachable.

fix

Check the server address in the chirpstack-server-multicast config node. Ensure the port (usually 8080) is included.

TypeError: Cannot read properties of undefined (reading 'multicastGroupId')

msg.multicastGroupId or msg.payload.multicastGroupId is missing for multicast node.

fix

Set msg.multicastGroupId or msg.payload.multicastGroupId to a valid multicast group ID.

Error: 3 INVALID_ARGUMENT: devEui must be 8 bytes hex

The devEui provided is not a 16-character hex string.

fix

Format devEui as an 8-byte hex string, e.g., '0102030405060708'.

Error: 3 INVALID_ARGUMENT: fPort must be between 1 and 223

fPort is out of allowed range.

fix

Set fPort to an integer between 1 and 223.

Upgrade

Version history

0.2.0latest on npm

Audit

Dependencies

node-redrequiredRuntime environment required for Node-RED nodes

Agent activity

21 hits · last 30 days

node

Resources

packagenode-red-contrib-chirpstack-enqueue ↗