All use cases

Personal

Yeelight → ESPHome with Grok Bot: local lights, no screwdriver

Firewall Xiaomi cloud and stock Yeelights start dropping off Wi-Fi.

Share

What hurt

@__atr__0 wanted six Yeelight ceiling lights fully local in Home Assistant without opening a single fixture. With Grok Bot he probed OTA with a fake update, served real ESPHome images from his Mac one light at a time, backed up HA before each flash, and migrated old entity names so automations/HomeKit kept working. Bedroom light stalled twice on upload — power cycle fixed it. Overnight: zero dropouts offline. Tip only. Not affiliated with xAI.

What to install or create

Probe OTA → backup HA → flash one light → rename entities → cut cloud again.

Bots

  • No new bot. Follow the first-run steps.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/__atr__0/status/2116319106958012462 (credit @__atr__0).
  2. 2Ask Grok Bot to research OTA for your Yeelight model and draft a one-light flash plan.
  3. 3Take a Home Assistant backup; approve a fake-update probe before any real image.
  4. 4Serve the ESPHome image from your Mac one light at a time; power-cycle if an upload stalls.
  5. 5Migrate old entity names to the new devices, then re-block cloud and watch overnight dropouts.

Approval fence

Every flash and network change waits for your go; keep a HA backup before each light.

What to tweak

Steal fake-update probe + one-at-a-time flash + name migration so dashboards survive.

Source

Alessandro @__atr__0 · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro