4-Socket Smart Powerstrip

Enhancing Commercial 4-Socket Powerstrip With ESPHome-Based Home Assistant Controller

In this article, I am turning a 4-Socket Commericial Powerstrip into a Home Assistant-compatible smart powerstrip that can be remotely controlled via WiFi.

Parts Cost
manually switchable powerstrip €9.00
ESP32-C33 Super Mini €1.50
2x 2 Circuit Solid State Relais 2x €2.20
4x Bi-Color Bi-Polar LED €1.90 for 100
5V1A AC Power Supply €2.10

Preparing Manual Powerstrip

Open and disassemble the powerstrip you want to use. Make sure it is a powerstrip with individually switchable sockets.

Adding Microcontroller

For this project, I am using a ESP32-C3 Super Mini because of its tiny footprint and low cost.

ESPHome Configuration

The microcontroller controls four sockets and uses two GPIOs per switch that are inverted (so you can use low level trigger and high level trigger relais, and can use bi-polar bi-color signal LEDs).

Here is the ESPHome configuration:

esphome:
  name: powerstrip-400w-ssr-1
  friendly_name: SSR PowerStrip 400W
  platformio_options:
    board_build.f_flash: 40000000L
    board_build.flash_mode: dio
    board_build.flash_size: 4MB

esp32:
  board: esp32-c3-devkitm-1
  variant: esp32c3
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "xxx"

ota:
  - platform: esphome
    password: "xxx"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Powerstrip-Ssr-400W"
    password: "xxx"

captive_portal:


light:
  - platform: status_led
    name: "Status LED"
    id: esp_status_led
    icon: "mdi:alarm-light"
    pin:
      number: GPIO8
      inverted: true
    restore_mode: ALWAYS_OFF

output:
  - platform: gpio
    pin: GPIO0
    id: 'relay1'
    inverted: true
  - platform: gpio
    pin: GPIO2
    id: 'led1'
  - platform: gpio
    pin: GPIO3
    id: 'relay2'
    inverted: true
  - platform: gpio
    pin: GPIO4
    id: 'led2'
  - platform: gpio
    pin: GPIO21
    id: 'relay3'
    inverted: true
  - platform: gpio
    pin: GPIO20
    id: 'led3'
  - platform: gpio
    pin: GPIO10
    id: 'relay4'
    inverted: true
  - platform: gpio
    pin: GPIO7
    id: 'led4'
  
switch:
  - platform: output
    name: "Switch1"
    icon: "mdi:power-socket-eu"
    restore_mode: RESTORE_DEFAULT_OFF
    output: relay1
    on_turn_on:
      then: 
        - output.turn_on: led1
    on_turn_off:
      then:
        - output.turn_off: led1

  - platform: output
    name: "Switch2"
    icon: "mdi:power-socket-eu"
    restore_mode: RESTORE_DEFAULT_OFF
    output: relay2
    on_turn_on:
      then: 
        - output.turn_on: led2
    on_turn_off:
      then:
        - output.turn_off: led2
  
  - platform: output
    name: "Switch3"
    icon: "mdi:power-socket-eu"
    restore_mode: RESTORE_DEFAULT_OFF
    output: relay3
    on_turn_on:
      then: 
        - output.turn_on: led3
    on_turn_off:
      then:
        - output.turn_off: led3

  - platform: output
    name: "Switch4"
    icon: "mdi:power-socket-eu"
    restore_mode: RESTORE_DEFAULT_OFF
    output: relay4
    on_turn_on:
      then: 
        - output.turn_on: led4
    on_turn_off:
      then:
        - output.turn_off: led4

Testing

Upload the ESPHome configuration to the microcontroller, and make sure everything works as expected before you proceed with anything else:

  • Add to Home Assistant: Home Assistant should recognize your new device once it goes online for the first time. Add it to Home Assistant
  • Visit Device: In Home Assistant, go to Settings/Devices&services, click Devices tab, search for your device name, and check to see whether your device (and all of its entities) can be found.

  • Test-Drive Switches: Open the device and double-check that the Controls section looks like this:

    Without connecting anything to the microcontroller, you can already test it: use the Status LED switch in the Home Assistant control panel to turn the blue on-boad LED on and off.

