Skip to content
Open source MPL-2.0Glassworks 0.4.4

The open core for Home Assistant wall panels

One open core handles the dashboard, ESPHome device, setup flow, and updates for any wall panel. Everything else plugs in as a pane—voice, synced music, Zigbee/Thread radios, or features you build yourself.

How it’s built

A frame holds panes, and Kiln installs it

  1. Plugins. Each declares what hardware it needs.

    • Assist
    • Camera
    • Diagnostics
    • Sendspin
    • Timers
    • Bluetooth proxy
    • Notifications
    • Zigbee / Thread radio
    • Frame-specific panes, like the S1 wall base
  2. The stable contract between core and panes.

    • entities()
    • settings()
    • setupSteps()
    • overlays()
    • requires ↔ provides
  3. What every panel needs. No device code.

    • GeckoView dashboard shell
    • Setup flow
    • ESPHome device and entity registry
    • Screen policy
    • Settings menu
    • Updates through HA
  4. One per device. Everything hardware-specific lives here.

    • Board id
    • Update installer
    • Radio backend
    • Presence and light sources
    • Device extras, like relays
    • Screen-off method
  5. Any Android panel. Kiln installs over USB, from the browser.

    • An Android SoC
    • Zigbee / Thread radio (optional)
    • Presence and light sensors
    • Microphone and speaker
    • Relays, wall base and other extras
  6. The installer. Fires a stock device into a panel, over USB, from the browser.

    • Connects over USB, in the browser
    • Backs the device up first
    • Roots it, where the frame needs root
    • Flashes the frame and core
    • Provisions Wi-Fi and Home Assistant

Supporting a new panel means writing a new frame. The Aqara S1 Plus is one, with the radio and wall-base panes.

Aqara S1 Plus · a made-up home
USBRootFlashProvisionKILN · INSTALLS OVER USB, FROM THE BROWSERMicrophoneSoCRadio chipPresenceDevice I/OSpeakerHARDWARE · ANY ANDROID PANELBoard idInstallerRadio backendPresenceDevice I/OScreen offFRAME · ONE PER DEVICEShellSetupDeviceScreenSettingsUpdateGLASSWORKS COREPANE APIAssistTimersRadioDiagnosticsDevice paneSendspinPANESZHA · Z2M · OTBRRadio over TCP, firewalledMusic AssistantSynced audio over SendspinHome AssistantESPHome device · dashboard · updates

Standalone MIT libraries

All library docs ›
esphome-apiThe device side of the ESPHome native API, in Kotlin.API 0.1.1MITesphome-api-androidAndroid helpers for esphome-api: mDNS discovery.API 0.1.0MITimprovImprov Wi-Fi for Android, over BLE, serial or adb.API 0.1.0MITbluetooth-proxyAn ESPHome Bluetooth proxy on Android.MITsendspinA Sendspin synced-audio player for Android.MITvoiceWake words and Home Assistant Assist on Android.MITimprov-serialImprov Wi-Fi Serial for the browser, and over adb.MITha-authHome Assistant sign-in and tokens.MITsendspin-protocolThe Sendspin synced-audio protocol.MITfastbootFastboot over WebUSB, for every frame Kiln installs.MITframe-cardThe frame card and 3D renderer, for Kiln and the site.MIT

Why MPL-2.0

Glassworks stays open while your product stays yours.
Port itWrite a frame for any Android wall panel, smart mirror, or tablet.
Ship your own hardwareBundle Glassworks on hardware you sell. Your custom frames and panes can stay closed.
Share core fixes backImprovements to Glassworks core files stay open so every supported device gets better.

Build with Glassworks

GitHub ›
Adding a deviceDefine hardware capabilities, install recipes, and frame bindings for a new panel.Pane APIThe stable contract for ESPHome entities, setup steps, settings, and overlays.The frame agentHow privileged hardware actions run cleanly and safely on rooted panels.Open hardware researchTeardowns, boot chains, radio logs, and bring-up notes published from the repo.Project principlesWhy Home Assistant stays the brain, ESPHome stays the wire, and nothing installs in HA.
↑↓ to move↵ to open