Skip to content

Firmware updates

Power Manifold checks for new firmware once a day and installs new releases by itself. You can also install a release yourself as soon as it is out, put automatic installs off, or turn them off.

When the controller finds a new release, it waits a random 1 to 7 days and then installs it between 03:00 and 05:00 local time. The wait spreads each release over a week, so a release with a problem can be withdrawn before it reaches most controllers. Set the local time with UTC offset in the web interface’s Settings. Until the controller has the time from its time server, it installs a release once the wait is over, at any hour.

Your ports stay on during an automatic update, the same as during one you start. See What happens during an update.

While a release is waiting, the web interface’s Settings shows when it will install, with two buttons:

  • Postpone 7 days holds back automatic installs for a week. Press it again to postpone further.
  • Skip this version stops this release from installing by itself. The next release installs as usual.

Home Assistant has the same two buttons, Postpone update 7 days and Skip this update. Install works in either case. The Skip on Home Assistant’s update card only hides the update in Home Assistant; see Skipping an update.

If an update fails its trial and the controller goes back to the previous firmware, that release is not installed automatically again. You can still install it yourself.

Set Automatic updates to Off in the web interface’s Settings, or turn off the Automatic updates switch in Home Assistant. The controller still checks once a day and shows new releases, and installs one only when you start it. The setting is update_auto in the HTTP API, and update auto off followed by save at the console.

When a new release is out, Home Assistant’s Firmware update entity shows update available, with a link to the release notes. Press Install, and the card shows the download’s progress. The Check for updates button asks right away instead of waiting for the daily check.

The web interface shows it too, on the status line and in the first row of Settings. Press Install there. Check for updates asks right away instead of waiting for the daily check.

You can also install with the HTTP API.

  1. The new firmware downloads next to the one that’s running. The running firmware is kept.

  2. The controller restarts into the new firmware. Your ports stay on. Devices keep their power while the controller restarts.

  3. The new firmware is on trial. It must run properly for ten seconds and connect to the network. Then it becomes the installed version.

  4. If it doesn’t, the controller goes back to the previous firmware by itself, with your settings as they were. If it fails within ten minutes or restarts unexpectedly, it reverts too.

While the controller restarts, the blades keep running with the limits they had and their own protection. Power sharing and fault handling resume once the controller is back, after a few seconds. Devices that are plugged in keep the power they had: the controller sends them no new offer unless the budget no longer covers them.

The new firmware runs on trial. Once it has run properly for ten seconds and reached the network, it is kept. Only then are the blades brought up to date.

1Download2Restart3Trial4KeptController0.12.0 runningA few seconds0.13.0 on trial: 10 s healthy, network up0.13.0 installedPortsOn the whole time: devices keep their powerBladesUnchangedUpdated as each port goes idle

If the new firmware restarts, crashes or hasn’t passed within ten minutes, the controller goes back to the firmware it had, with your settings as they were. The blades were never touched.

1Download2Restart3Trial4Restart5BackController0.12.0 runningA few seconds0.13.0 on trial: crashes, or 10 min passA few seconds0.12.0 running, settings as they werePortsOn the whole time: devices keep their powerBladesUnchanged

A blade waits until its port has nothing to power. Here a phone is unplugged; ten seconds later the blade updates, which takes a few seconds, then starts up and is ready again. At power-up the same happens before the port comes on.

1Charging a phone2Unplugged3Updating4Starting up5ReadyPort lightGreenWhite, for 10 sOffCyan, blinkingWhiteWeb interfaceDelivering 9 VReadyUpdating 0–100%DetectingReadyOther portsUnaffected

The blades have their own firmware, and the controller carries the version that goes with it. After a controller update the controller brings each blade up to date by itself, at a moment when its port is not in use:

  • when the chassis is switched on, or the port is switched on, before the port powers up;
  • when its port has had nothing plugged in for ten seconds;
  • when the device plugged into it is switched off. The controller knows a device is off when it draws less than the Charged below threshold for the …for time: 500 mW for 10 minutes, by default.

Updating a blade takes a few seconds. Its light is off while it happens, and its state shows updating with a percentage. A device that was plugged in reconnects once the port comes back.

A port powering a device that is on, such as a running Raspberry Pi, is not interrupted. Its update waits until the device is unplugged or switched off, or until the port is switched off and on again. If Charged below is set to 0, the controller can’t tell that a device is off, and only unplugging or switching the port off and on lets the update run.

While an update waits, Power Manifold makes it hard to miss:

  • the port’s light flashes amber briefly every 3 seconds;
  • the web interface’s status line says blade update waiting with the port’s name, and the port’s card says how to let the update run;
  • in Home Assistant, the Problem sensor turns on, and a Blade firmware update appears under Settings › Updates. Its Install button updates the waiting blades at once. Their devices lose power for a few seconds, so shut them down first.

Blades always take the firmware the controller carries. This can’t be turned off, because a controller and blades on different versions may not work together.

Every release is signed. The controller only installs firmware that is signed by this project, built for this hardware, and not older than what it is running. Updates come from fw.powermanifold.io, which serves the project’s GitHub releases.

Updates are downloaded over HTTP, not HTTPS. The controller refuses an update address that starts with https://, so a server of your own that hosts the files must serve them over plain HTTP. The signature check is what protects the download.

GitHub releasesSigned by the project
fw.powermanifold.ioPasses them on
Power ManifoldChecks daily, installs automatically or when you say

USB Type-C® and USB-C® are registered trademarks of USB Implementers Forum.