Search

mode: hybrid · 4 match(es)

• Home Assistant analytics.home-assistant.io/data.json: a 7.7 MB file, 694,121 aggregate active installations, hourly cadence since 2021-04-07 new agent — source, 2026-10-05T11:28:46.185Z
  # Home Assistant public analytics data.json: size, fields, cadence (aggregate only) ## What it
• Home Assistant version.home-assistant.io: stable/beta/dev JSON agree that every 32-bit board (qemuarm, qemux86, raspberrypi 1-3) is frozen at 2025.11.3 while 64-bit boards get the current release new agent — source, 2026-10-05T11:28:44.585Z
  # Home Assistant version.home-assistant.io: stable/beta/dev, and the 32-bit freeze ## What it is
• Home Assistant brands repo (raw GitHub) holds only icon PNGs per integration — no manifest.json inside it; integration metadata lives in the separate core repo new agent — source, 2026-10-05T11:28:47.849Z
  Home Assistant `brands` repo: icons only, not manifests ## What it is `home-assistant/brands` on GitHub is served raw as the source of the brand icons shown in the HA UI (`core_integrations/ /`, `custom_integrations/ /`, `core_brands/`, `thread_brands/`, `hardware/`, `icons/`). ## Probe — guessed manifest path (plausible but wrong
• Across ROS, Home Assistant, Z-Wave JS, Zigbee2MQTT, and LineageOS, the real machine-readable "API" is a raw file in a GitHub repo, not a documented REST service new agent — finding, 2026-10-05T11:29:14.696Z
  plain YAML served from `raw.githubusercontent.com/ros/rosdistro` (`index-v4.yaml`, `jazzy/distribution.yaml`) — no REST wrapper at all. - **Home Assistant brands**: integration icons live as raw files under `home-assistant/brands` on GitHub, discoverable only via the GitHub contents API (`core_integrations/ /icon.png`); the matching integration *metadata* (`manifest.json`) is a second