[ddwrt] Initial contribution of DD-WRT/OpenWrt/Tomato SSH based binding

[ballle98]

New binding that monitors and manages DD-WRT, OpenWrt, Tomato, and generic Linux routers/access points via SSH. It auto-detects the wireless chipset driver (Broadcom wl, Atheros wl_atheros, Marvell iwinfo, OpenWrt iwinfo, generic iw) and adapts its commands accordingly.

Features:

Device telemetry — CPU load, CPU temperature, uptime, WAN IP, interface traffic counters
Wireless radio monitoring — SSID, channel, mode, associated client list
Wireless client tracking — online/offline state, signal strength, SNR, roaming between APs, MAC randomization support (hostname-based identification)
Syslog monitoring — real-time DHCP, wireless association, warning, and error events via logread -f, tail -F, or journalctl -f
Firewall rule control — enable/disable DD-WRT GUI-configured filter rules via nvram
Device reboot — remote reboot via SSH
Automatic discovery — devices on the network bridge, radios per device, wireless clients, and firewall rules
Thing types: network (bridge), device, radio, wireless-client, firewall-rule Channel types: 40 channels across 4 thing types covering telemetry, radio status, client details, syslog events (state + trigger), and firewall state

Architecture:

Single network bridge manages multiple devices; all things are children of the bridge
Per-device SSH session with automatic recovery on connection loss
Per-device refresh thread with catch-all exception handling for resilience
Chipset auto-detection from SSH MOTD banner and runtime probing
SshLogFollower with auto-reconnect for continuous syslog streaming
DDWRTNetworkCache (ConcurrentHashMap-based) for thread-safe device/client/radio state
OUI database for generating human-readable hostnames for devices without DHCP names
Ed25519 SSH key support in OSGi via explicit JCA provider registration
SSH ~/.ssh/config integration (ProxyJump, User, Port, IdentityFile)
Tests: 58 unit tests across 3 test classes (SyslogParserTest, OuiDatabaseTest, DDWRTNetworkCacheTest)

Dependencies:

Apache SSHD 2.17.1 (sshd-osgi), net.i2p.crypto eddsa 0.3.0

Prior discussion:

fix #18282
Community forum: https://community.openhab.org/t/considering-a-new-dd-wrt-binding/162386

Marketplace

https://community.openhab.org/t/dd-wrt-binding-5-1-0-0-6-0-0-0/168973

Tested with:

DD-WRT (Netgear R7000 Broadcom & Linksys WRT1900ACS Marvell chipsets) — gateway router
OpenWrt 24.10 (MediaTek MT7981, Cudy WR3000) — mesh AP

[openhab-bot]

This pull request has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/considering-a-new-dd-wrt-binding/162386/9

[lsiepel]

Thanks, this is a first pass, review half of the files to get an impression and i think these comments can be applied on multiple places. Once these are addressed we can continue with the next review iteration.

[lsiepel]

I re-opened some comments. When i try to build the binding locally, many tests fail. I also see build errors, have not checked SAT, please check that too.

[ERROR]   SyslogParserTest.testAnsiEscapesStripped:183 
Expected: is not null
     but: was null

[ballle98]

I re-opened some comments. When i try to build the binding locally, many tests fail. I also see build errors, have not checked SAT, please check that too.

[ERROR]   SyslogParserTest.testAnsiEscapesStripped:183 
Expected: is not null
     but: was null

Looks like the CI build passed. And I ran a CI build locally with no issues. There are no issues in target/summary_report.html

   {
          "label": "Maven CI Verify",
          "type": "shell",
          "command": "./mvnw",
          "options": {
              "cwd": "${workspaceFolder}/../.."
          },
          "group": {
              "kind": "build"
          },
          "args": [
              "clean",
              "verify",
              "-B",
              "-T",
              "1.5C",
              "-U",
              "-am",
              "-amd",
              "-pl",
              ":org.openhab.binding.ddwrt,:org.openhab.addons.bom.openhab-core-index,:org.openhab.addons.bom.runtime-index,:org.openhab.addons.bom.test-index,-:org.openhab.addons.reactor.features.karaf,-:org.openhab.addons.features.karaf.openhab-addons,-:org.openhab.addons.features.karaf.openhab-addons-external"
          ],
          "problemMatcher": [],
          "detail": "CI-like clean verify build for ddwrt binding from openhab-addons root"
      },

[INFO] Reactor Summary for openHAB Add-ons 5.2.0-SNAPSHOT:
[INFO] 
[INFO] openHAB Add-ons .................................... SUCCESS [ 12.419 s]
[INFO] openHAB Add-ons :: BOM ............................. SUCCESS [  0.042 s]
[INFO] openHAB Add-ons :: BOM :: Runtime Index ............ SUCCESS [  2.985 s]
[INFO] openHAB Add-ons :: BOM :: Test Index ............... SUCCESS [  1.698 s]
[INFO] openHAB Add-ons :: BOM :: openHAB Core Index ....... SUCCESS [ 37.721 s]
[INFO] openHAB Add-ons :: Bundles ......................... SUCCESS [01:15 min]
[INFO] openHAB Add-ons :: Bundles :: ddwrt Binding ........ SUCCESS [ 30.316 s]
[INFO] openHAB Add-ons :: BOM :: openHAB Add-ons .......... SUCCESS [01:27 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:28 min (Wall Clock)
[INFO] Finished at: 2026-04-18T07:44:20-05:00
[INFO] ------------------------------------------------------------------------

[ballle98]

@lsiepel please review. Install from marketplace should work now.

[ballle98]

@lsiepel I believe I have addressed all your comments. Did I miss anything? Do you have additional comments?

[Copilot]

Pull request overview

Copilot reviewed 54 out of 55 changed files in this pull request and generated 3 comments.

[lsiepel]

Another pass, not yet fully covered everything, but don;t want to hold back these comments.

[lsiepel]

Not sure about the signalstrength, as it is more quality of sigtnal

[lsiepel]

Many minor/nitpicks. The exception handling and logging need to be checked binding wide.
Regarding progress; only the handlers are left. I believe we can still get this into 5.2.

[lsiepel]

Thanks, i have now covered all files. Found a few more in the handlers.

[lsiepel]

Thanks, while there are still some minor cleanups possible, i think the model is solid and as this is a new binding the risk is about zero and certainly not warrants postponing for another 6 months.

LGTM

You could add the addon's logo to the openHAB website. See https://www.openhab.org/docs/developer/addons/#add-your-add-on-s-logo-to-the-openhab-website-and-the-ui