Once everything works, disconnect the microcontroller and mount it to the powerstrip. Since the AC-driven 5V power supply won’t be functional until at the very end, connect the microcontroller to a powerbank via its USB connection so you can continuously test it while adding LEDs and relais boards.

Do not connect AC to the powerstrip at this time. Since there are many uninsulated open contacts, that would be irresponsible and dangerous. We’ll be able to do all testing with a safe 5V voltage supply from a USB powerbank.

Custom Expansion Board

You can either solder wires directly to the microcontroller board, or build yourself a simple expansion board if you prefer to plug in wires (enabling you to easily experiment and change wiring).

The microcontroller plugs into the inner header row:

If you use standard perfboard, connect the pins on the backside so that each GPIO is accessible via three sockets. A more convenient way would be to use a stripe board.

Mounting Microcontroller

The powerstrip housing has plenty of screw mounts that originally secured the mechanical switches and now can be used to secure microcontroller and relais boards.

Mount directly

If you’d like to mount the microcontroller board as-is, this 3D printed part slides over one of the screw mounts:

Flipped over, you see the recess for the screw that secures the part to the housing:

Slide the part over one of the screw pilars, then use the original screw to secure the part to it. Now you can glue the microcontroller board onto the mounting area:

Mounting Expansion Board

If you use an expansion board, the overall height is limited. In this case, drill a 8mm hole in the middle of the PCB so that it can slide onto the plastic pilar of the original housing.

With an even smaller 3D printed part, it can then be secured using the original screw:

Slide the PCB over one of the srew pilars:

Press the 3D part onto the pilar until the PCB is tightly fixed. Then use the original screw to tighten the cap on the pilar:

Finally, plug in the ESP32 C3 Super Mini. You now have plenty of headroom to use header pins and cables and be able to later close the original housing without issues:

Adding Bi-Color Signal LEDs

The original powerstrip came with simple 3mm red signal LEDs that are directly wired to AC power and on when a particular socket was powered. You can leave them in place if you want to save some time and effort.

If you opt for more sophisticated signal LEDs that can signal both on and off state (in red and green), replace the existing LED with 3mm bi-color bi-polar LEDs that can emit two colors, based on their polarity.

Adding bi-color signal LEDs roughly doubles the build time for this project. It is much easier to continue to use the existing simple signal LEDs (in which case you can skip the next paragraph).

LED Replacement

Pull out the existing LED, and de-solder their wires from the sockets (including their current limiting resistors).

Solder a 150R current limiting resistor to one leg of your bi-polar LED. Solder two wires to the LED that are long enough to be connected to the microcontroller. Plug the wires into the two GPIOs that represent one switch, i.e. use GPIO0 and GPIO2 for switch 1 (see ESPHome configuration above for GPIO assignments).

I had a left-over reel of 150R SMD resistors and used these with the LEDs. It is a bit more fiddly but works well. A regular resistor is much easier to solder. Don’t forget to use shrink tube to insulate and protect resistor and solder connections.

Once you connect the LED to the microcontroller, power it on using external power (i.e. a powerbank). The LED should show a red light. If it emits green, then switch over the cables (reverse LED polarity).

Next, go to Home Assistant again, and navigate to your device’s control panel (see above).

  • Turn Switch 1 on. The LED should turn green. Turn off the switch. The LED should turn red.
  • Turn on the switch again, then remove power from the microcontroller. The LED is off. Now restore power. The LED should immediately come up with a green light. Thanks to the restore mode, each switch remembers its state.

Once all four LED work as expected, you can position them in the existing 3mm LED holes with a drop of super glue. Now it’s time to add the relais that do the actual AC switching.

Mounting Solid State Relais

I chose commonly available DIY AC solid state relays. Both low level and high level trigger boards work:

DIY SSR can handle light loads of up to 440W (2A). For switching low current lights, that is perfect. If you need to switch larger loads, do use appropriately rated mechanical relais or industrial SSR. When using the SSR I used here, clearly label your powerstrip. You (or others) may not remember this crucial limitation when the powerstrip is in use later.

