Rewire a battery light-up ghost to USB-C and an ESP32 for Home Assistant alerts, with Claude
- Posted
- by nabossha (@nabossha)
- Last checked
- Method:
- How we verify
Evidence: Described by posterThe person describes what happened in words, without screenshots or video.
Outcome
nabossha's spouse had ordered a sketchy light-up gadget online. Claude helped nabossha gut it: the batteries and on/off switch came out, and USB-C power and an ESP32 went in. It's now hooked into Home Assistant and changes its light show when the doorbell rings, a parcel arrives or someone passes by, in time for Halloween. The attached video shows the gadget, a ghost figure, lit up by a door.
AI tool
Prompt Recreated prompt
The source didn't share its exact prompt, so we wrote this from what it describes.
Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points. Goal: Convert a cheap battery-powered light gadget to USB power with a small Wi-Fi board, so my smart home can control its lights. What I can give you (ask for whatever's missing): - Photos of the gadget, inside and out, and its LEDs or circuit board: [PHOTOS] - The board and smart home system I want to use (e.g. ESP32, Home Assistant): [BOARD AND SYSTEM] - Which events should change the lights: [EVENTS] Rules: - Start by identifying the LEDs and their voltage from my photos, and tell me if they can run safely from USB 5V or the board's pins. - Give a wiring diagram and parts list, and say where a resistor or transistor is needed. - Warn me before any step that could damage the board or make the gadget unsafe (heat, short circuits, battery leftovers). - Write the firmware config and one automation per event, and explain how to test each one. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A parts list, wiring steps, the firmware config and the automations. You'll know it worked when: the gadget runs from USB and its lights change when each event happens.
Customize this prompt
Answer the questions below and we'll put your answers into the prompt for you. You can leave any of them empty.
Photos of the gadget, inside and out, and its LEDs or circuit board
You'll attach this in the chat tool, not here. Add the file in the chat before you send the prompt.
Your prompt
Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points. Goal: Convert a cheap battery-powered light gadget to USB power with a small Wi-Fi board, so my smart home can control its lights. What I can give you (ask for whatever's missing): - Photos of the gadget, inside and out, and its LEDs or circuit board: [PHOTOS] - The board and smart home system I want to use (e.g. ESP32, Home Assistant): [BOARD AND SYSTEM] - Which events should change the lights: [EVENTS] Rules: - Start by identifying the LEDs and their voltage from my photos, and tell me if they can run safely from USB 5V or the board's pins. - Give a wiring diagram and parts list, and say where a resistor or transistor is needed. - Warn me before any step that could damage the board or make the gadget unsafe (heat, short circuits, battery leftovers). - Write the firmware config and one automation per event, and explain how to test each one. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A parts list, wiring steps, the firmware config and the automations. You'll know it worked when: the gadget runs from USB and its lights change when each event happens.
Scroll to see the whole prompt. Your answers show in green.
2 blanks are still empty: The board and smart home system I want to use (e.g. ESP32, Home Assistant); Which events should change the lights. They'll stay in brackets in your prompt, so the chat tool may ask you about them.
What you type stays in this browser tab. We don't send it or save it, and it's gone when you leave the page. If you use a "Try this in" button, your answers go to that tool as part of the prompt.
Try this in:
This prompt has blanks to fill in, like [PHOTOS]. We'll copy it instead of filling it in, so you can edit it before you send.
The source used Claude. These are general chat tools, so results may differ.
Opens in a new tab. We don't see what you send.
These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.
Optional stronger version
Our rewrite with extra checks. The poster didn't test it.
Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points. Goal: Convert a cheap battery-powered light gadget to USB power with a small Wi-Fi board, so my smart home can control its lights. What I can give you (ask for whatever's missing): - Photos of the gadget, inside and out, and its LEDs or circuit board: [PHOTOS] - The board and smart home system I want to use (e.g. ESP32, Home Assistant): [BOARD AND SYSTEM] - Which events should change the lights: [EVENTS] Rules: - Start by identifying the LEDs and their voltage from my photos, and tell me if they can run safely from USB 5V or the board's pins. - Give a wiring diagram and parts list, and say where a resistor or transistor is needed. - Warn me before any step that could damage the board or make the gadget unsafe (heat, short circuits, battery leftovers). - Write the firmware config and one automation per event, and explain how to test each one. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. - Add a fallback so the lights show something sensible if Wi-Fi or the smart home server goes down. Output: A parts list, wiring steps, the firmware config and the automations. You'll know it worked when: the gadget runs from USB and its lights change when each event happens. Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.
Source
https://x.com/nabossha/status/2111576614756630994
Related cases
- Turn a spare ESP32 box into a baby monitor that only wakes parents after 10 minutes of fussing, built with ClaudeRecreated promptEvidence: Described by poster
pugio and their spouse were sleep-training their baby, who wakes a few times a night and either babbles back to sleep or fusses for 10 minutes before a parent needs to go in. With a spare esp32-box-3 and a few rounds with Claude, they built a baby monitor that tracks how long the baby cries or fusses, streams audio only after 10 minutes, and sends notifications at 30 seconds and at 10 minutes. The log shows the baby often wakes 1–2 times a night and resettles almost immediately, and the parents only wake when the audio comes through. During the day it tells them when naps end.
Claude · Personal · Source date:
- Make a DIY patio project checklist in Google Keep with GeminiImproved promptEvidence: Article or interviewBeginner-friendly
An Android Police writer describes using Gemini in Google Keep for planning: asking it for a checklist for a DIY paver patio project, including prep materials and safety gear, gave them a 15-point list within three seconds that they say would have taken 20 minutes of searching. They edit the lists rather than using them as-is.
Gemini · Personal · Source date:
- Audit a Proxmox home lab with Claude and find skipped backups, stale IPv6 settings and a stuck updateRecreated promptEvidence: Article or interview
Adam Davidson gave Claude access to two Proxmox machines in a home lab and asked it to look for problems without changing anything. Writing for How-To Geek, Davidson says Claude found three overlooked problems. The backup job only covered services Davidson had picked by hand, so newly added services were being skipped; the fix was to back up everything by default and exclude what isn't needed. The ISP had changed the IPv6 prefix, so a few services still pointed at a Pi-hole IPv6 address that no longer existed, which was why a Jellyfin list plugin had been silently failing. And on the OptiPlex running Proxmox, the enterprise repository was off with no free repository turned on, so it was stuck on 9.1.1; it has since been updated.
Claude · Personal · Source date: