Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsYou can build a floor plan dashboard in Home Assistant with the built-in picture-elements card: choose a floor-plan image, add the card to a dashboard view, then position entity icons, labels, and controls over the image. No custom integration or special hardware is required.
What you need before you start
- A readable image of the floor you want to show. The built-in card accepts an image URL; locally hosted images can use Home Assistant hosting, and
media-source://URLs are also supported. - The entity IDs you want to display or control, such as a room light or temperature sensor.
- A dashboard view where the image and its overlays will be useful.
Home Assistant describes the Picture Elements card as “one of the most versatile types of cards.” Its required configuration is a background image and an elements list. See the official Picture Elements documentation.
As an Amazon Associate I earn from qualifying purchases.
The background does not have to be a floor plan; for this project, the floor plan is simply the image that makes the overlays useful. A clear existing image is enough to get started. A community discussion mentions Sweet Home 3D as one possible way to make a plan, but it is an example rather than a requirement: Home Assistant Community: Adding a floor plan.
Recommended Free Tools
Add the built-in card to a dashboard
Open the dashboard you want to use, enter its edit mode, and add a Picture elements card. If you are using Home Assistant’s automatically maintained default dashboard, taking control of it has a trade-off: Home Assistant warns that it will no longer update automatically with new dashboard elements. Consider that before taking control; you can instead create or use another dashboard for the floor plan.
#1 Best Overall
- (1)This is an all-in-one Android multimedia tablet designed specifically for smart home consumers, integrating touch, computer, multimedia, audio, Internet, and LED ambient lighting
- (2)It is widely used in various work and life scenarios, including smart home control centers, smart building intelligent management, smart hotel management, and unattended vending machines, and is deeply loved by customers.
- (3)For home assistant enthusiasts, this device integrates LED ambient lighting and temperature and humidity sensors through MQTT. Eliminate the tedious steps of integration and conveniently use MQTT for remote control.
- (4)It has a stylish and novel design and exquisite appearance, making it a smart home tablet that is deeply loved by consumers.
- (5)Built in KIOSK mode switch, you can easily set KIOSK mode. Please note: when setting KIOSK mode, please set a password, otherwise, you will need to use the type-c interface mouse right-click to exit it. If you have set a password, you can easily exit KIOSK mode by entering it.
In the card configuration, set the image and add elements for your entities. Use entity IDs that exist in your own installation—the examples below are illustrative, not ready-to-paste IDs.
type: picture-elements
image: /local/floorplan/main-floor.png
elements:
- type: state-icon
entity: light.living_room
style:
top: 47%
left: 42%
- type: state-label
entity: sensor.living_room_temperature
style:
top: 55%
left: 62%Home Assistant’s documentation shows the same general approach: place an element with CSS positioning such as top: 47% and left: 42%. Change the image path to one available in your setup, replace the sample entities, and adjust the coordinates until each overlay sits over the right room. The coordinates refer to the image, so a different image or crop may require repositioning.
Rank #2
- 10.1 inch capacitive touch screen, 1280*800P resolution
- Android 14 OS, RK3576 processor, 4GB RAM +64GB ROM,
- Support WIFI 6E / 1000MB Ethernet /BLE 5.3
- Support RJ45 POE power supply
- Support I/O, IR, RS-232, RS485 serial protocol supported
Choose elements for the tasks you want to do
The card supports several built-in element types. Choose a small set that helps people understand or control the home instead of adding an icon for every entity.
- State icon: shows an entity icon and its state, and can expose actions for supported entities.
- State label: displays an entity’s state or value, useful for readings such as temperature.
- State badge: presents an entity as a badge.
- Action button and icon: provide additional ways to invoke actions or show an icon.
- Image: adds an image element; images can change or be filtered according to state.
- Conditional: shows an element when its conditions are met.
- Custom: allows a custom element.
For a practical starting point, put state icons on the rooms where a light needs quick control and state labels only where a live reading adds context. Keep nearby controls separated enough to distinguish and tap. One Home Assistant community participant reported that closely packed icons made their floor plan cluttered and harder to use than a conventional dashboard for sensor data; that is personal experience, not a universal usability result. See the community discussion.
Rank #3
- Powerful Processor: RK3576 8-core processor featuring Quad-core Cortex-A72 and Quad-core Cortex-A53 with a maximum frequency of 2.2 GHz for smooth and responsive performance
- Operating System and Storage: Android 14 OS with 4GB RAM and 64GB ROM providing ample space for smart home applications and multitasking capabilities
- Advanced Network Connectivity: Support for WIFI 6, 100/1000M Ethernet, and BLE 5.3 ensuring fast and reliable wireless and wired connections
- Power over Ethernet Support: RJ45 POE power supply capability simplifies installation by eliminating the need for separate power cables
- Comprehensive Interface Options: Support for I/O, IR, RS232, and RS485 serial protocols enabling integration with various smart home devices and systems
Organize dashboards for more than one floor
Home Assistant’s floor feature is an organizational and targeting aid, not an automatic floor-plan dashboard generator. A floor groups areas that correspond to a physical level of the home; devices and entities are assigned to areas, and areas can then be assigned to floors. Floors can also be used as action targets. See Home Assistant’s Floors documentation.
For a multi-floor home, use consistent area names and consider a separate view or floor-plan card for each level. You still need to choose each image and place its overlays yourself; assigning areas to a floor does not create or position them. The Dashboard views documentation describes the available view layouts.
Rank #4
- 10.1 inch capacitive touch screen, 1280*800P resolution
- Android 14 OS, RK3576 processor, 4GB RAM +64GB ROM,
- Support WIFI 6E / 1000MB Ethernet /BLE 5.3
- Support RJ45 POE power supply
- Support I/O, IR, RS-232, RS485 serial protocol supported
Pick a layout and check it on your screens
Home Assistant documents Sections, Masonry, Panel, and Sidebar view layouts. Panel gives a single card the full width of the view, which can suit a floor-plan card. In a Sections view, the usual card-resizing control does not resize a picture-elements card. See Dashboard cards and Dashboard views.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
After saving, inspect the view on the screens people will actually use. Check that the plan remains legible, overlays land in the right places, and controls are not crowded. If the image is difficult to read at the intended display size, simplify the overlays or choose a clearer image rather than trying to show every device at once.
Best Value
- 【Android OS&RAM+ROM】Android 14 OS, RK3576S 8-core processor, 4GB RAM +64GB ROM，with Proximity Sensor,No Camera
- 【Screen Model】10.1 inch capacitive touch screen, 1280*800P resolution
- 【Network】Support WIFI 6 ,100/1000M, Ethernet /BLE 5.3；
- 【RJ45&POE Supported】Support RJ45 POE power supply
- 【Interfaces】Support I/O, IR, RS232, RS485 serial protocol supported
When an SVG custom-card approach makes sense
An SVG floor-plan card is a separate, optional route—not a different spelling of the built-in picture-elements configuration. A Home Assistant Community example describes storing an SVG under www/floorplan, referencing it with a /local/floorplan/... path, and using a stylesheet with a custom card. That setup requires its own custom resources and configuration; do not paste its YAML into the built-in card as though the two were interchangeable. The example is available in the community thread.
| Consideration | Built-in picture-elements | SVG/custom-card pattern |
|---|---|---|
| Setup and maintenance | Uses Home Assistant’s built-in card and an image plus element configuration. | Requires the chosen custom card and its associated resources; the community example uses an SVG and stylesheet. |
| How state changes appear | Supports state icons, labels, state-based images or filters, and conditional elements. | Depends on the particular custom card and its configuration; the cited example demonstrates an SVG-plus-stylesheet pattern. |
| Styling and animation | Supports the card’s standard image overlays and custom elements; the documentation does not establish a universal animation capability. | Can use the styling mechanisms of the selected custom card; the cited example alone does not establish a universal feature set. |
| Custom-resource dependence | No custom card is needed for the documented built-in workflow. | Depends on custom resources, so their setup and maintenance are part of the choice. |
The available examples do not establish that one approach is universally better. Start with the built-in card when an image and positioned overlays meet the need; consider an SVG/custom-card workflow only if its specific capabilities justify the additional setup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