These boards come with low-quality screw terminals that are too small to use larger-diameter wire, plus the terminals waste a lot of space. That’s why I decided to remove the screw terminals with a hot air gun, and solder cables directly.

If you don’t feel comfortable removing them, you could also solder your own wires directly to the solder pins on the backside of the board.

Each relay board comes with two relais, so two boards are required.

You can get these SSR boards also with just one, or with four SSR relais. Since the boards need to fit into the existing smartstrip housing, using two two-relais boards worked best.

Designing Relais Mount

To safely secure both boards, use 3D printed parts:

The mount is designed to be slid onto one of the screw mounts left from the mechanical switches, then secured with the screw that originally helt a mechanical switch:

This is what the 3D printer part looks like:

Assemble Solid State Relais

The 3d printed part slides onto one of the pillars that previously secured the mechanical buttons:

The part can then be secured using one of the original screws. The SSR is placed onto the part, and also secured using one or two screws:

Wiring

The SSR relais breakout boards have two AC outputs, marked as A1/B1 and A2/B2.

  • Connect the blue AC wire that comes from the outside AC wire to A1 and A2.
  • Connect B1/B2 to one socket each. You may be able to reuse the existing red cable that originally connected to a mechanical button, or replace this wire with a longer wire (just make sure it has a sufficient diameter).
  • On the other (DC) side, the boards require 5V DC, so solder two black and red wires, or use the scew terminals (if you did not remove them).
  • The relais are triggered by CH1/CH2. Triggering can be done with 3.3V, so connect each CHx to one of the GPIOs you assigned to switches.

If you used the ESPHome configuration above, the GPIO assignments are as follows:

Switch Low Active High Active
Switch 1 GPIO0 GPIO2
Switch 2 GPIO3 GPIO4
Switch 3 GPIO21 GPIO20
Switch 4 GPIO10 GPIO7

Relais can be low active (turned on when the GPIO is low) or high active (turned on when the GPIO is high). Since each switch has two complementary GPIOs, just pick the one that matches your relais board.

Power Supply

If the commercial powerstrip comes with a built-in USB power supply, you may be tempted to use it for your microcontroller and relais. That’s what I did first, too, and here are the results:

On the left side, I connected the DC power wires directly to the USB C connector of the built-in power supply:

Caveats

Using a built-in power supply of unknown origin may cause problems:

  • Overload: when a user connects a device to the USB power supply (i.e. a phone charger), this may overload the USB power supply, causing a voltage drop significant enough for the microcontroller to brown out and reset.
  • Bad Quality: I did not anticipate the poor quality of these built-in power supplys: some of the SSR boards did not trigger correctly, most likely because of strong EMI emissions.

Unreliable SSR Trigger

When I tested the setup using a power bank, all worked as expected. Once I powered it via the built-in power supply, strange things happened:

  • The microcontroller continued to work just fine, and also the bi-color signal LEDs switched color based on state alright. So that part was alright, and the supply voltages were ok, too.
  • However, only one SSR switched from on to off and vice versa. All remaining three relais were constantly on. So apparently, there was a problem either with the trigger voltage, or with the SSR boards altogether.

Since the supply voltage was perfectly fine, it seemed unlikely that the built-in power supply was too weak, or that the signal LED would draw too much current and cause a voltage drop at the GPIO.

EMI

What made me wonder was that one relais did work correctly - which happened to be the one with the greatest distance to the USB power supply. So apparently, EMI (electromagnetic interference) generated by the unshielded and rather primitively designed built-in power supply interfered with the SSR breakout boards.

Without further investigation, I removed the built-in USB power supply altogether. I won’t need it anyway, and I definitely do not want to introduce a source of radio interference to my lab where I intend to use the smart powerstrip.

Plus, now I needed the space to fit in a decent quality 5V 1A encapsulated power module from HiLink:

Finalizing

When all changes have been made, and the housing is closed, there are still some holes that were originally used by the manual buttons and the USB power supply.

