Add Innr SP 244 v2 smart plug v1.9.30

[zigpy-bot]

OTA File Submission

File Information

• Filename: 1166-0336-191E3685_8008e8.ota
• Original Filename: 1166-0336-191e3685-sp244v2-1.9.30.ota
• Manufacturer (user provided): Innr
• Manufacturer Directory: innr
• Manufacturer ID: 0x1166 (4454)
• Image Type: 0x0336 (822)
• File Version: 0x191E3685 (421410437)
• File Size: 285,042 bytes
• Header String: Telink OTA Sample Usage
• Hosting: Repository file (hosted in zigpy-ota)
• Existing Images Handling: Keep all existing images
• Tested on Device: Yes

Metadata

• Source URL: https://github.com/user-attachments/files/24494598/1166-0336-191e3685-sp244v2-1.9.30.zip

Release Notes

This updates the Innr SP 244 v2 smart plug to firmware version 1.9.30.

Note: Please reload ZHA or restart Home Assistant shortly after this update is fully applied to avoid an incorrectly increased "summation delivered" state.

Note: The relay may turn on or off during the upgrade process.

Changes compared to version 1.7.23 and older

• Fixed attribute reporting failing after power-cycle
• Improved default attribute reporting settings
• Improved thresholds for the resettable voltage and current overload protection
• Added possibility to disable voltage overload protection
• kWh in 3 decimals instead of 2
• Added Multiplier and Divisor for kWh
• Various bug fixes and performance improvements

Disabling voltage overload protection

To disable voltage overload protection:

1. Keep the button pressed between 15 and 20 seconds, then release
2. After 5 seconds, the LED will start quick-blinking; keep the button pressed
3. After 10 seconds, blinking stops; keep the button pressed
4. After 15 seconds, the LED will start quick-blinking again
5. Release the button. The LED will slow-blink 3 times to indicate success

Enable again in the same way.

Enabled/disabled state is persisted over power-cycles, even if not connected to a bridge.
While voltage overload protection is disabled, every on/off action will double-blink the LED before assuming final state.

Current overload protection cannot be disabled.

Overload behavior

• If the voltage or current overload protection triggers, the plug switches off and fast-blinks its LED
• If the cause was voltage overload, the plug will go back to normal operation automatically when the overload condition disappears
• If the cause was current overload, the plug will stay off and in overload condition until manually operated, either with the button or by power-cycling

---

• Closes Add Innr SP 244 v2 v1.9.30 #21
• Submitted by @GerryInnr

[TheJulianJES]

This looks good. Thanks!

Note for anyone installing this update:

• If you have issues with the "summation delivered" sensor not showing the expected state, make sure you're running Home Assistant Core 2026.1.1 (or newer) and restart HA after applying the update.

  • If you continue to face issues, removing and re-pairing the device should solve the issue.
  • If you don't want to remove and re-pair the device, you can also force a read of the updated divisor attribute on the Metering cluster. To do this, follow these instructions:
    1. Go to the device page of the smart plug in Home Assistant.
    2. On the left, next to "reconfigure", press the three dots, and click "Manage Zigbee device".
    3. Stay on the default "Clusters" tab and select the Metering cluster in the first dropdown menu.
    4. After that's chosen, select the divisor (id: 0x0302) attribute in second dropdown menu below.
    5. Finally, press "Read attribute".
    6. Afterwards, your "Summation delivered" sensor should show the correct values again.

• If you experience an issue where sensors of the plug are not updating, press the "Reconfigure" button on the device page in Home Assistant. Then, start the reconfiguration. This will re-set up attribute reporting. Older firmware versions of the plug could sometimes forget this. With this new firmware update, it should persist properly.

Alternatively, you can also remove the device from Home Assistant and then re-pair it.

If you face any of the described issues or others, please leave a comment here. We can update the release notes in HA to include more details then (or pull the update if something goes really bad).