luotwo

Light RID Scanner — Productivity skill for Claude Code

Productivity community

Open-source Remote ID & OpenDroneID Wi-Fi scanner for drone detection and tracking on Raspberry Pi.

How to install Light RID Scanner

This entry records only its repository, not the path inside it, so there is no exact command to give. Open luotwo/Light_RID_Scanner and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Light RID Scanner does

Open-source Remote ID & OpenDroneID Wi-Fi scanner for drone detection and tracking on Raspberry Pi. Supports DJI drone monitoring, real-time map dashboard, WeCom alerts, and multi-station aggregation. Built with CodeX & Claude Code.

Alternatives in Productivity

Getting Help — career-ops is an open source project maintained in limited time 32.5k ★
Om Correct — Sweep a corrected fact through the vault — finds every note restating it, applies the correction at the single 4.6k ★
Nosqli — NoSQL injection scanner (MongoDB/Mongoose/operator-injection DBs) — auth bypass via $ne/$gt operators, bracket 4.5k ★

README

Light RID Scanner

[English](README.md) | [简体中文](README.zh-CN.md)

Light RID Scanner is a fixed-station Remote ID (ASTM F3411 / OpenDroneID) Wi-Fi monitor built for Raspberry Pi and other Linux-based capture nodes. It passively listens for drone Remote ID broadcasts over Wi-Fi, decodes them in real time, and presents the results through a local web dashboard.

It also includes a portable edition for mobile deployments and a node-center viewer that aggregates multiple stations into a single pane of glass.

station_edition/ Full fixed-station build. It contains the source runtime, web UI, security/auth controls, systemd/AP maintenance, and Raspberry Pi deployment defaults.
portable_edition/ WIP (Work in Progress). The portable runtime code has been removed while the product policy is being revised; the directory currently contains only a WIP README.
Root run.py Compatibility wrapper for station_edition/run.py.
Root rid_model.json Public GitHub Raw model map. Binaries also embed this file and restore it if runtime download fails.

The station edition is meant to be usable from its own directory. Runtime files such as `config.json`, `rid_storage.db`, and `rid_model.json` are resolved relative to the current working directory unless explicit paths are passed. Older `history-cache.json` / `rid_history_cache.json` files are treated as legacy migration sources.