node-red-contrib-power-genius 0.0.0-stage → 1.0.0

package/GeniusPGProtocol.js

@@ -0,0 +1,135 @@
+// Client for the PowerGenius XL line based API (TCP port 9008).
+//   banner:    V<a.b.c>[ AUTH]\r\n   (sent once on connect)
+//   request:   C<seq>|<command>\n   (seq 1-255; the documentation says CR, but a bare LF is what the device works with)
+//   reply:     R<seq>|<hex result>|<message>
+//   status:    S<n>|<message>   (asynchronous, for example "S|state=REBOOT")
+// The documentation is incomplete, so everything here is tolerant: unknown lines are passed on, never dropped.
+class GeniusPGProtocol {
+    constructor(socket) {
+        this.socket = socket;
+        this.seq = 0;
+        this.pending = new Map();
+        this.lineBuffer = "";
+        this.statusHandler = null;
+        this.bannerHandler = null;
+        this.lineHandler = null;
+    }
+
+    nextSeq() {
+        this.seq = (this.seq % 255) + 1;
+        return this.seq;
+    }
+
+    handleData(chunk) {
+        this.lineBuffer += chunk.toString("utf8");
+        const lines = this.lineBuffer.split(/\r\n|\r|\n/);
+        this.lineBuffer = lines.pop();
+        for (const line of lines) {
+            this._handleLine(line);
+        }
+    }
+
+    _handleLine(line) {
+        if (!line) return;
+        if (this.lineHandler) this.lineHandler(line);
+
+        if (line.startsWith("V")) {
+            if (this.bannerHandler) this.bannerHandler(line);
+            return;
+        }
+
+        if (line.startsWith("S")) {
+            const pipeIdx = line.indexOf("|");
+            const msg = pipeIdx !== -1 ? line.substring(pipeIdx + 1) : "";
+            if (this.statusHandler) this.statusHandler(msg);
+            return;
+        }
+
+        if (line.startsWith("R")) {
+            const pipeIdx1 = line.indexOf("|");
+            if (pipeIdx1 === -1) return;
+            const pipeIdx2 = line.indexOf("|", pipeIdx1 + 1);
+            const seq = parseInt(line.substring(1, pipeIdx1), 10);
+            const pending = this.pending.get(seq);
+            if (!pending) return;
+            this.pending.delete(seq);
+
+            // The documentation's examples show replies without the hex result: "R0|state=STANDBY ...".
+            // A real result field contains only hex digits, so anything else is the message itself.
+            const first = line.substring(pipeIdx1 + 1, pipeIdx2 !== -1 ? pipeIdx2 : undefined);
+            const hasResult = pipeIdx2 !== -1 && /^[0-9a-fA-F]+$/.test(first);
+            const hexResult = hasResult ? first : "0";
+            const message = hasResult ? line.substring(pipeIdx2 + 1) : line.substring(pipeIdx1 + 1);
+
+            if (parseInt(hexResult, 16) !== 0) {
+                const error = new Error(`Command error: 0x${hexResult} - ${message}`);
+                error.code = hexResult;
+                pending.reject(error);
+            } else {
+                pending.resolve(message);
+            }
+        }
+    }
+
+    sendCommand(cmd, timeoutMs) {
+        const seq = this.nextSeq();
+        return new Promise((resolve, reject) => {
+            const entry = { resolve, reject };
+            if (timeoutMs) {
+                const timer = setTimeout(() => {
+                    this.pending.delete(seq);
+                    const error = new Error(`Timeout waiting for reply to '${cmd}'`);
+                    error.code = "ETIMEDOUT";
+                    reject(error);
+                }, timeoutMs);
+                entry.resolve = (v) => { clearTimeout(timer); resolve(v); };
+                entry.reject = (e) => { clearTimeout(timer); reject(e); };
+            }
+            this.pending.set(seq, entry);
+            this.socket.write(`C${seq}|${cmd}\n`);
+        });
+    }
+
+    onStatus(handler) {
+        this.statusHandler = handler;
+    }
+
+    onBanner(handler) {
+        this.bannerHandler = handler;
+    }
+
+    // Called for every received line, before it is interpreted. Used to learn undocumented traffic.
+    onLine(handler) {
+        this.lineHandler = handler;
+    }
+}
+
+const toValue = (value) => {
+    if (value === "") return value;
+    const n = Number(value);
+    return Number.isNaN(n) ? value : n;
+};
+
+// Parses "key=value key=value ..." (optionally prefixed by a word such as "status").
+const parseKeyValues = (msg) => {
+    const kv = {};
+    const re = /([\w-]+)=(\S*)/g;
+    let m;
+    while ((m = re.exec(msg)) !== null) {
+        kv[m[1]] = toValue(m[2]);
+    }
+    return kv;
+};
+
+// "V3.8.8 AUTH"
+const parseBanner = (line) => {
+    const tokens = line.trim().split(/\s+/);
+    return {
+        firmware: tokens[0].replace(/^V/, ""),
+        authRequired: tokens.includes("AUTH"),
+    };
+};
+
+exports.GeniusPGProtocol = GeniusPGProtocol;
+exports.parseKeyValues = parseKeyValues;
+exports.parseBanner = parseBanner;

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jorgen Dahl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,106 @@
-# Temporary Holding Version
+# node-red-contrib-power-genius
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Node-RED nodes for monitoring a FlexRadio / 4O3A PowerGenius XL (PGXL) amplifier over its TCP API (port 9008).
+Framing: `C<seq>|<command>` request, `R<seq>|<hex>|<message>` reply, `S<n>|<message>` asynchronous status.
+
+Requires Node.js 18 or newer and Node-RED 3.1.0 or newer.
+
+[![Node.js CI](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/node.js.yml/badge.svg)](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/node.js.yml) [![Node.js Package](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/npm-publish.yml/badge.svg)](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/npm-publish.yml) [![CodeQL](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/codeql-analysis.yml) [![njsscan sarif](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/njsscan-analysis.yml/badge.svg)](https://github.com/sm6srw/node-red-contrib-power-genius/actions/workflows/njsscan-analysis.yml)
+> **Work in progress.** The API documentation ([API Docs](API%20Docs/PGXL-Amplifier-to-Radio-API-Documentation.pdf),
+> firmware 3.8.8) only covers a few commands and says little about the replies, so the nodes keep whatever the
+> amplifier sends. The property tables below come from a real amplifier (firmware 3.9.9); units not given in the
+> documentation are inferred.
+
+## Nodes
+
+- **power-genius-server** (config): host, port (default 9008), auto connect and status poll interval (default 1000 ms, 0 = off).
+- **power-genius-status**: emits one status property per node, or *all* as an object. The property is picked from a list, or typed (*other*) so that properties missing from the documentation can be used. Emits `msg.payload` (the value), `msg.topic` (the property name) and `msg.previous`. With `*`, `msg.payload` is the whole status object and `msg.topic` is `status`. By default it only emits when the value changes; an optional deadband suppresses small numeric changes. A start delay (default 1000 ms) holds back the first output after deploy so that downstream nodes, such as dashboard widgets, can initialize. Any input emits the last known value and refreshes from the device.
+- **power-genius-info**: emits the device info once after connecting, either as an object or as a single property. Any input re-reads and emits it.
+- **power-genius-control**: switches `operate` (standby / operate), selects the `antenna` (1-3, amplifiers with the antenna switch only), sets the `fanmode` (`STANDARD`, `CONTEST` or `BROADCAST`), or sends any command (`command`, the payload is the command) and outputs the reply as `msg.payload`. The action is fixed in the node, or taken from `msg.topic` when the node is set to `msg.topic`; a fixed action always wins. For `operate` the payload is `true`/`false`, `1`/`0` or `"on"`/`"off"`; anything else is rejected and nothing is sent.
+
+### Status properties
+
+The `status` reply is a list of `key=value` pairs; numbers are emitted as numbers, everything else as text.
+
+| Property | Meaning | Values / unit |
+|---|---|---|
+| `state` | Amplifier state | `STANDBY`, `IDLE` (operate, not transmitting), `TRANSMIT_A`, `TRANSMIT_B`; probably `FAULT` |
+| `bandA`, `bandB` | Band of slice A / B | metres, e.g. `20` |
+| `bsrcA`, `bsrcB` | Source of the band data | e.g. `FLEX` |
+| `bsrcAutoA`, `bsrcAutoB` | Band source selected automatically | 1 = yes, 0 = no |
+| `flexA`, `flexB` | FlexRadio nickname (FLEX mode) | text |
+| `vac` | Mains voltage | V |
+| `vdd` | Supply voltage | V; 0 when not transmitting |
+| `id`, `peakid` | Drain current, and its peak | A; 0 when not transmitting |
+| `fwd`, `peakfwd` | Forward power, and its peak | dBm; `fwd` is 30 (the meter minimum) when there is no RF, `peakfwd` keeps the last peak |
+| `swr` | Return loss | dB (negative, e.g. -18; the FLEX `RL` meter); -60 when there is no RF |
+| `temp` | PA temperature | °C |
+| `hltemp` | Harmonic load temperature | °C |
+| `cntfreq` | Frequency counted from the RF | kHz, e.g. 14098; 0 when there is no RF |
+| `cat1freq`, `cat2freq` | Frequency from CAT port 1 / 2 (legacy radios with CAT or CI-V) | kHz; 0 in FLEX mode |
+| `biasA`, `biasB` | Bias setting of input A / B, as `SOURCE_MODE` | e.g. `RADIO_AB`; others seen elsewhere: `AUTO_AAB`, `MANUAL_A` |
+| `fanmode` | Fan mode | `STANDARD`, `CONTEST`, `BROADCAST` |
+| `meffa` | MeFFA state | `OFF`, `ACTIVE`; may name a fault such as SWR, TEMP or CURRENT |
+| `unkey` | Protection fault | 1 = active protection fault, 0 = normal operation |
+| `antA` | Antenna selected on the antenna switch | Only on the 3-port antenna switch version; 0 on the SO2R version, which has no switch |
+| `ants` | Antenna switch | 0 on the SO2R version (no antenna switch); values on the antenna switch version not seen yet |
+
+Many status properties are only meaningful for some radio setups. With a FlexRadio (FLEX mode) the amplifier gets the
+band and PTT from the radio over the network, and the properties for legacy radios using CAT or CI-V, such as
+`cat1freq` and `cat2freq`, stay at 0 (the `catradioA`/`catradioB` info objects likewise describe the legacy radio setup).
+It is not known which of the remaining properties, for example `bsrcAutoA/B`, belong to which mode, since the test amplifier is
+used with a FlexRadio.
+
+Units are taken from the FLEX meter definitions in the API documentation and from observed values. There are two
+hardware versions: SO2R, and one with a 3-port antenna switch. `antA` and `ants` were only seen on the SO2R version.
+Other properties may show up on other
+firmware or setups: use a status node
+with property `*` and a debug node to list them.
+
+### Info properties
+
+Collected with `setup read`, `ifconf read`, `catradio read=A|B` and `flexradio read=A|B`; each reply is parsed as `key=value` pairs.
+
+| Property | Meaning |
+|---|---|
+| `name` | Device name (the `nickname`, with `_` replaced by a space) |
+| `nickname` | Device name as reported |
+| `firmware` | Firmware version, from the banner the device sends on connect |
+| `authRequired` | `true` when the device asked for authentication (not supported yet) |
+| `ledintens` | LED intensity |
+| `txdelay` | TX delay |
+| `inactivity-timeout` | Inactivity timeout, 0 = off |
+| `authcode` | Authentication code for WAN access. Treat it as a secret: it is part of the whole info object |
+| `ants`, `ant1name`..`ant3name` | Antenna switch setup: `ants` (0 on the SO2R version, which has no switch) and the names of antennas 1-3 (empty when not set) |
+| `ifconf` | Object with the network configuration: `address`, `netmask`, `gateway`, `dhcp`, `dhcpstatus` and the active `address-status`, `netmask-status`, `gateway-status` |
+| `catradioA`, `catradioB` | Objects with the CAT radio configuration of slice A / B, used with legacy radios (CAT or CI-V): `type`, `baud`, `parity`, `stopbits`, `civ`, `active` |
+| `flexradioA`, `flexradioB` | Objects with the FlexRadio configuration of slice A / B: `serial`, `txant`, `ptt`, `active` |
+
+## Commands used
+
+Read-only: `status`, `setup read`, `ifconf read`, `catradio read={A|B}`, `flexradio read={A|B}`.
+Through the control node: `operate={0|1}` (0 = standby, 1 = operate), `antenna={n}` (select the antenna, only on the
+antenna switch version), `setup fanmode={STANDARD|CONTEST|BROADCAST}` and anything with the `command` action.
+
+`operate` comes from another open-source PGXL client ([Log4YM](https://github.com/brianbruff/Log4YM)) and works; it is not
+in the API documentation. `antenna=1` is known to exist: the SO2R version answers `0x50000013 - No antenna switch on this hardware`.
+The antenna numbers (assumed 1-3) have not been tried on an amplifier with the switch.
+
+## Learning what the amplifier sends
+
+- Set the Node-RED log level to `trace` to log every line received from the amplifier.
+- Use a **power-genius-control** node with action `command` to try commands and see the replies. An error with result code `0x50000015` means the amplifier does not know the command.
+
+Commands are sent as `C<seq>|<command>` terminated by a bare LF; the documentation says CR, but LF works.
+
+Not supported: authentication (`AUTH` in the banner, only outside the local network), UDP discovery, and the FLEX radio-side commands (`amplifier create`, `meter create`, `interlock create`, ...), which the amplifier sends to the radio, not to clients.
+
+## Example
+
+An example flow is included. After installing, use **Import → Examples → node-red-contrib-power-genius** in the editor.
+Set the host of the **power genius** server node to your amplifier before deploying. The flow is in
+[examples/power-genius-example.json](examples/power-genius-example.json).
+
+## Install
+
+    npm install node-red-contrib-power-genius

package/examples/power-genius-example.json

@@ -0,0 +1,238 @@
+[
+    {
+        "id": "pg-tab",
+        "type": "tab",
+        "label": "Power Genius",
+        "disabled": false,
+        "info": "Example flow for node-red-contrib-power-genius.\n\nSet the host of the **power genius** server node to the address of your PowerGenius XL, deploy, and watch the debug sidebar."
+    },
+    {
+        "id": "pg-server",
+        "type": "power-genius-server",
+        "host": "192.168.1.100",
+        "port": 9008,
+        "autoConnect": true,
+        "pollInterval": 1000
+    },
+    {
+        "id": "pg-comment-setup",
+        "type": "comment",
+        "z": "pg-tab",
+        "name": "Setup: edit the power genius server node (host), then deploy",
+        "info": "Double click any Power Genius node, then the pencil next to Server, and enter the host name or IP address of the amplifier. The API port is 9008.",
+        "x": 280,
+        "y": 40,
+        "wires": []
+    },
+    {
+        "id": "pg-comment-monitor",
+        "type": "comment",
+        "z": "pg-tab",
+        "name": "Monitor: the whole status, and one property",
+        "info": "The first status node emits the whole status as an object. Use it to find out which properties your amplifier reports, then add one status node per property you care about.",
+        "x": 220,
+        "y": 100,
+        "wires": []
+    },
+    {
+        "id": "pg-status-all",
+        "type": "power-genius-status",
+        "z": "pg-tab",
+        "name": "",
+        "server": "pg-server",
+        "property": "*",
+        "onlyChange": true,
+        "deadband": 0,
+        "startDelay": 1000,
+        "x": 150,
+        "y": 160,
+        "wires": [["pg-debug-status"]]
+    },
+    {
+        "id": "pg-debug-status",
+        "type": "debug",
+        "z": "pg-tab",
+        "name": "status",
+        "active": true,
+        "tosidebar": true,
+        "console": false,
+        "tostatus": false,
+        "complete": "payload",
+        "targetType": "msg",
+        "x": 400,
+        "y": 160,
+        "wires": []
+    },
+    {
+        "id": "pg-status-state",
+        "type": "power-genius-status",
+        "z": "pg-tab",
+        "name": "",
+        "server": "pg-server",
+        "property": "state",
+        "onlyChange": true,
+        "deadband": 0,
+        "startDelay": 1000,
+        "x": 150,
+        "y": 220,
+        "wires": [["pg-debug-state"]]
+    },
+    {
+        "id": "pg-debug-state",
+        "type": "debug",
+        "z": "pg-tab",
+        "name": "state",
+        "active": true,
+        "tosidebar": true,
+        "console": false,
+        "tostatus": true,
+        "complete": "payload",
+        "targetType": "msg",
+        "statusVal": "payload",
+        "statusType": "auto",
+        "x": 400,
+        "y": 220,
+        "wires": []
+    },
+    {
+        "id": "pg-comment-info",
+        "type": "comment",
+        "z": "pg-tab",
+        "name": "Info: setup and interface configuration",
+        "info": "Emits the device info after connecting. Click the inject button to read it again.",
+        "x": 210,
+        "y": 280,
+        "wires": []
+    },
+    {
+        "id": "pg-inject-info",
+        "type": "inject",
+        "z": "pg-tab",
+        "name": "read info",
+        "props": [{ "p": "payload" }],
+        "repeat": "",
+        "crontab": "",
+        "once": false,
+        "onceDelay": 0.1,
+        "topic": "",
+        "payload": "",
+        "payloadType": "date",
+        "x": 120,
+        "y": 340,
+        "wires": [["pg-info"]]
+    },
+    {
+        "id": "pg-info",
+        "type": "power-genius-info",
+        "z": "pg-tab",
+        "name": "",
+        "server": "pg-server",
+        "property": "*",
+        "startDelay": 1000,
+        "x": 280,
+        "y": 340,
+        "wires": [["pg-debug-info"]]
+    },
+    {
+        "id": "pg-debug-info",
+        "type": "debug",
+        "z": "pg-tab",
+        "name": "info",
+        "active": true,
+        "tosidebar": true,
+        "console": false,
+        "tostatus": false,
+        "complete": "payload",
+        "targetType": "msg",
+        "x": 450,
+        "y": 340,
+        "wires": []
+    },
+    {
+        "id": "pg-comment-control",
+        "type": "comment",
+        "z": "pg-tab",
+        "name": "Control: operate / standby, or any command",
+        "info": "The control node takes its action from msg.topic. With topic 'operate' the payload is true/false (or 1/0, on/off) and 'operate=<0|1>' is sent. With topic 'command' the payload is sent as the command, for example 'setup read' or 'ping', and the reply is output. Watch the state property of the status node change between STANDBY and IDLE.",
+        "x": 190,
+        "y": 400,
+        "wires": []
+    },
+    {
+        "id": "pg-inject-operate",
+        "type": "inject",
+        "z": "pg-tab",
+        "name": "operate",
+        "props": [{ "p": "payload" }, { "p": "topic", "vt": "str" }],
+        "repeat": "",
+        "crontab": "",
+        "once": false,
+        "onceDelay": 0.1,
+        "topic": "operate",
+        "payload": "true",
+        "payloadType": "bool",
+        "x": 120,
+        "y": 460,
+        "wires": [["pg-control"]]
+    },
+    {
+        "id": "pg-inject-standby",
+        "type": "inject",
+        "z": "pg-tab",
+        "name": "standby",
+        "props": [{ "p": "payload" }, { "p": "topic", "vt": "str" }],
+        "repeat": "",
+        "crontab": "",
+        "once": false,
+        "onceDelay": 0.1,
+        "topic": "operate",
+        "payload": "false",
+        "payloadType": "bool",
+        "x": 120,
+        "y": 520,
+        "wires": [["pg-control"]]
+    },
+    {
+        "id": "pg-inject-command",
+        "type": "inject",
+        "z": "pg-tab",
+        "name": "setup read",
+        "props": [{ "p": "payload" }, { "p": "topic", "vt": "str" }],
+        "repeat": "",
+        "crontab": "",
+        "once": false,
+        "onceDelay": 0.1,
+        "topic": "command",
+        "payload": "setup read",
+        "payloadType": "str",
+        "x": 130,
+        "y": 580,
+        "wires": [["pg-control"]]
+    },
+    {
+        "id": "pg-control",
+        "type": "power-genius-control",
+        "z": "pg-tab",
+        "name": "",
+        "server": "pg-server",
+        "action": "",
+        "x": 300,
+        "y": 520,
+        "wires": [["pg-debug-reply"]]
+    },
+    {
+        "id": "pg-debug-reply",
+        "type": "debug",
+        "z": "pg-tab",
+        "name": "reply",
+        "active": true,
+        "tosidebar": true,
+        "console": false,
+        "tostatus": false,
+        "complete": "payload",
+        "targetType": "msg",
+        "x": 470,
+        "y": 520,
+        "wires": []
+    }
+]

package/package.json

@@ -1,6 +1,61 @@
 {
   "name": "node-red-contrib-power-genius",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "1.0.0",
+  "description": "Power Genius XL Control and Monitoring Nodes",
+  "keywords": [
+    "node-red",
+    "power genius",
+    "pgxl",
+    "4o3a",
+    "flexradio",
+    "ham radio",
+    "sm6srw",
+    "nu1t"
+  ],
+  "scripts": {
+    "test": "jest --coverage",
+    "watch": "jest --watch",
+    "preversion": "npm test"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/sm6srw/node-red-contrib-power-genius.git"
+  },
+  "author": "Jorgen Dahl",
+  "license": "MIT",
+  "bugs": {
+    "url": "https://github.com/sm6srw/node-red-contrib-power-genius/issues"
+  },
+  "homepage": "https://github.com/sm6srw/node-red-contrib-power-genius#readme",
+  "engines": {
+    "node": ">=18"
+  },
+  "files": [
+    "*.js",
+    "*.html",
+    "examples"
+  ],
+  "node-red": {
+    "version": ">=3.1.0",
+    "nodes": {
+      "power-genius-server": "power-genius-server.js",
+      "power-genius-status": "power-genius-status.js",
+      "power-genius-info": "power-genius-info.js",
+      "power-genius-control": "power-genius-control.js"
+    }
+  },
+  "dependencies": {},
+  "devDependencies": {
+    "auto-dist-tag": "^2.1.1",
+    "jest": "^28.1.3",
+    "node-red": "^5.0.0",
+    "node-red-node-test-helper": "^0.3.6"
+  },
+  "overrides": {
+    "multer": "^2.5.0",
+    "body-parser": "^1.20.9"
+  },
+  "jest": {
+    "verbose": true
+  }
+}

package/power-genius-control.html

@@ -0,0 +1,69 @@
+<script type="text/javascript">
+    RED.nodes.registerType("power-genius-control", {
+        category: "Power Genius",
+        color: "#a6bbcf",
+        defaults: {
+            name: { value: "" },
+            server: { type: "power-genius-server", required: true },
+            action: { value: "" },
+        },
+        inputs: 1,
+        outputs: 1,
+        icon: "bridge.svg",
+        label: function () {
+            return this.name || "pg control";
+        },
+    });
+</script>
+
+<script type="text/html" data-template-name="power-genius-control">
+    <div class="form-row">
+        <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+        <input type="text" id="node-input-name" />
+    </div>
+    <div class="form-row">
+        <label for="node-input-server"><i class="fa fa-server"></i> Server</label>
+        <input type="text" id="node-input-server" />
+    </div>
+    <div class="form-row">
+        <label for="node-input-action"><i class="fa fa-cog"></i> Action</label>
+        <select id="node-input-action">
+            <option value="">msg.topic</option>
+            <option value="operate">operate</option>
+            <option value="antenna">antenna</option>
+            <option value="fanmode">fanmode</option>
+            <option value="command">command</option>
+        </select>
+    </div>
+</script>
+
+<script type="text/markdown" data-help-name="power-genius-control">
+Controls the Power Genius XL.
+
+### Input
+
+: topic (string) : `operate`, `antenna`, `fanmode` or `command`. Only used when the node's Action is set to `msg.topic`; a fixed action in the node always takes precedence.
+
+: payload (boolean|number|string) : Depends on the action:
+
+| Action | Payload | Command sent |
+|---|---|---|
+| `operate` | `true`, `1`, `"1"` or `"on"` for operate, `false`, `0`, `"0"` or `"off"` for standby. Anything else is an error and nothing is sent. | `operate=<1\|0>` |
+| `antenna` | The antenna number, 1-3. Only for amplifiers with the antenna switch; the SO2R version answers with an error | `antenna=<n>` |
+| `fanmode` | `STANDARD`, `CONTEST` or `BROADCAST` (any case). Shows up as `fanmode` in the status | `setup fanmode=<mode>` |
+| `command` | The command, on a single line, for example `setup read` or `ping` | The payload as it is |
+
+### Output
+
+: topic (string) : The action.
+: payload (string) : The reply message from the amplifier, for example `key=value key=value ...`. Empty when the command has no reply message.
+
+A failed command is reported as an error on the node, with the result code from the amplifier. For example
+`0x50000015` means that the amplifier does not know the command, and `0x50000013` that the hardware has no antenna switch.
+
+### Details
+
+`command` is for trying out commands that the API documentation does not cover. Commands that change the
+configuration, such as `ifconf`, `catradio` and `flexradio`, take effect after `save`, which reboots the amplifier. Use with care.
+The effect of `operate` shows up in the status `state` (`STANDBY`, or `IDLE` when operating).
+</script>