Habitat: running my home without hunting for my phone
Four connected devices, four apps taken apart, one Mac app.
On this page
To start my vacuum, I first have to find my phone. And I lose it all the time.
It’s absurd, because I spend my days in front of my Mac. But the vacuum only knows its mobile app. The dining-room bulb goes through Alexa. The TV has its Chromecast, the scale has Withings. Four devices, four apps, four accounts, and nothing that runs on the computer under my hands.
In two days, I replaced all of that with a single Mac app I called Habitat. I click the vacuum in a 3D model of my apartment, or I press ⇧⌘A, and off it goes. To get there, I didn’t install Home Assistant: I opened up each device’s app to understand how it talks to it.
Why not Home Assistant
Home Assistant is the answer I get every time, and it’s a good one. It wasn’t mine, for two reasons.
First, I didn’t want one more dashboard in a browser tab. I wanted a real Mac app that opens with a double-click and obeys the keyboard.
Second, I wanted to know what these devices actually say, to whom, and by which route. Plugging in a ready-made integration wouldn’t have taught me anything.
The method: read before you touch
“Reverse engineering” sounds like hacking. In practice, it’s mostly reading. For each device, I followed the same steps.
Get the official Android app and verify its signature. I don’t install it, I don’t run it.
Decompile it and read how it talks to the device: which addresses, which message format, which key.
Rewrite only that piece, in a small program of my own.
Test read-only first: status, battery, map. No commands until reading is reliable.
Only then send a real command, and check its effect by reading the state back.
Everything happens on my own devices, with my own accounts. And every lead, successful or not, is written down: what was observed, and what is still a guess.
The vacuum: the local control that didn’t exist
My starting goal: drive the Roborock Q7 L5 entirely over the local network, without going through the manufacturer’s servers.
I got fairly far. By reading the app, I rebuilt the pairing handshake, and the robot answered my Mac: 203 bytes, valid checksum. A small moment of victory.
Then the bad news. This model speaks a protocol that only goes through the manufacturer’s cloud. The local port refuses the connection, the app’s code confirms it, and the open-source projects that have studied the range reach the same conclusion.
So I accepted the cloud, but with my own client: sign-in with a code sent by email, session kept in the Mac’s Keychain. The result: 29 operations, the map with its rooms, schedules, history, maintenance.
The surprise came from elsewhere. The robot’s voice pack is a plain ZIP of 124 MP3s, unsigned. I served a modified version from my Mac, and the robot accepted it. When I ask where it is, it now plays three little notes before saying “Salut, je suis là” (“Hi, I’m here”).
The bulb: no way in
The dining-room bulb is an Amazon Basics. To find it on the network, I kept it simple: I switched it off, then on again, watching which address stopped responding.
Then I looked for a door. More than a thousand ports tested, no connection accepted. No Matter announcement picked up, no reply to the usual discovery protocols. That doesn’t prove there’s no local access, only that I didn’t find it.
So it goes through Alexa, and through the Internet. Habitat sends the command, then reads the state back. With a caveat shown in the interface: Alexa may return a cached state, not necessarily what the bulb is doing right now.
The Chromecast: the model student
It’s the only device that plays fair. It announces itself on the network, its protocol is well known, and it asks for no account.
Habitat finds it without me typing an address, then controls playback, pause, volume and the queue. It can also send it a file from the Mac, with its subtitles, converting it if needed.
I added screen sharing from the Mac to the TV. It works, in 720p, without sound, with several seconds of delay. Enough to show something, not to work on it.
The scale: the failure I own
For the Withings scale, I was aiming for Bluetooth: read the weigh-ins directly, with no server. I found the protocol and its authentication mechanism in the app.
Except my Mac never saw the scale. 67 Bluetooth devices detected around me, and none of them was it.
Plan B: I sign in on the official Withings page, in a Habitat window, and the app reads my weigh-ins with that session. It’s less elegant, and the interface doesn’t pretend otherwise: Bluetooth isn’t presented as working.
Habitat: a scale model rather than a dashboard
Once the four devices were reachable, they needed a single interface. I didn’t want a grid of buttons. I modeled my apartment in 3D, furniture included, and each connected device sits where it really is.
I click the pendant light and a small card opens next to it: on/off, brightness, color. Same for the vacuum and the screens. No menu, no device list to scroll through.
And above all, there’s the keyboard.
| Shortcut | Action |
| ⌘L | Turn the light on or off |
| ⇧⌘A | Start the vacuum |
| ⇧⌘P | Pause the vacuum |
| ⇧⌘B | Send it back to its dock |
| ⇧⌘T | Play or pause on the TV |
Two details make me happy every time. When the bulb changes color, the lamp in the model lights the room in the same color. And Habitat tracks the vacuum’s position in the model: all it takes is aligning three corners of its map with my floor plan.
The app is self-contained. It ships with everything it needs and launches with a double-click.
What I take away
“Local” is often an empty promise. Of four devices, only one can really be controlled without the Internet. The other three go through their manufacturer’s servers, whether I like it or not.
A command is a request, not a fact. Habitat never shows “done” on the strength of an acknowledgement: it reads the state back. And it never resends a failed physical command on its own.
Reverse engineering is patience. Most of the time goes into reading, listening to the network and touching nothing. Failures count as much as successes: knowing a door is closed saves you from going back to it.
It’s fragile, and I accept that. A manufacturer update can break one of my adapters overnight. It’s a personal tool, not a product. One smart plug is still holding out, in fact: it isn’t in Habitat.
My phone is still lost somewhere in the apartment. The difference is that the vacuum no longer waits for me to find it.