I have a Snapdragon laptop, a desktop PC and a Home Assistant box on a
Raspberry Pi. I wanted the computers in Home Assistant like any other device:
sensors, power buttons, notifications, media. The usual answer is HASS.Agent
plus an MQTT broker. HASS.Agent had no native ARM64 build, and I didn't want
a broker just so two machines in the same house could talk.

So I built Deskmate. It's a desktop app (Tauri 2, Rust, React) and its own
Home Assistant integration (Python, in the default HACS catalog). It's MIT
licensed. This post is about the three parts I use every day and a few
design decisions behind them.

One encrypted connection instead of a broker

The integration opens a WebSocket endpoint inside Home Assistant. The PC
connects to it with a pairing code you copy from the integration's setup
screen. Every session starts with a fresh X25519 key exchange, frames are
AES-256-GCM with replay protection, and a second cipher layer can be turned
on. Keys live in Windows Credential Manager, or in the keyring on Linux.

Home Assistant never sends code to run. A command is an ID that the PC looks
up in its own configuration, so a compromised Home Assistant can press the
buttons you created, and nothing else. The protocol also refuses to
downgrade: a version or cipher mismatch is rejected with a reason instead of
falling back quietly.

Files between the phone and the PC

This is the feature I didn't expect to use so much. A panel in the Home
Assistant sidebar lets you send files from your phone to the PC and download
from folders you chose to share. No cloud, no cable, no extra app on the
phone: the Home Assistant app is already there.

Paths go through an allowlist with canonicalized paths. Traversal, UNC and
device paths, alternate data streams and reparse points are refused, and a
received file never overwrites an existing one. There's a shared clipboard
too: copy on the PC, paste on the phone, and the other way round.

Music

The PC shows up as a media_player entity, so any media card works: what's
playing, play and pause, next and previous, volume and mute. From Home
Assistant you can also switch Windows between speakers and headphones or mute
the microphone, which is handy before a call.

Screen time for kids, without a Microsoft account

Windows' own family features need a Microsoft account for the child and work
through the cloud. Deskmate does it locally: a daily limit per Windows
account, allowed hours, and a block list for games and apps. The child gets
an "Ask for more time" button; the request reaches your phone as a Home
Assistant notification and you add minutes with one tap. Time is counted on
the PC, so it works without internet, and with one administrator password a
child can't just close it.

Everything else

  • Sensors: CPU, memory, disks, network, battery, GPU and temperatures, idle time (game controllers count), lock state, screen on.
  • Power: sleep, hibernate, restart, shut down, lock, brightness, and your own scripts as buttons, switches and sliders.
  • Notifications with a picture and buttons that trigger automations.
  • An optional Windows service that keeps the PC in Home Assistant at the sign-in screen and after a reboot, with a Connection sensor that tells "asleep" from "off" from "lost".
  • A Linux daemon and desktop app (preview), x86_64 and ARM64.
  • Hotkeys, an always-on-top widget panel, and a Stream Deck plugin.
  • Signed automatic updates, no telemetry, and every sensor that reveals what you're doing is off until you turn it on.

A few things I learned

Opt-in by default costs nothing. The active window, Wi-Fi name and
camera-in-use sensors are useful, but they also describe your day. Making them
off by default meant one extra click for people who want them and no awkward
surprises for anyone else.

Write the threat model down. docs/SECURITY.md lists what Deskmate
protects against and what it doesn't. Writing it forced decisions that would
otherwise have stayed vague, for example that Home Assistant can never trigger
an update, only the app can.

ARM64 needs care with dependencies. Some popular Rust crypto and TLS crates
pull in a C toolchain that breaks the Windows ARM64 build. CI checks the
dependency tree for both Windows targets so this can't creep back in.

Try it

  1. In HACS, search for Deskmate, download it and restart Home Assistant.
  2. Add the Deskmate integration and copy the pairing code.
  3. Install the app from the releases page, paste the code, connect.

GitHub: https://github.com/JakubWawrzola/deskmate

Issues and ideas are welcome. The next version is planned in the open, in
docs/dev/ROADMAP.md.