Sensors
Dockhand
raetha/ha-dockhand · vv1.11.0
HACSLocal polling
Dockhand Integration for Home Assistant
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 172 (0.02%) |
|---|---|
| GitHub stars | 47 |
| Latest version | v1.11.0 (2026-10-19) |
| Set up in the UI | Yes |
| Maintainers | @raetha |
| License | MIT |
Limitations from the README
- No push updates. Dockhand's API is polled, so changes appear on the next poll (see Data Updates).
- Schedules are read-only. Dockhand's API has no way to run a schedule now, or to enable or disable one.
- Restart only works on running containers and stacks. Docker can't restart a stopped one; turn its switch on instead.
- Runtime controls only for stand-alone containers. Memory, CPU and process limits and the restart policy can't be changed live for a Compose-managed container, since the stack's own compose file would put them back.
- No controls for system containers. Dockhand's own container and Hawser agents (and stacks containing one) get no start/stop/restart switch, button or runtime controls, matching Dockhand's own UI. Dockhand's scheduled update check skips them too, so their updates are found only by Check for updates.
- Install can't move a container to a newer version tag. When Dockhand reports a newer tag (say 2.0 while you run 1.9), moving to it means changing the image tag in the container's or stack's configuration; Install only applies updates to the tag you already use.
- Install can't update an image pinned to a digest. A container running image:tag@sha256:… always gets exactly that image. When the tag moves on, its update entity says so (pinneddigestmoved), but the update is changing the pin in its compose file.
- Git stack deploys follow the stack's own settings. Whether a deploy pulls fresh images is the git stack's "repull images" setting in Dockhand; it can't be overridden per press.
- Resource stats only for running containers. Stopped containers' CPU, memory, network and disk sensors are unavailable, as Dockhand reports nothing for them.
- Containers labelled dockhand.hidden=true never appear, since Dockhand leaves them out of its API.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/raetha/ha-dockhand
- Source code: https://github.com/raetha/ha-dockhand
- Issues: https://github.com/raetha/ha-dockhand/issues
- HACS: https://hacs.xyz
