A Raspberry Pi 5 can be used as a dedicated smart home control panel that automatically opens a Home Assistant or Node-RED dashboard after boot, runs it in full-screen kiosk mode, and turns off the display after a period of inactivity.
This setup is useful for wall-mounted home automation panels, smart home control stations, IoT monitoring terminals, and touch-based dashboards. Instead of manually opening a browser every time the Raspberry Pi restarts, the dashboard loads automatically and remains available until the display enters its idle state.
In this guide, I'll walk through configuring Raspberry Pi OS, launching Chromium automatically, displaying a dashboard without browser navigation bars, and managing screen inactivity.
What You Need
The setup requires the following hardware and software:
- Raspberry Pi 5 with Raspberry Pi OS Desktop (64-bit)
- A compatible HDMI or DSI display with touch input
- A stable power supply for the Raspberry Pi 5
- Home Assistant or Node-RED running on your network
- Chromium browser
- A network connection between the Raspberry Pi and your dashboard server
For a compact control panel, a 7-inch touch display is a practical choice because it provides enough space for sensor readings, lighting controls, climate information, and device status without requiring a large installation.
For example, the 7-inch Raspberry Pi 5 compatible touch LCD display development kit provides a 1024 × 600 resolution and capacitive touch interface for building a dedicated smart home dashboard. The Raspberry Pi 5 itself is purchased separately, allowing developers to use their own board.
Configure Raspberry Pi OS to Start Automatically
The first step is to make sure Raspberry Pi OS boots directly into the desktop environment instead of stopping at a terminal or login screen.
Open the Raspberry Pi configuration utility:
sudo raspi-config
Navigate to:
System Options
→ Boot / Auto Login
→ Desktop Autologin
Select the desktop auto-login option. This allows the Raspberry Pi to enter its graphical desktop automatically after restarting.
If you are using Raspberry Pi OS Bookworm or a newer version, the default desktop environment generally uses Wayland with the labwc compositor.
After configuring auto-login, reboot the Raspberry Pi:
sudo reboot
Confirm that the system reaches the desktop without requiring manual login.
Install and Test Chromium
Chromium is the browser used to display the Home Assistant or Node-RED dashboard.
Check whether it is already installed:
chromium --version
If the command is unavailable, install it:
sudo apt update
sudo apt install chromium -y
Before configuring automatic startup, test that the dashboard is accessible from the Raspberry Pi.
For Home Assistant, a typical URL is:
http://192.168.1.100:8123
For Node-RED, the default dashboard address may look like:
http://192.168.1.100:1880/dashboard
Replace the IP address with the actual address of your server. If Home Assistant or Node-RED runs on another device, it is a good idea to configure a DHCP reservation on your router so the server's address does not change.
You should also create a dedicated dashboard for the touch panel. A dashboard designed for a 7-inch display should use larger buttons, simplified navigation, and fewer unnecessary cards.
Launch the Dashboard in Full-Screen Kiosk Mode
Raspberry Pi OS with the labwc desktop environment can launch applications automatically through its autostart configuration.
Create the configuration directory if it does not already exist:
mkdir -p ~/.config/labwc
Open the autostart file:
nano ~/.config/labwc/autostart
Add the following command for a Home Assistant dashboard:
chromium --kiosk --noerrdialogs --disable-infobars --no-first-run "http://192.168.1.100:8123" &
For a Node-RED dashboard, replace the URL:
chromium --kiosk --noerrdialogs --disable-infobars --no-first-run "http://192.168.1.100:1880/dashboard" &
The --kiosk parameter launches Chromium without the normal browser interface. The --noerrdialogs parameter suppresses certain browser error dialogs, while --no-first-run prevents the first-run setup experience from appearing.
The ampersand (&) allows the application to run in the background while the desktop continues loading.
Save the file and exit Nano:
Ctrl + O
Enter
Ctrl + X
Restart the Raspberry Pi:
sudo reboot
After booting, Chromium should automatically open the selected dashboard in full-screen mode.
Prevent the Screen from Going Blank Too Early
The default screen blanking behavior may not be suitable for a permanently installed smart home dashboard.
To configure it, open:
sudo raspi-config
Depending on the Raspberry Pi OS version, navigate to:
Display Options
→ Screen Blanking
Disable the default screen blanking temporarily while testing the kiosk setup.
This prevents the operating system from unexpectedly blanking the screen while you are configuring Chromium or testing your dashboard.
However, disabling screen blanking does not mean the display must remain on permanently. We can implement a separate inactivity policy that controls when the display should enter its low-power state.
Turn Off the Display After 5 Minutes of Inactivity
The important distinction is between turning off the display output and physically switching off the LCD backlight.
These are not always the same thing. Some HDMI monitors support power management or DDC/CI brightness control, while others simply display a black image with the backlight still running. Certain integrated LCD kits also provide their own backlight control interface.
Therefore, the screen-off method depends on the display hardware.
For a display that supports DDC/CI, you can investigate whether its brightness or power state can be controlled through the Raspberry Pi. For example, some HDMI displays support the ddcutil utility.
Install it:
sudo apt install ddcutil -y
Check whether a compatible display is detected:
ddcutil detect
If your display supports DDC/CI, you may be able to control its brightness or power state using supported commands. The exact commands depend on the display and its capabilities.
For displays that expose a backlight control interface through Linux, you can also inspect the available interfaces:
ls /sys/class/backlight/
If a backlight device is detected, inspect its properties:
ls /sys/class/backlight/*/
The available brightness controls depend on the display driver and hardware. Do not assume that every HDMI touch display exposes the same Linux backlight interface.
Create an Inactivity Script
For a display with a controllable backlight, the general approach is to use an idle-monitoring utility to trigger a display power or brightness command after five minutes.
For example, a monitoring utility such as swayidle can be used in Wayland environments to detect inactivity and execute commands.
The intended logic is:
User interacts with dashboard
↓
Display remains active
↓
5 minutes without input
↓
Backlight or display power is disabled
↓
User touches screen
↓
Display is restored
The commands used for turning the backlight off and on should be adapted to the specific display controller.
For example, if your display exposes a brightness interface, the control script can use the appropriate brightness value to reduce the display output to zero and restore the original value when activity is detected.
Before implementing automatic power control, test the display's brightness control manually. This avoids accidentally disabling the display without a reliable way to restore it.
For a touch-based panel, you should also verify that the touch controller remains active while the display is off. On some displays, touch input can wake the display automatically. On others, additional software logic is required to detect the first touch and restore the display.
Configure the Dashboard for Touch Interaction
A kiosk dashboard should be designed for the display rather than simply loading the desktop version of a website.
For Home Assistant, consider creating a dedicated dashboard containing:
- Large lighting control buttons
- Room temperature and humidity readings
- Air-conditioning controls
- Door and window status
- Energy consumption information
- Camera or security status
- Frequently used smart home scenes
For Node-RED, the dashboard can display IoT device status, sensor measurements, switches, and control buttons using a custom layout.
Avoid placing too many controls on a single page. Small touch targets can make the interface difficult to use, especially when the display is mounted on a wall or installed in a fixed control panel.
A 1024 × 600 display can be particularly useful for a landscape-oriented smart home interface with several control cards arranged side by side.
Troubleshooting Common Problems
Chromium does not launch after reboot
Check that the autostart file exists:
cat ~/.config/labwc/autostart
Verify that the dashboard URL is correct and that the Raspberry Pi can access the server.
The dashboard opens but is not full-screen
Confirm that Chromium is launched with the --kiosk parameter. Also check whether another browser instance is already running.
The dashboard shows a login screen every time
Configure the authentication method carefully. A dedicated Home Assistant user is recommended for a permanently installed panel. Avoid exposing the dashboard or disabling authentication in a way that creates an unnecessary security risk.
The screen goes black but the backlight remains on
This may indicate that the operating system is blanking the display output rather than controlling the physical backlight. Check whether your display supports DDC/CI, a Linux backlight interface, or a manufacturer-provided control method.
Touch input does not wake the display
The touch controller may stop responding, or the display power-control method may disable the entire panel. Test the touch controller independently and make sure your power-management script can restore the display when input is detected.
Final Thoughts
A Raspberry Pi 5 can be turned into a practical Home Assistant or Node-RED touch control panel by combining desktop auto-login, Chromium kiosk mode, dashboard optimization, and display inactivity management.
The most important part of the configuration is separating browser startup from display power management. Chromium can reliably launch a dashboard at boot, but turning off the actual LCD backlight after five minutes requires compatible display hardware and an appropriate control method.
For developers building a dedicated IoT or smart home interface, a Raspberry Pi 5 with a compact touch LCD display makes it possible to create a permanent control panel without keeping a keyboard, mouse, or conventional monitor connected.
Top comments (0)