Most powerline/PLC adapters have no IP, no app API, no web page — just an Ethernet cable. This custom integration talks directly to them over raw Layer 2 (HomePlug AV 0x88E1 + Broadcom MEDIAXTREAM 0x8912), the same protocol the official vendor apps use. No cloud, no IP scanning, no port forwarding.
What it gives you:
Auto-discovery of all adapters on the powerline network
Per-adapter sensors: TX/RX rates, online status, firmware
LED and power-saving control, QoS priority switches (adapter-dependent)
Restart button
Live topology card — mesh graph of your powerline network in Lovelace
Optional sidebar panel and alerts when links degrade
Verified hardware: TP-Link AV1000 (TL-PA7017, BCM60355) and AV500 (QCA7420), including two AV500s talking to each other. Also supports FRITZ!Powerline (AVM) with LED control and restart.
Safety: config writes are a read-modify-write of the adapter’s own PIB (never a hard-coded image), using the same checksum scheme the vendor app uses. A rejected write is detected and reverted — this will not brick your adapter.
Install via HACS (custom repository) or manually — see the README for setup and the protocol writeup.
Bug reports and Wireshark captures from other adapter chipsets welcome.
Do you know if Powerline Network integration should be expected to work with Netgear PLP2000 Powerline Adapter? I’ve got two of those in my network, but in trying to initialize the integration, it says “No Powerline adapters found.”
The Netgear device uses Homeplug AV2. I don’t know which chipset they use.
I am running HAOS, so it appears I should not need explicit CAP_NET_RAW ?
The PLP2000 is Netgear’s AV2-1200 adapter — HomePlug AV2 isn’t officially supported/tested yet in this integration. So far it’s only been verified on AV500 (Qualcomm QCA7420) and AV1000 (Broadcom BCM60355). Discovery works by sending HomePlug vendor frames (Ethertype 0x88e1/0x8912); if the AV2 chipset/firmware responds differently, you’ll get “No Powerline adapters found” even with everything wired correctly.
On the CAP_NET_RAW question: you’re right, under HAOS you don’t need to set it explicitly — host networking is the default there, so it works out of the box.
I haven’t had an AV2 adapter in my hands so far, which is why it isn’t supported yet. But if you’re up for capturing some traffic with Wireshark (filter: eth.type == 0x88e1 || eth.type == 0x8912, capturing the official Netgear app performing an action) and sharing it, AV2 support could finally make it in!
