dualETH firmware changelog#
Every dualETH firmware release we have published, newest first. To update a node, open the firmware updater in Chrome or Edge and follow the steps — or use the direct link under any version below.
Not sure how updating works? Read the firmware updater guide first.
v7.9.0 — 17 July 2026#
USB setup mode — set a node up with no network
Adds USB setup mode. A node's address, DHCP setting and name can now be read and changed over its USB cable, with nothing plugged into its network port. This is the recovery path for a node sitting on an address nobody remembers, or on a different network to the computer you're using - which previously meant reflashing it to get back in. To enter setup mode the node is restarted and caught in a short window as it starts up; while it is in setup mode its status lights are solid orange and it passes no DMX and no Art-Net, until you restart it again. Requires the expanseElectronics USB service tool. Everything else is unchanged from v7.8.2, which this includes in full - the node starts up about 2.5 seconds slower to allow for the setup window. OTA-safe from v7.5.1+ - device settings are preserved.
v7.8.2 — 11 July 2026#
Important fix: web UI could stop responding + RDM
Recommended for all devices. Fixes a long-standing bug where a node's web interface could stop responding permanently - the node kept working (passing DMX, answering Art-Net, responding to ping) but the browser could no longer reach it, and rebooting did not help. Caused by the node running out of internal network sockets; it could be triggered by any change made from the web interface, so any unit could hit it. Also includes everything from v7.8.x: a new RDM page (the node discovers RDM fixtures on Port A by itself - no lighting console needed - and shows manufacturer, model, DMX address, mode, sensors, lamp and device hours, and status messages, with patching and Identify), and a factory-reset option. OTA-safe from v7.5.1+ - device settings are preserved across the update.
v7.8.0 — 11 July 2026#
RDM: on-node discovery, patching + fixture inspector
Adds an RDM page. The node now discovers RDM fixtures on Port A entirely on its own - no lighting console required - and lists each one with its manufacturer, model, DMX address, footprint and mode. Patch a fixture's DMX address or mode straight from the browser (the node reads the value back from the fixture to confirm it), and flash Identify to find it in the rig. Expand a fixture to inspect it: software version, device and lamp hours, lamp strikes, power cycles, lamp state, every mode name, all sensors (temperatures, fan speeds) and any status messages. All of it is on the REST API too. RDM is Port A only. OTA-safe from v7.5.1+ - device settings are preserved across the update.
v7.7.0 — 16 June 2026#
Night mode (optional) + DMX-in boot fix
Fixes a DMX-input regression where a slow boot (e.g. a slow DHCP lease) could skip a load-bearing startup delay and leave Port A not receiving DMX in input mode. Also adds an optional status-LED night mode + NTP clock that is OFF in this standard build (it is a compile-time feature) plus minor web UI styling fixes. OTA-safe from v7.5.1+ - device settings are preserved across the update.
v7.6.6 — 15 June 2026#
DMX-in reboot fix
Fixes the node rebooting a few seconds after Port A is switched to DMX input (after which it reverted to DMX output). Root cause: the DMX-input callback ran flash-resident code from the UART break interrupt, which faults on the ESP8266 when a break lands during a flash access. The callback is now interrupt-safe and frame handling moved to the main loop; also fixes a DMX double-buffer swap bug. OTA-safe from v7.5.1+ - device settings are preserved across the update.
v7.6.5 — 5 June 2026#
RDM/Art-Net reliability fixes
Reliability sweep fixing the EXCP/HWDT reboots and settings loss seen in the field. Crash counters no longer ratchet watchdog/exception resets into a settings wipe or a node that stops outputting. The device now survives sustained Art-Net traffic: fixed a DMX-TX interrupt storm that starved the W5500 SPI, and an unbounded Art-Net packet read that smashed the stack under that contention. Also fixes an RDM receive-buffer overflow, and the node no longer reboots when management tools (e.g. DMX Workshop) rebuild their node list. OTA-safe from v7.5.1+ - device settings are preserved across the update.
v7.5.2 — 13 May 2026#
Per-unit serial number (DE-XXXXXXXXXXXX)
Each device now reports a human-readable serial number derived deterministically from the ESP8266 chip ID — format DE- followed by 12 base36 characters (e.g. DE-HI98I0YTL2B7). The serial appears on the Device Status page in the dashboard and on the /api/identify and /api/status REST endpoints. Computation is deterministic — re-flashing the same module always produces the same serial. Intended as a label-printable handle for production fixtures; it's not a security identifier.