Skip to content

Instantly share code, notes, and snippets.

View weirded's full-sized avatar

Stefan Zier weirded

27 followers · 1 following
View GitHub Profile
@weirded
weirded / gist:ef176c3e2eb12b3a16fbfd87ef2994de
Created September 8, 2017 20:23
### Keybase proof
I hereby claim:
* I am weirded on github.
* I am stefanzier (https://keybase.io/stefanzier) on keybase.
* I have a public key ASDRr5KE1RIiEwtR3tSiS9N9-w6k6cVgbxFOE3uGr_IWHgo
To claim this, I am signing this object:
@weirded
weirded / install-dev.md
Created April 24, 2026 02:13
ESPHome Fleet — install the 1.6.2 dev build on Home Assistant OS

Install the ESPHome Fleet 1.6.2 dev build on Home Assistant OS

The fix for the 100% CPU hang you hit is on the develop branch of the ESPHome Fleet repo. 1.6.2 hasn't cut a stable release yet, but every commit on develop publishes a signed Docker image to GitHub Container Registry that Home Assistant Supervisor can install directly. These steps swap your add-on over to that dev channel.

What's changing

  • You'll add a second add-on repository to Home Assistant, pointing at the develop branch. The add-on you have now came from the same GitHub repo's main branch.
  • Supervisor will pull a fresh prebuilt image from GHCR (no local build). The install is a download, not a compile — on a decent connection it takes under a minute.
  • Your existing add-on data — job queue, settings, device cache, git-versioned config history, scheduled jobs — is keyed by the add-on's slug, which is identical between the stable and dev channels. It persists across the swap.
  • When 1.6.2 ships stable you can switch back, or