YOUR LAB. AT A GLANCE. Open source · No subscription · Assembled in Bulgaria

ONE COLLECTOR. ONE ADDRESS.

Bring your devices
into one view.

The collector owns the node registry. Its browser interface and API run on the same local server. Glimdock pairs once and receives the active nodes from it.

Current setup uses the development sourceBuild the central collector from codex/central-host-agnostic using the build guide. Published v0.1.0 binaries do not include this integrated server.
  1. 1

    Start the central collector

    Choose an always-available Linux or macOS machine with network access to your devices. Build the Rust collector and start it with glimdock-collector run --state-dir ./glimdock-state --bind 127.0.0.1 --port 8765. On that machine, open http://127.0.0.1:8765/; local access works directly. For LAN access, bind to the collector’s real LAN address and use the generated display key for readings and management key for node settings. You can include the collector host as a generic node or omit it.

    Commands, services and token setup
  2. 2

    Set up device feeds

    Run the Rust native agent on each Windows, macOS or Linux device you want to monitor. For routers and other equipment, configure an SNMP or JSON API agent with the values its platform exposes. A Proxmox collector feed can add guests, storage and hardware probes. Klipper connects through Moonraker.

    Native, SNMP and JSON API examples
  3. 3

    Register nodes in the web interface

    Open Nodes, choose Add node, then enter the feed URL, name, type and any required key. Set the platform or let the feed identify it. Adjust polling, pause or resume a feed, and remove nodes you no longer need. The registry keeps stable IDs. Four nodes can be active at once; up to sixteen remote feeds can remain configured.

    Nodes are registered explicitly. The collector does not automatically scan your LAN or install agents on other devices.

  4. 4

    Pair Glimdock once

    Connect USB-C power, join your 2.4 GHz Wi-Fi and save the collector snapshot address and display key in the display’s connection settings. Use the configuration key too if you want to manage nodes from its touchscreen. The address is http://COLLECTOR:8765/api/v1/snapshot; localhost on Glimdock would refer to the display itself.

    The display receives its node list from the collector. Start on All nodes for summary bento cards, then tap a node for its detailed pages.

Use the browser as a display too.

Open Display & firmware in the collector. Its emulator runs the production firmware interface with your live nodes, at the same 320 × 240 resolution. Click or touch the canvas to navigate. The public website demo uses synthetic readings and cannot change your collector settings.

Update the firmware over USB.

  1. 1

    Open a supported browser

    Use Chrome or Edge on your computer. Web Serial requires HTTPS or localhost. If your collector is on another machine over HTTP, use the documented localhost companion to reach it securely from your computer.

  2. 2

    Connect the supported board

    Connect the Waveshare ESP32-S3-Touch-LCD-2.8 V1 with a USB data cable. Close any serial monitor holding the port. V2 firmware is not supported by this image set.

  3. 3

    Choose the port and install

    In Display & firmware, choose the USB update action and select the board’s serial port. The updater verifies the board and image hashes before writing and checks the programmed data afterwards. Saved Wi-Fi and collector pairing remain in their own flash partition.

Physical case validation is still in progress

The current Pebble case uses an internal USB extension whose fit and data path have not yet been confirmed on an assembled unit. It has no external boot/reset opening. Validate your board and extension before final assembly; use the directly accessible board port for the verified development setup.

Choose the readings your devices expose.

Native OS values, hardware sensors, network interfaces and platform-specific APIs are all useful sources. A temperature or GPU reading may require device-specific support and permissions. The collector and display keep missing values unavailable and label stale data rather than inventing it.

Monitoring has no cloud account or subscription. Configuration keys grant access to node settings, so keep them private and keep the collector on your trusted network.

Read the complete setup guide