AA Belt Radar module for AllianceAuth.
A Belt Survey Analyser to track how fast you mine your belt.
Features
- Interactive Live Sessions & Mining Analytics
- Dynamic live session updates: new survey scans and mining data are automatically loaded and immediately visible
- Real-time mining speed tracking in m³/s
- Estimated completion time (ETA) for belt mining
- Remaining volume and belt size calculation
- Compressed ore price estimation
- Visual Analytics & Diagrams
- Ore Progression: Visual chart tracking the progress and composition of mined ore
- Mining Speed & Volume Chart: XY line & column diagram displaying remaining volume (m³) alongside mining speed (m³/s) over time
- Belt Automation & Timers
- Automatic belt type and size detection
- Automatic respawn timer creation when only 10% of the belt volume is left
- Public and private belt respawn timers
- Collaboration & Notifications
- Optional session sharing with fleet members or corporation
- Configurable Discord webhook notifications for belt respawn timers
Highlights
Installation
Step 1 - Install the Package
Make sure you're in your virtual environment (venv) of your Alliance Auth then install the pakage.
pip install aa-beltradar
Step 2 - Configure Alliance Auth
Configure your Alliance Auth settings (local.py) as follows:
INSTALLED_APPS = [
# other apps
"eve_sde", # only if it not already existing
"beltradar",
# other apps?
]
# This line is right below the `INSTALLED_APPS` list, if not already exist!
INSTALLED_APPS = ["modeltranslation"] + INSTALLED_APPS
Step 3 - Add the Scheduled Tasks
To set up the Scheduled Tasks add following code to your local.py
CELERYBEAT_SCHEDULE["AA Belt Radar :: Update Belt Radar"] = {
"task": "beltradar.tasks.update_all_belt_radar",
"schedule": 600,
}
CELERYBEAT_SCHEDULE["AA Belt Radar :: Update Market Price"] = {
"task": "beltradar.tasks.update_market_prices",
"schedule": 86400,
}
Step 3.1 - (Optional) Add own Logger File
To set up the Logger add following code to your local.py
Ensure that you have writing permission in logs folder.
LOGGING["handlers"]["beltradar_file"] = {
"level": "INFO",
"class": "logging.handlers.RotatingFileHandler",
"filename": os.path.join(BASE_DIR, "log/beltradar.log"),
"formatter": "verbose",
"maxBytes": 1024 * 1024 * 5,
"backupCount": 5,
}
LOGGING["loggers"]["extensions.beltradar"] = {
"handlers": ["beltradar_file"],
"level": "DEBUG",
}
Step 4 - Migrate & Preload EVE SDE Data
AA Skillfarm uses EVE SDE data to map IDs to names for EveTypes. You will need to preload some data from SDE once.
python manage.py migrate eve_sde
python manage.py esde_load_sde
Step 4.1 - Migrate App and collect static
Migrate the app and collect static.
python manage.py migrate beltradar
python manage.py aabeltradar_migrate_market_data
python manage.py collectstatic --noinput
Step 5 - Setting up Permissions
With the Following IDs you can set up the permissions for the Belt Radar
| ID | Description | |
|---|---|---|
basic_access |
Can access the Belt Radar module | All Members with the Permission can access the Belt Radar. |
manage_access |
Can Manage Belt Radar module | Can manage Application |
admin_access |
Has access to all Survey Sessions | Can see all Survey Sessions |
Step 6 - (Optional) Setting up Compatibilies
The Following Settings can be setting up in the local.py
| Setting Name | Descriptioon | Default |
|---|---|---|
BELT_RADAR_APP_NAME |
Set the name of the APP | "Belt Radar" |
BELT_RADAR_TASK_TIME_LIMIT |
Defines the time (in seconds) a task will timeout | 1200 |
BELT_RADAR_WEBHOOK_URL |
Defines URL for Webhook notification | None |
Translations
Help us translate this app into your language or improve existing translations. Join our team!"
Contributing
You want to improve the project? Please ensure you read the Contribution Guidelines
Metadata
Release files for aa-beltradar 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aa_beltradar-2.0.0.tar.gz | 1.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aa_beltradar-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 MB
Release files / aa_beltradar-2.0.0.tar.gz
| Download URL | aa_beltradar-2.0.0.tar.gz |
|---|---|
| Size | 1.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77cabb9ea9f0486ef772e601fd102ad1e3cf44f259931a0d7c71f52873a8b848
|
|
BLAKE2b-256 checksum How to use checksums |
4f56a8fba889430d61e40e1859c220633070ece23c81b7c3b0d91e15d099775b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / aa_beltradar-2.0.0-py3-none-any.whl
| Download URL | aa_beltradar-2.0.0-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82658130597e5230e3d09b9517b3616e0173ddbd47109ae88218d2b4e4742b80
|
|
BLAKE2b-256 checksum How to use checksums |
f986537143883c7e88a527c06e1648f89e62ee321a9d2b3bb7d930ffef0e96ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log