A used Meta Portal as a local-voice Home Assistant display
A Nest Hub-style screen that shows a Home Assistant dashboard and answers voice commands usually means buying a tablet and a stand, or waiting for hardware that keeps selling out. A used Meta Portal does the same job for the price of a takeout meal. Meta stopped selling the Portal line in 2022[1], so the 10-inch models turn up on local listings for under CA$40, and they are a good screen with far-field microphones and a decent speaker already built in.
The part that used to be fiddly, making a locked-down Meta device boot into your own software and stay that way, is now one script. Kiosk Satellite’s author ships a provisioner, portal-root-kiosk-satellite, that installs Kiosk Satellite and sets the Portal up for it: the app becomes the device owner and the home screen, ADB stays on across reboots, and Meta’s unused software is trimmed[2]. So this guide is short. Get the Portal ready, run the provisioner, then point Kiosk Satellite at Home Assistant. It is for someone who runs Home Assistant already and is comfortable with a terminal.
At the end:
- The Portal boots straight into Kiosk Satellite and shows a Home Assistant dashboard.
- It is a native Home Assistant voice satellite: a wake word wakes it, speech is transcribed, the Assist pipeline answers, and the reply comes back through the Portal’s speaker. No extra integration to install in Home Assistant[3].
- Home Assistant gains entities for the device: the voice satellite, a screenshot “camera” of the screen, screensaver controls, and a motion sensor[3].
The steps:
- How it fits together
- Before you start
- Enable ADB
- Run the provisioner
- Connect Home Assistant
- What you get
- The microphone
- What is still open
How it fits together#
Kiosk Satellite is two things at once. It is a kiosk browser that shows a Home Assistant dashboard full-screen, and it is a voice satellite that joins Home Assistant as a native ESPHome device[3]. The provisioner handles everything on the Portal; the only work left for you is connecting Kiosk Satellite to Home Assistant and choosing the voice pipeline.
Before you start#
You need:
- A Meta Portal on a model and firmware build the provisioner supports. It lists the exact tested builds[2]; the first-generation 10-inch Portal runs Android 9 (API 28)[4], and several other models are covered. This guide was done on that first-generation 10-inch.
- The Portal taken through its initial on-screen setup and signed into a Facebook or WhatsApp account. That setup has to be finished before the Debug menu and ADB appear[2], and the Portal’s camera and system services still rely on the account afterward, so leave it signed in.
- A Linux host with
adband the Android SDK, which the provisioner uses to build a small on-device helper[2]. - A Home Assistant instance the Portal can reach on the network, and a long-lived access token from an administrator account[5][6].
- The Portal’s physical camera cover open and its camera/microphone privacy control off, which the provisioner’s kiosk profile and presence detection need[2].
A few values differ from setup to setup. Replace the whole placeholder, brackets included, with your own:
| Placeholder | What it is | Where to find it |
|---|---|---|
<PORTAL_IP> |
the Portal’s address on your network | your router, or adb devices once ADB is on |
<HA_URL> |
your Home Assistant address, e.g. http://homeassistant.local:8123 |
your own instance |
<HA_TOKEN> |
an administrator long-lived access token | Home Assistant → User profile → Security → Long-lived access tokens[7] |
<ESPHOME_KEY> |
the device’s ESPHome encryption key | shown inside Kiosk Satellite when you turn on its ESPHome server[3] |
Enable ADB#
ADB is behind a menu Meta left in place. On the Portal, open Settings > Debug, tap ADB Enabled, and enter the device PIN if asked. Connect the Portal to the Linux host with USB-C, and on the first connection tap Allow on the Portal to trust the computer[4].
adb devices
The Portal shows up with a serial and the word device[4]. Stock firmware
turns ADB off again at every reboot, so you may repeat this until the provisioner has run;
making ADB persistent is one of the things it does.
Run the provisioner#
Clone portal-root-kiosk-satellite and run its recommended profile against the Portal[2]. It confirms the Portal is an exact supported model and firmware build, briefly uses a root exploit during a controlled reboot to change settings Android otherwise locks, applies the kiosk profile, and verifies the result across two normal boots. It is not a permanent root: the Portal returns to normal enforcing mode afterward, and only the configuration changes persist.
python3 tools/provision_portal.py --serial <PORTAL_IP>:5555 --profile kiosk
The kiosk profile is the whole Portal-side setup in one run. It installs Kiosk Satellite,
grants it the permissions a voice display needs (microphone, camera, presence, overlays,
background work), makes it the device owner and the home screen, and turns on persistent
wireless ADB. It also lets Kiosk Satellite update itself, stops the Portal from suppressing
the microphone while the speaker is playing, debloats unused Meta apps, removes the local
Meta account, and blocks Meta firmware updates and remote wipes so a stray update can’t
break the setup. The run reboots the Portal several times and finishes with PROVISION_OK.
The project’s README has the full host requirements, the per-model build list and every option. It is Apache-2.0, and the author is clear that low-level changes carry risk, so back up anything important and proceed only if you accept it[2].
When it finishes, the Portal boots into Kiosk Satellite on its own. Everything left is on the Home Assistant side.
Connect Home Assistant#
Kiosk Satellite joins Home Assistant as a native ESPHome device, so there is nothing to
install on the Home Assistant side[3]. In Kiosk Satellite, point it at <HA_URL>,
sign in with <HA_TOKEN>, and turn on its ESPHome server; it generates <ESPHOME_KEY>.
In Home Assistant, open Settings > Devices & services, add the discovered ESPHome
device, and paste <ESPHOME_KEY> when asked for the encryption key[3].
Then pick the Assist pipeline and wake word on the new device’s page. An Assist pipeline is the chain of wake word, speech-to-text, intent and text-to-speech[8], running either locally or through Home Assistant Cloud[9]. On this unit the wake word is “Hey Jarvis” and the pipeline is the Home Assistant Cloud one, so nothing extra runs locally; spoken replies came back about a fifth of a second after the end of speech. Last, set the dashboard Kiosk Satellite should show, in its browser settings. The Kiosk Satellite docs cover the rest of its options[10].
What you get#
Because the device is a native ESPHome device, Home Assistant exposes a set of entities for it automatically[3]:
- the voice satellite itself, as an
assist_satelliteentity, with selects for the assistant pipeline and the wake word. - a Screenshot camera, a still image of whatever is on the Portal’s screen, handy for checking the display from elsewhere in Home Assistant.
- screensaver controls: a switch for whether the screensaver is active, and buttons to postpone it or move to the next slide.
- camera views: a select and per-view “show” buttons, so a Home Assistant automation can throw a camera feed up on the Portal when, say, the doorbell rings.
- a motion binary sensor, a screen-brightness light, and a volume number.
None of this needs any YAML; it arrives with the device.
The microphone#
On this first-generation 10-inch Portal the satellite got the microphone directly, and the provisioner’s audio change, stopping the Portal from muting the mic while the speaker plays, is what keeps it hearing you over its own replies.
Other models differ. The Portal+ runs Meta’s “Hey Alexa” detector, which holds the
far-field microphone and leaves a satellite receive-only until a separate tool frees it; an
unofficial, third-party project, portal-ha-bridge, has a --free-mic option for exactly
that[11]. The Portal Mini’s microphone returns silence to apps, and Kiosk
Satellite falls back automatically. So if voice isn’t being heard on your model, the
microphone is probably held by Meta’s own software, and freeing it is a model-specific step.
What is still open#
The Portal is end-of-line hardware. Meta stopped selling it in 2022[1], and it gets no new features. The one thing not to do is factory reset a working one: the setup you just did and the Facebook or WhatsApp account the Portal still relies on both go away, and putting hardware this old back through Meta’s first-run is a gamble you don’t need. Everything the provisioner changes is reversible without a reset.
If you would rather use the Portal for something other than a Home Assistant display, such as running ordinary Android apps on it, OpenPortal is an open-source tool that manages a Portal from the browser over USB, with sections for installing apps and mirroring the screen and nothing to install on your computer[12].
For under CA$40, salvaged from a product its maker gave up on, it has been a good little display: a crisp screen, microphones that hear across a room, and a voice assistant that answers in a local accent because the pipeline is mine.
Sources#
-
Meta Portal, Wikipedia. Meta announced in June 2022 that it would no longer sell Portal products. ↩︎↩︎
-
portal-root-kiosk-satellite, jxlarrea on GitHub. A host-side provisioner that briefly uses a root exploit during a controlled reboot to make Portal-specific changes persist for Kiosk Satellite: it installs Kiosk Satellite and makes it the device owner and home screen, grants its permissions, keeps wireless ADB alive, allows non-Meta app updates, controls audio processing, debloats and removes the local Meta account, and blocks Meta firmware updates and remote wipes. Runs on a Linux host via
tools/provision_portal.py --profile kiosk; needs the Portal’s initial setup (OOBE) finished and an exact supported model and firmware. Apache-2.0, and it warns that low-level changes carry risk; the first-generation 10-inch Portal (Android 9) is among its tested models. ↩︎↩︎↩︎↩︎↩︎↩︎↩︎ -
Kiosk Satellite ESPHome guide, jxlarrea on GitHub. It presents itself as a fully native ESPHome device and exposes the screenshot camera, RTSP switch, screensaver controls, camera views, motion sensor, screen light and volume; the encryption key is pasted into Home Assistant when configuring the discovered device. ↩︎↩︎↩︎↩︎↩︎↩︎↩︎
-
Portal setup, Meta for Developers. Enabling ADB from Settings > Debug, trusting the computer over USB-C, the
adb devicescheck, and the supported-device table listing the first- and second-generation Portal at minSdkVersion 28. ↩︎↩︎↩︎ -
Kiosk Satellite, jxlarrea on GitHub. Requires Android 7.0 or newer, a reachable Home Assistant instance and a long-lived access token; licensed CC BY-NC-ND 4.0. ↩︎
-
Kiosk Satellite voice satellite guide, jxlarrea on GitHub. Kiosk Satellite is a Home Assistant Assist satellite on its own through its ESPHome server, and the access token should be an administrator’s. ↩︎
-
Securing Home Assistant, Home Assistant. Long-lived access tokens are created from the User profile > Security page. ↩︎
-
Assist pipelines, Home Assistant developer docs. An Assist pipeline strings together wake word detection (optional), speech to text, intent recognition and text to speech. ↩︎
-
Assist, Home Assistant. Assist can work locally or use Home Assistant Cloud voice services. ↩︎
-
Kiosk Satellite documentation, Kiosk Satellite. The project’s guides and reference for running an Android device as a Home Assistant display and voice satellite. ↩︎
-
portal-ha-bridge, RoadRunner-1024 on GitHub. An unofficial, third-party project; its
--free-micflag disables Meta’s “Hey Alexa” detector (com.millennium) to free a first-generation Portal+ microphone, reversible with--restore-mic. ↩︎ -
OpenPortal, andronedev. A browser-based, open-source tool (source) that manages a Meta Portal over USB with nothing to install on the computer; its Apps and Screen sections install apps and mirror the display. ↩︎