Home Assistant
Power Manifold connects to Home Assistant through an MQTT broker. Once connected, it appears as one device with every port and setting. No YAML configuration is required.
Connect it
Section titled “Connect it”-
Have an MQTT broker. If you don’t have one, install the Mosquitto broker add-on in Home Assistant, then add the MQTT integration. Create a Home Assistant user for Power Manifold to log in with.
-
Point Power Manifold at it. In the web interface’s Settings, fill in the MQTT broker (your Home Assistant’s address), the port (usually 1883) and the user and password. Press Save, then Reboot.
-
Find the device. In Home Assistant, go to Settings → Devices & services → MQTT. Power Manifold appears as a device named after it. Its device info lists the controller’s board ID as the serial number, and the MAC address of each network connection it has.

If you use more than one Power Manifold, give each a different device name before connecting it.
To encrypt the connection to the broker, see MQTT security.
What you get
Section titled “What you get”For each port
Section titled “For each port”Entities are named after the port, so renaming a port renames them. Their entity IDs don’t change.
| Entity | What it does |
|---|---|
| Switch | Turns the port on or off. |
| Power, voltage, current | Live readings, once a second. |
| Energy | Energy delivered since the controller started. Works with the Energy dashboard. |
| State | idle, active, throttled, fault and so on. Its attributes include the most recent fault and when it happened. |
| Contract | The kind of offer the device took: fixed, pps or avs, or none. |
| Charging | On while a device is plugged in and still charging. |
| Converter temperature, plug temperature | Blade temperatures, also while the port is off. |
| Priority, power limit, voltage cap, power-up state, switch off when charged, sleep timer | The port settings. |
| Hard reset | Briefly cuts the port so the device starts its connection over. |
| Re-announce | Sends the device the port’s offer again. |
| Events | Fires on plug-in, unplug, charged, faults and more. See below. |
For the whole chassis
Section titled “For the whole chassis”| Entity | What it does |
|---|---|
| Total power, budget headroom, total energy | How much is being used and how much room is left. |
| Power budget | The chassis budget. |
| Fan | auto, on or off. |
| LED brightness | Port light brightness. |
| Charged below, charged after | When a device counts as charged. |
| Problem | On when something needs attention. Its detail attribute says what. |
| Network | Which connections are online: Ethernet, Wi-Fi, or Ethernet and Wi-Fi. With both online, Ethernet carries the traffic. |
| Bus voltage | The input voltage from your power supply. |
| Open Wi-Fi setup | Opens Wi-Fi setup for ten minutes to change Wi-Fi. |
| Firmware update | Shows when a new release is out, with a link to its release notes. Press Install to update; the card shows the download’s progress. See Updates. |
| Check for updates | Asks for a new release now instead of at the daily check. |
| Blade firmware | Shows an update while a blade’s firmware update waits for its device to be unplugged or switched off. Install updates those blades now, and their devices lose power for a few seconds. See Blade firmware. |
| Automatic updates | On: new releases install by themselves. See Automatic updates. |
| Voltage step events | Off by default. On: every voltage step a PPS or SPR AVS device takes fires a contract event, one for each 0.1 V when a device sweeps its voltage. |
| Postpone update 7 days, Skip this update | Hold back automatic installs for a week, or for the release now offered. The card’s own Skip does not reach the controller; see Skipping an update. |
Skipping an update
Section titled “Skipping an update”The Firmware update card has its own Skip button. That Skip stays inside Home Assistant: it hides the update, but the controller is not told, and still installs the release automatically a few days later. To stop a release from installing, press the controller’s Skip this update button instead.
To make the card’s Skip do the same, add this automation. It presses
Skip this update whenever a version is skipped on the card. Replace
pwrman with your device name.
alias: Pass Power Manifold update skips to the controllertriggers: - trigger: state entity_id: update.pwrman_firmware attribute: skipped_versionconditions: - condition: template value_template: "{{ trigger.to_state.attributes.skipped_version is not none }}"actions: - action: button.press target: entity_id: button.pwrman_skip_this_updateClear skipped on the card does not undo the controller’s skip. The skipped release can still be installed with Install, and the next release installs automatically as usual.
Automations
Section titled “Automations”Each port has an events entity for use as an automation trigger. Its event types are:
| Event | When |
|---|---|
attached / detached |
A device is plugged in or unplugged. |
charged / charging |
A device finished charging, or started again. |
enabled / disabled |
The port was switched on or off. |
auto_off |
Switch off once charged or the sleep timer turned the port off. |
throttled / restored |
The port was turned down for the budget, or got its power back. |
fault |
The port shut itself off. The text attribute says why. |
inserted / removed / ready |
The controller found a port, lost contact with it, or the port finished starting up. |
contract |
The device switched to a different voltage or current. On PPS or SPR AVS, where the device chooses its own voltage, the event comes when it switches to that range or away from it; its voltage changes inside the range show in the port’s sensors instead. Turn on the Voltage step events switch, or the setting of the same name on the web page, to get an event for every step as well. |
probe_failed |
A blade didn’t respond while starting up. |
pd_reset |
The port or the device reset the USB-C® connection, which briefly cuts the device’s power. The text attribute says which side did it and, if the port’s offer had changed since the device was plugged in, how long before. |
updated |
The blade’s firmware was updated. |
Example: get a notification when a port faults.
triggers: - trigger: state entity_id: event.desk_phone_events not_from: unavailableconditions: - condition: state entity_id: event.desk_phone_events attribute: event_type state: faultactions: - action: notify.notify data: message: "Desk phone port: {{ trigger.to_state.attributes.text }}"Example: power-cycle an unresponsive Raspberry Pi by turning its port’s switch off, waiting ten seconds, and turning it back on. This uses the port’s Switch entity, so a script or a dashboard button can do it.
USB Type-C® and USB-C® are registered trademarks of USB Implementers Forum.