- Python 100%
|
|
||
|---|---|---|
| config | ||
| docs | ||
| scripts | ||
| src/rgb_aura | ||
| systemd/user | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| LICENSE | ||
| pyproject.toml | ||
| README.md | ||
RGB Aura
Northern-light RGB animation controller using OpenRGB SDK.
RGB Aura drives selected OpenRGB zones with a dark-blue base color and slow green aurora-style movement. It is designed for a specific local hardware layout, with runtime guardrails to avoid writing to unexpected devices or reserved zones.
Current documentation
Hardware assumptions
RGB Aura currently assumes the validated OpenRGB device mapping in config/device_map.json.
The active RGB Aura zones are:
- GPU
- Motherboard
- Top Fractal fans
- Thermaltake/front fans
The reserved ARGB zone must remain untouched.
Requirements
- Python 3.11 or newer
- OpenRGB with the SDK server enabled
- OpenRGB SDK server reachable at
127.0.0.1:6742 - Python virtual environment created in the project directory
- Project dependencies installed from
pyproject.toml
Basic manual run
From the project directory:
source .venv/bin/activate
python -m rgb_aura.main --animation-speed 1.25 --leave-dark-blue
Stop with Ctrl+C.
When possible, RGB Aura restores the active controlled zones to dark blue during clean shutdown.
Dry-run preview
Dry-run mode previews scheduler behavior without connecting to OpenRGB and without writing RGB values:
python -m rgb_aura.main --dry-run
Runtime configuration
Runtime settings are stored in config/runtime_config.json.
Static OpenRGB hardware mapping remains separate in config/device_map.json.
Optional systemd user service
RGB Aura can optionally be installed as a systemd user service.
The service is not installed automatically. See docs/systemd-user-service.md.
Safety notes
RGB Aura validates runtime values, runtime configuration, and OpenRGB device mapping before normal animation writes.
For known safe failure behavior and exit codes, see docs/safe-failure-modes.md.