My smart home spent years talking to me through my phone — automations firing, sensors updating, dashboards refreshing — all of it invisible unless I unlocked a screen and opened an app. The moment I wired my Divoom Pixoo-64 into Home Assistant, that changed. The 64×64 pixel panel beside my monitor became an always-on face for the house: the weather before I leave, the washing machine's progress, a flashing red alert when the doorbell rings. No unlocking, no app hunting. The house finally shows you what it is doing.
If you run Home Assistant, you already know the problem: dashboards are powerful but they live behind glass you have to carry around. This guide walks through the whole journey — installing the community integration through HACS, configuring the device, building your first dashboard pages in YAML, and wiring automations that make the display feel alive. It is written for people who have never touched a custom component before, but move fast if you have.
Watch how the Pixoo-64 behaves on a real desk first — the panel is brighter and more legible at arm's length than photos suggest. Then let's get it into your Home Assistant instance.
Why a 64×64 Panel Fits Home Assistant Better Than Another Phone Tab
Home Assistant already renders beautiful dashboards, so why push data onto a tiny pixel grid? Because of where the information lands. A phone dashboard competes with messages, notifications and muscle memory; a wall-mounted tablet is another screen you walk past. The Pixoo-64 sits in the sweet spot: 64×64 pixels is exactly enough resolution for a temperature, a weather icon, a progress bar or a two-word status — and small enough that it reads as ambient information rather than another display demanding attention.
The hardware earns its place too. At $159.99 you get a large-format pixel panel with dual-band 2.4G and 5G WiFi, which matters for an integration that polls your device over the local network all day. And because the display talks over your LAN rather than a proprietary cloud, your Home Assistant instance can reach it directly — that local-first behavior is precisely why the community integration exists in the first place.
- Information density: 4,096 pixels fit one clean status view — a clock face, a sensor value, an icon — without turning into unreadable clutter.
- Placement freedom: desk stand or wall mount means it can live beside your desk, in the kitchen or by the front door, wherever a glance is worth something.
- Always-on by nature: unlike a phone, the panel stays lit and updated around the clock, which is what a passive dashboard actually needs.
- Community momentum: it is one of the most-discussed pixel displays in Home Assistant circles, which means real configs to learn from, not theory.
Install the Home Assistant Integration Through HACS
The integration that makes all of this possible is a community custom component built by a developer named gickowtf, and it has grown into a genuinely polished project with page types, services and template support. It is not official Divoom software — more on that honestly below — but the installation path is standard Home Assistant territory. You have two options; HACS is the comfortable one.
- Install HACS if you haven't already. HACS (Home Assistant Community Store) is the de facto hub for custom components. If your instance already has it, skip ahead.
- Add the integration repository. In HACS, search for Divoom Pixoo 64, or add the pixoo-homeassistant repo as a custom repository under the Integration category if it doesn't appear in search.
- Download and restart. Download the integration from HACS, then restart Home Assistant so the new custom component is picked up.
- Add it like any built-in integration. Go to Settings, then Integrations, add "Divoom Pixoo 64", and choose either a discovered Pixoo-64 on your network or manual IP entry.
Prefer to skip HACS entirely? You can copy the repository's custom_components/divoom_pixoo folder into your Home Assistant config directory by hand and restart — the same flow, just without the store. And if you ever want to go deeper than Home Assistant and talk to the display with your own scripts, our Pixoo-64 API beginner guide covers the raw local API and Python libraries separately.
Configure Your Pixoo-64 in Home Assistant: Discovery or Manual IP
Once the integration is added, open the device's Configure page. You will set three things: the device's IP address (picked from discovery or typed manually), the scan interval — how many seconds each page stays on screen before rotating — and the list of pages themselves, written in YAML. Two practical notes from the community: give the Pixoo-64 a DHCP reservation on your router so its address never drifts, and make sure it sits on the same network segment as your Home Assistant host, since the integration talks to the display over the LAN.
Every page you define can also carry an enabled flag driven by any Home Assistant entity and its own duration, which overrides the scan interval. That combination — conditional pages with custom durations — is what turns a rotating slideshow into a genuine dashboard that reacts to your home's state.
Build Your First Dashboard Pages in YAML
Pages are where this stops being a gadget and starts being a dashboard. The integration ships with a set of page types — components, clock, gif, channel, visualizer, PV solar overview, progress bar and a fuel-price board — but the components page is your real canvas: stack text, images and rectangles at pixel coordinates and feed them live entity values through Home Assistant templates. Here is a compact weather-plus-sensor card:
- page_type: components
components:
- type: text
position: [0, 0]
content: "Living room {{ states('sensor.living_room_temperature') }} C"
color: [0, 255, 136]
- type: text
position: [0, 12]
content: "{{ states('weather.home') }}"
color: white
- type: image
image_path: /config/img/house.png
position: [38, 28]Positions are XY coordinates on the 64×64 grid, colors accept RGB arrays or preset names, and fonts include pico_8, gicko and a few others documented in the project readme. The changelog lives in the developer's Home Assistant forum thread, which is also the best place to see what other people have built and to ask setup questions.
Pre-designed pages save you the layout work entirely. The progress bar is a favorite for appliance states — dishwasher, EV charging, laundry — and it enables itself only while the appliance runs:
- page_type: progress_bar
enabled: "{{ is_state('sensor.dishwasher_state', 'Run') }}"
header: DISHWASHER
progress: "{{ states('sensor.dishwasher_progress') }}"
footer: "{{ now().strftime('%H:%M') }}"
Automation Ideas That Make the Display Feel Alive
Pages rotate on a timer by default; automations are what make the display react. The integration exposes a light entity for power and brightness control plus a push service — Divoom Pixoo 64: Send a page — that temporarily overrides whatever is on screen. That single service is the doorway to every idea below:
- Doorbell flash: when the doorbell entity triggers, push a red "Someone is at the door" text page for ten seconds, then return to the rotation.
- Sunset scene switch: at sunset, swap the bright daytime clock page for a dimmed animation and drop brightness via the light entity — no more glowing rectangle at night.
- Appliance done: dishwasher or washer finishes, and the display shows a completion page with a buzzer pulse instead of a phone notification you would miss anyway.
- Motion hello: hallway motion after dark pushes a soft welcome face — a small touch that guests always notice.
service: divoom_pixoo.show_message
target:
entity_id: sensor.divoom_pixoo_64_current_page
data:
page_data:
page_type: components
components:
- type: text
position: [0, 30]
content: "Someone is at the door!"
color: [255, 0, 0]Two habits that save headaches
Keep a stable IP for the display with a DHCP reservation, and if animated content ever makes the panel stutter, drop the brightness a notch — several long-term users report crashes stop once the display runs around 90% or lower. It is also worth knowing the integration takes over the screen while it runs, so if family members like picking art in the Divoom app, pin a custom channel page for them instead of fighting the rotation.
Pixoo-64 vs Tidbyt: An Honest Home Assistant Matchup
Any smart home discussion of pixel dashboards eventually reaches Tidbyt, which has built much of its marketing around Home Assistant compatibility. Both displays can show sensor data, clocks and animations, and both are loved in the community. The differences are in the philosophy: Tidbyt leans on its own app and cloud-connected ecosystem with community apps, while the Pixoo-64 is a display-first canvas whose Home Assistant integration talks to it locally through a community component — with the Divoom app covering everything else, from millions of community pixel art designs to social counters.
| Factor |
Pixoo-64 $159.99 |
Tidbyt Gen 2 Tidbyt ecosystem |
|---|---|---|
| Home Assistant link | Community HACS integration, local LAN control, YAML pages and services | Official-style HA integration plus the Tidbyt app ecosystem |
| Panel | 64×64 LED panel — the largest in Divoom's Pixoo line | 32×32-style LED matrix, smaller canvas |
| Beyond the dashboard | Full Divoom app ecosystem: pixel art editor, community gallery, clocks, social counters | Tidbyt app store of community apps and watch faces |
| Best fit | You want a bigger canvas, local control and one display that doubles as an art frame | You want the Tidbyt app ecosystem specifically |
Neither choice is wrong, but the Pixoo-64 wins on canvas size and on living a double life: the same panel that shows your dishwasher progress at noon can carry pixel art or a clock face the rest of the day. If your household would judge a dashboard display by what it shows when nothing is happening, that versatility matters.
Divoom Pixoo-64
A 64×64 WiFi pixel display for $159.99 — big enough for real dashboard content, playful enough to double as your desk's art frame.
View Pixoo-64Frequently Asked Questions
Is the Home Assistant integration official?
No — it is a community-built custom component, and the developer states clearly that it is not official Divoom software and Divoom provides no support for it. That is normal in the Home Assistant world; many beloved integrations start community-made. For the display itself — first-time WiFi setup, pairing and hardware questions — the official product manual remains the right reference.
Do I need HACS to install it?
HACS is the easiest route, but not mandatory. You can also download the repository and copy its custom_components/divoom_pixoo folder into your Home Assistant config folder, then restart. Both paths end at the same place: adding "Divoom Pixoo 64" under Settings and Integrations.
Why does the display override what I set in the Divoom app?
That is the integration doing its job — it rotates through your configured pages on the scan interval. If someone in the house wants to keep art chosen in the Divoom app visible, define a channel page pointing at one of the display's three custom channels, or use an input boolean to disable the page list when you want free app control.
Can it show what's playing on my media player?
Yes. Image components accept a templated image URL, so you can feed the entity image of a media player into the page; community members have also published companion projects that push album art to the display automatically. The project's GitHub discussions are the best place to find those configs.
The Last Screen Your Smart Home Was Missing
A smart home produces a constant stream of useful truth — temperatures, states, arrivals, cycles finishing — and most of that stream dies quietly in logbooks and phone notifications. A pixel display wired into Home Assistant changes the physics: the information becomes ambient, glanceable, always on. After a few weeks, walking into the room and simply seeing the house's state feels less like a feature and more like the way it should have worked all along.
That is the case for the Pixoo-64 in one line: it is the largest canvas in the Divoom pixel display family, it speaks to Home Assistant over your own network, and when nothing needs saying it goes back to being art. Install the integration, start with a clock and one sensor, then let your automations take it from there — your smart home has been waiting for a face.
