Innr SP240 - Energy reporting x100

Configuration Zigbee
, , ,
1

Hi
I just got a Sonoff Dongle-e for my Zigbee devices. I had purchased innr SP240 powerplugs to provide me with powerreadings. Afters some tuning in Zigbee2MQTT they started reporting energy consumption (currentSummDelivered). But the value seems to be multiplied by 100, e.g. I have dishwasher that in 1 run consumed 120kWh, which is impossible. I see the same deviation on a boiler which according to the reading consumed 17kWh in just 3hrs. Did I misconfigure something or forgot to configure something. These values also show in Zigbee2MQTT under exposes tab.

The power reading in W, looks OK.

Can anyone help in fixing this? My HA setup is completely up to date (version 2025.5.1, Zigbee2MQTT is on 2.3.0-1)

Edit: I just found this thread [BUG] Innr SP240 newest firmware not compatible anymore with the quirk · Issue #3857 · zigpy/zha-device-handlers. But this doesn’t explain clearly how to fix this. Or should I just wait for an update of either the software of Z2M?

I in the meantime also found out there was a firmware update for the inner plugs they were on 1.7.23. This upgrade should fix it according to this thread Innr SP 240 seMetering.read UNSUPPORTED_ATTRIBUTE · Issue #26288 · Koenkk/zigbee2mqtt.

2

The update made things even worse. It did x10, so now in total the energy reading is x1000 in my case.
Anyone else has this problem and fixed it? I find workaround in ZHA, but I’m using Z2M and I don’t know the workarounds/fixes can be used in my setup.

3

I finally found a working solution, thanks to the information on this github: Innr SP 240 no Energy Data · Issue #26787 · Koenkk/zigbee2mqtt
TL;DR: 1. updated the plugs using Z2M OTA to version 1.9.30 (the most recent at time of writing)
2. in Z2M did a reconfigure
3. set the reporting as in the screenshot in the github.

Hope this information can help others who run into this issue

4

I just went through this and can confirm, that it really takes a “reconfigure” (:arrows_clockwise: in the lower left corner of the device). Delete and re-join did not work for me to solve the problems.

Regarding reporting settings, there is no “one size fits all”. It depends on your application. You need to adjust the values to your requirements.

Here are the values explained:

1. Minimum reporting interval (min interval)

  • Unit: seconds
  • Defines how often a report can be sent at most.
  • Example: min=10 → the device will never send reports more frequently than every 10 seconds, even if the value changes rapidly.
  • Useful to avoid flooding the Zigbee network.

2. Maximum reporting interval (max interval)

  • Unit: seconds
  • Defines how often a report must be sent at least, even if there’s no change.
  • Example: max=60 → the device will send a report at least every 60 seconds, even if the consumption didn’t change.
  • Ensures Home Assistant receives a periodic “heartbeat”.

3. Reportable change (reportable change / minimal report change)

  • Unit: depends on the attribute (watts for power, volts for voltage, amps for current, etc.)
  • Defines the minimum change in the measured value that must occur before a report is triggered.
  • Example:
    • change=1 for Power → a report will be sent if the power changes by at least 1 W.
    • change=0.01 for Current → a report will be sent if the current changes by 0.01 A (10 mA).

:arrows_counterclockwise: How they work together

A new report is sent when either of these conditions is true:

  1. The time since the last report > max interval
  2. The time since the last report > min interval AND the change is greater than reportable change

:zap: Example for your SP 240

If you set:

  • min=5
  • max=30
  • change=1 (watts)

Then:

  • The device reports immediately when the power changes by ≥ 1 W, but not more often than every 5 seconds.
  • It reports at least every 30 seconds, even if nothing changed.