MIT · core >=0.1.0-beta.1 · sink · linux_amd64, linux_arm64, darwin_amd64, darwin_arm64, windows_amd64 · 14779.9 KB · Nov 21, 2026
Connect Power Control 0.5.0 answers the review of 0.4.1 and adds support for more plugs.
Security and review points
Every change now asks the server whether the person may make it. Switching a plug and auto-off take
operate_resourceon the extension andoperateon the printer. Plugs, connections, tests and discovery takeconfigure_resource. The actions are declared underchecks.The built-in MQTT broker needs a user name and a password and lets in no client that does not sign in with them. After updating, set both on the Connections tab and in each plug, or the built-in broker stays off.
The built-in broker listens only on the port you approve (
needs.listen, TCP 1883). Testing it opens no other port.The extension reaches its built-in broker in process, with no loopback connection.
New
Ten plug drivers: Tasmota and Shelly (MQTT or by IP address), Zigbee2MQTT, ESPHome, OpenBeken, custom MQTT topics, and Home Assistant.
Settings in three tabs: Plugs (a card for each printer), Connections and Automation, with a guided dialog to set up a plug.
A Power Control page for the whole fleet, and a Printer power dashboard card with a power graph.
A printer can turn off after every print. It turns off only after a print that finished, never after a cancelled, failed or paused one.
The pages show a person only the controls their role may use.
The full list is in CHANGELOG.md.






Sign in to comment.
No comments yet.