Skip to content

Shelly Power Strip 4 Gen4

← README · All devices · Commands

State: partly checked Generation: 4 Chip: ESP32-C6

🧰 Before you start · ⚙️ Config · 📍 Pins · ⚡ Flash it · 👀 What to expect · ↩️ Way back

Gen4 / ESP32-C6. The pins and an example config are on the ESPHome device page (see the table).

Fact Value
Profile PowerStrip
Flash 8 MB
Official package 2.1.0 (stable since 2026-10-14; Bootloader, partition table and filesystem are the same as in 2.0.1; the hardware runs were made with 2.0.1)
Partition table 0x10000
App slot size 0x300000
Bootloader min_version 1.0.9 (set in the profile)
ESPHome device page Shelly Power Strip 4 Gen4

Note

Partly checked: ESPHome boots and joins Wi-Fi/Home Assistant (UART log). Outlets and metering were not checked by this project. The metering was tested on two strips under load by miguelangel-nubla (devices.esphome.io PR #1811); see the notes below.

Before you start

Check first:

  • the device runs Shelly's own firmware, not ESPHome yet
  • you know its IP address (--ip), or this PC is on the device's own access point (default 192.168.33.1)
  • the device can reach this PC: same network, port 8000 (--port) not blocked
  • your ESPHome config uses the partition table below and is compiled
  • a UART adapter is at hand as your way back (Recovery over UART)

Also:

  • The strip runs Shelly firmware 2.0.1: from stock 1.7.99 a direct send did not work, so update once with Shelly first or run python ota.py restore PowerStrip (see Notes).

ESPHome config

Important

build refuses a config without Shelly's partition table. Copy partitions/PowerStrip-stock.csv from this repository next to your YAML and keep CONFIG_PARTITION_TABLE_OFFSET: "0x10000".

esp32:
  variant: ESP32C6
  board: esp32-c6-devkitc-1
  flash_size: 8MB
  partitions: PowerStrip-stock.csv        # copy from partitions/ in this repository
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_PARTITION_TABLE_OFFSET: "0x10000"
    advanced:
      enable_ota_rollback: false

ota:
  - platform: esphome
    allow_partition_access: true

Add this under esphome: (the C6 needs the 80 MHz flash header, otherwise build refuses):

esphome:
  platformio_options:
    board_build.flash_mode: dio
    board_build.f_flash: 80000000L
    board_build.flash_size: 8MB

Tip

The ESPHome device page has the pins and an example config. Replace its esp32: block with the one above, or build refuses it.

Pins

Function Pin Source
SPI MISO / MOSI / SCLK GPIO12 / GPIO11 / GPIO13 stock boot log (SPI2 init ok)
ADE7953 chip select (chip 0 = outlets 4+3 / chip 1 = outlets 2+1) GPIO15 / GPIO10 stock boot log (CS0/1/2: 15/10/-1); the outlet mapping from the stock firmware and PR #1811
ADE7953 IRQ (chip 0 / chip 1) GPIO5 / GPIO6 measured by resetting each chip and watching the line (PR #1811); an earlier version of this page said GPIO6 / GPIO7
Relays 1 to 4 GPIO4 / GPIO2 / GPIO3 / GPIO1 in use on the owner's device
Buttons 1 to 4 (pull-up, inverted) GPIO20 / GPIO22 / GPIO23 / GPIO21 in use on the owner's device
LED ring (WS2812, 12 LEDs, 3 per outlet) GPIO18 in use on the owner's device

Flash it

  1. Install the requirements (once):
pip install -r requirements.txt
  1. Fetch the official package:
python ota.py fetch PowerStrip --insecure
  1. Build: put your app into it; the ZIP goes to out/:
python ota.py build PowerStrip app.ota.bin --esphome-factory app.factory.bin --esphome-yaml shelly-power-strip-gen4.yaml
  1. Check the device first. Nothing is sent:
python ota.py send PowerStrip out/PowerStrip-app-<date>.zip --ip <device IP> --dry-run
  1. Flash it (the log goes to a file with --log-file):
python ota.py send PowerStrip out/PowerStrip-app-<date>.zip --ip <device IP> --log-file

app.ota.bin and app.factory.bin are the two files ESPHome compiles. --dry-run only checks the device and, for this package, reads the update target slot. Command reference: Commands.

What to expect

send shows these lines at the default log level, in this order:

# Log line Meaning
1 Update target slot: 0 ... The slot check of send. Anything else: run python ota.py restore PowerStrip first
2 Device: The bootloader will be replaced ... (raw log: Boot: cur ... min ... update? 1) The installer will write ESPHome's bootloader. WARNING: ESPHome's bootloader was NOT written (update? 0) means it will not: build again with a higher --boot-min-version (why)
3 The progress (Update: ... %, one line that updates in place) up to 100 %, then Done: update installed, the device confirmed it The device restarts into ESPHome

Notes for this device

  • Stock 1.7.99: a direct send did not work: the installer wrote to slot 1 and the old app in app_0 started again, although the update reported success. send now reads the target slot first and refuses; after one official update to 2.0.1 (or ota.py restore PowerStrip) a new send targeted slot 0 and ESPHome started (slot rule). The 1.7.99 installer also left the old partition table (no scratch); after 2.0.1 it was the new one.
  • min_version: with 1.0.9 the installer wrote ESPHome's bootloader (hardware-confirmed).
  • After a good install the UART log shows ESP-IDF ... 2nd stage bootloader, ota data partition invalid and no factory, will try all partitions (expected) and Loaded app from partition at offset 0x20000.
  • OTA encryption: the owner's build requires it (Encryption: required); the example config has no encryption: entry.
  • Metering (from PR #1811, tested on two strips; the stock side read from the 1.7.99 firmware, not tested here):
  • Outlets 4 and 3 are measured by chip 0 (channel A and B), outlets 2 and 1 by chip 1. Channel B of both chips is wired with reversed polarity, so the active power of outlets 3 and 1 needs a factor of -1 (the stock firmware uses a negative scale there too).
  • ESPHome reads the current and power about four times too low with its fixed constants. The stock firmware sets the PGA to 8x on both current channels; ESPHome's constants fit 4x. The ESPHome device page uses a multiply: 4.0 filter instead of the PGA setting, because chip 1 comes back in its power-on state after every ESP32 reboot and loses what ESPHome wrote in setup.

Way back

python ota.py restore PowerStrip sends the official firmware back while Shelly firmware still runs.

Warning

  • Wipes Wi-Fi and settings. ESPHome opens its own access point or joins the Wi-Fi from your config; if nothing comes up, power-cycle the device (help).
  • No way back over the network once ESPHome's bootloader runs: restore gets no answer, only UART brings Shelly OS back (Recovery over UART). Take a flash backup first if you can.
  • Flashed it? Tell us, also when it worked: open a device report.

Bootloader and slots · Troubleshooting · Recovery over UART