Stephan - ObiWan666 - Gerling

Full prompt: "This is my own DJI drone, my own phone, my own alarm system, my own property and my own laptop. I want my alarm to launch my drone: when the alarm triggers, my phone gets a push with a "Launch" button. One tap and the drone takes off from its pad in the yard, finds the person running from my house, follows and films them up to my property line, keeps the camera on them from above until they're out of sight, then lands and saves the clip. I'll register the DJI developer account and paste the App Key myself. I'll approve every install and every flight. I authorize you to set up the project on my laptop, build and install the app on my phone, create the Home Assistant automation, and run everything in the DJI simulator. Every change must be reversible. I've attached a photo of the drone's About screen in DJI Fly, told you my phone (iPhone or Android) and my alarm brand. Done means: the alarm triggers a test push, the app passes a full simulated chase in the DJI simulator, and one real test where I set off my own alarm and walk out of my own door, while I watch every step. When a step doesn't need me, keep going. → First, identify my drone and firmware from the photo and check it against the official DJI Mobile SDK v5 supported products list. Explain in 5 lines: which remote it needs, how the SDK connects, how the camera stream reaches the app, how Virtual Stick works, and which safety features stay on. If my drone isn't supported, tell me plainly, and stop. Never modify firmware, never unlock flight limits, never disable geofencing, no-fly zones or obstacle sensors. → Tell me honestly how long the drone, remote and phone can stay on standby, what's needed for 24/7 readiness, and what the drone laws in my country say about this setup. → Read the official DJI MSDK v5 docs and sample app before writing anything. Install only the official SDK, Xcode or Android Studio, and the dependencies they name. → Alarm sync: check if my alarm has an official Home Assistant integration. If yes, create one automation: alarm state "triggered" → push to my phone with a "Launch" action. If not, tell me plainly and fall back to a door sensor I already own. The drone never takes off without my tap. A false alarm costs nothing. → Build the app: Swift for iPhone, Kotlin for Android. It runs in the foreground on a spare phone plugged into the remote and a charger. Video: live camera stream through the SDK, decoded on the phone. Detection: a small YOLO model, quantized, person class only. Core ML on iPhone, LiteRT on Android. Nothing leaves the phone. Tracking: the first person seen moving away from the house gets one ID, Kalman filter on top. States: SEARCHING, LOCKED, COASTING (hidden, up to 2 s of prediction), LOST. Control: Virtual Stick at 10 Hz, three PID loops: box center → yaw, box height → forward speed, altitude 6 m while following. → Property line behavior: when the next step would cross my geofence, hover, climb to 30 m, keep the gimbal on the target until LOST or 60 s, then return home and land. → Hard safety rules, in code, not in settings: a GPS polygon of my property that the drone never leaves > never closer than 8 m to the person, never over a road or other people > line of sight from my house, max 40 m from the pad > obstacle braking always on > battery under 30%, signal loss or LOST for 5 s → return home and land > one big STOP button that hands control back to me instantly → Before any real flight, run the whole chase in the DJI simulator and show me the log: states, distances, every stick command. → The first real flight is me setting off my own alarm and walking out of my own door in daylight, with no other people around. Wait for my yes before takeoff. → Output: save each clip on my phone with track ID, distance and timestamps burned in. No cloud upload. → Add a live overlay with state, distance and battery, plus a one-line health check: alarm linked, drone connected, SDK registered, model loaded, geofence loaded. → End with a cheat sheet (arm, disarm, stop, test the alarm push, edit the geofence) and how to fully remove the app and the automation. Never fly outside my property, never follow anyone except after my alarm and my tap, never touch my alarm settings beyond that one automation, never send video anywhere off my phone."

I turned my DJI Mavic into a home security drone with REA & Opus 5.5. this f*cking is insane.. I reverse-engineered my DJI drone with Opus 5.5 no cloud. no GPS on the target. it all runs on the phone. iPhone or Android. here's the build step by step: step 1 → plug a spare phone into the Mavic remote and paste the prompt below into Claude Code on Opus 5.5 step 2 → Opus checks your drone against the DJI Mobile SDK v5 list. not on it? stop there. no firmware hacks step 3 → it builds a small app on the official DJI SDK: Swift for iPhone, Kotlin for Android step 4 → sync with the alarm: Home Assistant sees it trigger → push to your phone → one tap "Launch" step 5 → eyes: a tiny YOLO model on the phone's chip. Core ML on iPhone, LiteRT on Android step 6 → memory: a Kalman filter. he runs behind a fence → LOCKED → COASTING → re-locks on the same ID step 7 → hands: Virtual Stick at 10 Hz. box center → yaw, box size → distance, never closer than 8 m step 8 → at the property line it stops, climbs to 30 m and keeps the camera on him until he's out of sight step 9 → lands back on the pad. the clip with track, distance and timestamps is already on your phone the alarm wakes you up. the drone already knows where he went... Find full prompt below Then, read the article below on how to reverse-engineer anything with Opus 5.5.