Aqara WP-P01D still publishes power reports even when EP21 reporting is disabled (Zigbee2MQTT + SLZB-MR1)

Developer Hub
,
1

Aqara WP-P01D still publishes power reports even when EP21 reporting is disabled

Hi Aqara team & community,

I’m running a large Zigbee network (~116 devices, mostly Aqara) using a SMLIGHT SLZB-MR1 coordinator and Zigbee2MQTT 2.6.1.
My goal is to keep on/off state updates instant, but reduce network chatter — especially power reports — to keep the mesh healthy and automations fast.

I’ve posted a detailed breakdown of my tests and findings here:
:link: Zigbee2MQTT Discussion #28742 – “Aqara WP-P01D power spam despite EP21 reporting disabled”

TL;DR of the Issue

  • Device: Aqara WP-P01D (EU plug, lumi.plug.maeu01)
  • Cluster: genAnalogInput, Endpoint 21, Attribute presentValue (watts)
  • Expected:
    After unbinding EP21 and setting reporting to max=65535, the plug should stop sending power reports.
  • Observed:
    Some plugs still send attributeReport messages every 8–12 s even after power-cycling.
    This keeps the network chatty and contributes to congestion.

Why This Matters

I have 40+ of these plugs. When several are under fluctuating load, they dominate network traffic
(20–40 messages per 5-minute window per plug). This causes:

  • Congestion on the Zigbee mesh (more retries, occasional delays)
  • Worse stability for other devices (some briefly go “unavailable”)

What I Tried

  • :white_check_mark: Unbound EP21 (genAnalogInput) from Coordinator
  • :white_check_mark: Disabled EP21 reporting (max=65535) and power-cycled plugs
  • :white_check_mark: Tried “loose but enabled” reporting (min = 60 s, max = 7200 s, Δ = 15 W) — slightly better, but still chatty
  • :white_check_mark: Verified binds & reporting fleet-wide (custom audit script)
  • :white_check_mark: Reduced coordinator TX power to 20 dBm (per SLZB recommendation)
  • :white_check_mark: Switched last_seen format to ISO8601 (helped availability ping traffic)

Despite all of this, power updates keep coming in.

Questions for Aqara

  1. Is this expected behavior?
    Do WP-P01D plugs send power reports via a “lifeline” that cannot be disabled via standard ZCL configureReporting?
  2. Firmware option or attribute?
    Is there a manufacturer-specific attribute/command to fully silence or slow power reporting?
  3. Best practice for large networks:
    For installations with dozens of WP-P01D, is there a recommended way to keep the network healthy
    (less chatty but still accurate power/energy data)?

Would love to hear from others running many WP-P01D plugs — have you managed to quiet them down without losing on/off state updates?

2

@t11111 Hey there! Thanks for sharing such a detailed and in-depth exploration of this issue you’re facing with the Aqara WP-P01D plugs in your Zigbee network. It’s super valuable when community members take the time to document their tests and findings like you have.

Regarding your questions, unfortunately, I couldn’t find any relevant information in the reference materials provided. But don’t worry! This is a great opportunity for our community to come together and collaborate. Maybe others who have experience with these plugs or large Zigbee networks will chime in and share their insights.

If you have any suggestions or ideas for improvement, you can submit manual customer service feedback. This way, the relevant team can look into it and see if there’s anything that can be done to address your concerns.

Let’s hope we can find a solution to keep your network healthy and running smoothly without sacrificing the on/off state updates. Looking forward to more discussions on this!

1 Like
3

@t11111 Hi there, thanks for sharing this detailed issue and your troubleshooting efforts—it’s really helpful for the community to see such thorough testing!

Unfortunately, the reference information available doesn’t specifically cover the Aqara WP-P01D plug’s power reporting behavior, EP21 configuration, or manufacturer-specific attributes to adjust this. It’s a great question, though, and one that likely resonates with other users running large Zigbee networks.

If you haven’t already, consider reaching out to Aqara Customer Service for more tailored support—they might have additional insights or firmware-related details. You can contact them via the Aqara Home App (Profile>Help&Feedback>Customer Service) or by scanning the QR code:

QR Code
QR Code400×400 9.45 KB
. If you don’t have an Aqara Home account, you can also click here to create a ticket.

Hopefully, other community members with experience with the WP-P01D will chime in with their own workarounds—feel free to keep the thread updated with any progress!

Thanks again for contributing to the discussion—your efforts help make the community stronger.