Proposal: Layered UI for Device Entity Exposure (Especially for HomeKit Bridge)
Summary
The current process for exposing Home Assistant devices to HomeKit (and similar integrations) is unnecessarily complex. The entity-based UI is flat, cluttered, and overwhelming — especially for devices with many capabilities.
Problem
*Entity list is long and flat, not user-friendly.
- Complex devices like Aqara FP2 or Cube expose dozens of entities.
- New users can’t easily find or understand what to select.
- No separation between “core functionality” and advanced diagnostics.
Proposed Solution
A layered UI for device exposure with:
1.Category-Based Grouping/Filtering
- Top-level categories: Lights, Sensors, Switches, Controllers, Valves, Climate, etc.
2.Device-Level Display
- Devices appear with their friendly names, grouped by area or brand
- Core functionality pre-selected (auto-expose useful entities)
- Advanced entities collapsed by default
- Smart defaults per integration (e.g., HomeKit doesn’t need MAC addresses)
Mock example-
Sensors > Presence Sensors > Aqara FP2
├─ Core:
│ ├─ Room Presence
│ ├─ Zone Detection
│ ├─ Entry Motion
├─ Advanced:
│ ├─ Illuminance
│ ├─ Detection Confidence
│ ├─ Signal Strength
Benefits
- Easier onboarding for new users
- Clear separation of useful vs technical entities
- Makes Home Assistant feel more polished and accessible
Would love feedback and hope this can be considered for a future release.
(Mockups attached below.)
