Two movement modes
Timed commands schedule a stop after seven seconds. Jog commands keep a Bluetooth connection open so the dashboard can send stop when a held button is released.
PROJECT 001 / HOME AUTOMATION
Reverse-engineering my sofa’s Bluetooth controls and bringing them into Home Assistant.
Bluetooth-enabled Poltronesofà sofas with a manufacturer’s app.
A custom Python integration and a Home Assistant dashboard for two sofas.
Headrest, footrest, stop and child-lock controls in my existing smart-home interface.
01 / THE IDEA
I wanted my Poltronesofà sofas to sit alongside the rest of my home controls in Home Assistant. The sofas already had Bluetooth, and the Raspberry Pi 4 running Home Assistant OS already had a Bluetooth radio. The missing piece was understanding the commands.
Rather than adding a separate Wi-Fi controller, I used the existing hardware and built the connection in software. My phone accesses the Home Assistant dashboard over the network; the Pi sends the actual commands to the sofas over Bluetooth.
02 / DECODING BLUETOOTH
I used Android Bluetooth packet captures to analyse the traffic generated by the manufacturer’s app. Comparing the traffic with the controls I pressed let me identify the commands for headrest movement, footrest movement, stop and child locking.
The integration reproduces those command payloads through Bluetooth Low Energy GATT writes. It also subscribes to notifications when querying the sofa’s child-lock state.
# Headrest out: the payload sent over Bluetooth.
headrest_out = bytes.fromhex(
"05 01 05 01 00 00 00 00"
)An example from my integration. Device addresses are not included in this write-up.
03 / THE INTEGRATION
I wrote a custom Home Assistant integration in Python, using Bleak and Home Assistant’s Bluetooth support. The integration exposes button entities for movement and stopping, plus a switch for the child lock.
Timed commands schedule a stop after seven seconds. Jog commands keep a Bluetooth connection open so the dashboard can send stop when a held button is released.
Connection and command retries account for Bluetooth interruptions, with cleanup when operations finish or fail.
Stop requests invalidate older queued movements. The code uses the existing jog connection when available, with a fresh connection as a fallback.
After a child-lock change, the integration queries the sofa again and checks its reported state, rather than simply assuming the command worked.
04 / THE DASHBOARD
I built the dashboard using Home Assistant’s custom button-card: large hold-to-move controls, a prominent stop button and a separate child-lock switch for each sofa.
This browser demo recreates those interactions. It does not connect to Home Assistant, Bluetooth or any real device.
Hold a direction to move. Release to stop.
Tap once. A stop is scheduled after seven seconds.
Ready. This is a simulation, not a live device.
My Home Assistant dashboard labels its one-tap controls “Full travel”. In the integration, these are timed commands with a stop scheduled after seven seconds, not position-controlled moves.
The demo’s percentages are visual simulation values. The integration does not provide measured headrest or footrest positions.
05 / THE TAKEAWAYS
This project brought together protocol analysis, asynchronous Python, Bluetooth communication and interface design. Sending a command was only part of the work: reading state back, handling connections and coordinating movement and stop requests made the integration much more useful.
It is a personal integration built around my own sofas. This page documents that build rather than claiming compatibility with every model.
Working on a similar project? Say hello