Below I provided STL files to 3D print covers. You can use any type of cover. Just don’t let these holes be accessible, and do not use simple card board covers: there is dangerous AC voltage directly below. Do not let users ever touch and “explore” these holes.

Here is the original powerstrip with all 3D printed covers in place:

If you (like me) used simple solid state relais boards, make sure you add a prominent sticker that clearly states their limitations: 440W (400W as a safety margin) per socket (relais) is the maximum power they can switch. Do not take this light-heartedly: these SSR will blow in a split-second when overloaded. Use a different type of relais if you need to switch more load.

Learning Points

It’s a thrilling moment when the idea finally materializes, and the end result works really well. I love the bi-color status LEDs, and it’s amazing to see the new smart powerstrip switch loads completely noise-free thanks to the solid state relais.

It is a long way until you get there, though, often much longer than anticipated. And not all of this way is always pure joy. So I took the time to note the lessons I learned from this project.

  • Time: Most ideas seem so simple yet turn out to be much more complex. That’s part of the learning experience, but to not get overwhelmed, try to simplifying projects. The goal should be to get a rewarding final product within the time that you have. No one likes half finished stuff, or revisiting projects from the past. And once you lose the temper and rush things, the project goes downhill for sure: rushing, and being open for shortcuts and cheats, produces errors, and the final result will break easily (if it ever worked). So here are my back thoughts on time:
    • It was a great idea to use a switchable powerstrip to start with. Building a smart powerstrip out of individual sockets and 3D printed housing takes much more time.
    • It is debatable whether the two-color signal LEDs were worth the effort. They look awesome, yet finding these LEDs, adding complexity to the ESPHome configuration, plus a lot more wiring was a price that these LEDs aren’t worth. Keeping the AC powered built-in signal LEDs would have been perfectly fine and cut project time in half. After all, the powerstrips are hidden under the sofa anyway, and signalling a “power on” is really all that’s needed.
  • Material: When needed material isn’t at hand - wires of just the right diameter (big enough for the currents, small enough to fit the through holes) for example - turned out to be the single most important factor for wasting time. Lacking the right components (and having to improvise or work around) is cumbersome and produces bad results. So before starting the project, ask more clearly: what are actually the parts required?
  • Soldering: I can solder quite decently, but I hate it. I am just way too often missing a third arm.
    • PCB Design: I am finally going to look into designing my own PCBs. I tried to ignore this topic but it is just too useful to be avoided. I am definitely fed up with perfboard and having to go through all kinds of compromises.
    • Tools: For cases where soldering is not related to PCBs (i.e. soldering wires or resistors to LEDs directly), I need better helping hands. The ones I have are too unprecise. They swing back and forth. I’d like to have something more rigid, with wheels to move the parts by the millimeter until they perfectly align. Maybe it’s an age thing, too.

Materials

STL file for large microcontroller mount: flat 30x33mm mounting surface
STL file for small microcontroller mount: simple plastic cover to secure a PCB on one of the plastic pilars of the original housing
STL file for SSR mount: mounting part to hold a SSD breakout board.
STL file for round cover: round plastic cover (outer diameter 26mm, inner diameter 24mm) to cover the holes used by the removed mechanical buttons.
STL file for usbport cover: if you remove the built-in USB power supply, this part covers its holes in the housing.

Slow Website?

This website is typically very fast, and pages should appear instantly. If this site is very slow for you, then your routing may be messed up, and this issue does not only affect done.land, but potentially a few other websites and downloads as well. Here are simple steps to speed up your Internet experience and fix issues with slow websites and downloads..

Comments

Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.

Here is how your comments are stored

Whenever you leave a comment, a new github issue is created on your behalf.

  • All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.

  • There is no third-party provider, no disrupting ads, and everything remains transparent inside github.

Github Users Yes, Spammers No

To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.

If you don’t have a github account yet, go get yourself one - it’s free and simple.

If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.

Discussions

For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.

  Show on Github    Submit Issue

(content created Aug 31, 2024 - last updated Sep 07, 2024)