https://github.com/n1kdo/dmr-listener
scripts to collect and process DMR usage data from CBridge and Brandmeister
https://github.com/n1kdo/dmr-listener
amateur-radio amateur-radio-repeaters brandmeister cbridge dmr hamradio
Last synced: 6 months ago
JSON representation
scripts to collect and process DMR usage data from CBridge and Brandmeister
- Host: GitHub
- URL: https://github.com/n1kdo/dmr-listener
- Owner: n1kdo
- License: bsd-2-clause
- Created: 2020-05-02T20:36:57.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2025-02-17T13:51:31.000Z (8 months ago)
- Last Synced: 2025-03-26T08:05:34.740Z (7 months ago)
- Topics: amateur-radio, amateur-radio-repeaters, brandmeister, cbridge, dmr, hamradio
- Language: Python
- Homepage:
- Size: 991 KB
- Stars: 3
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# DMR-listener
DMR listener is a tool that scrapes the "call watch" web service of a C-Bridge, listens to MQTT
data brom Brandmeister and collects information about the usage.
I started collecting data because of the limited size of the talkgroup dictionary on my XPR radios,
I wanted to find the top users to program by hand with CPS.
Once I started collecting data, I saw that I could extract a lot more useful intelligence from it.
That's when I added the HTML reports and graphs. This tool grew by accident.
There is data generated:
* usage by talkgroup by repeater
* usage by user by repeater by talkgroup
* talkgroup activity plotted over time
* exported contacts list in N0GSG and MotoContacts formats
* A web page with selected Georgia Repeaters and Talk Groups. This comes partially from static
data, but is verified nightly against the collected usage data. By using the last heard data,
a user can figure out what talkgroups are working where. The static data is still maintained
by hand by me based on reading log data from the nightly jobs. This is suboptimal.
* Web reports for repeater and user usage, live at https://www.n1kdo.com/dmr_data
This is perhaps the fourth generation of this, the current version uses `async_lister.py`
to listen to Brandmeister and HamDigital cbridge to try to collect useful information from
Brandmeister and a limited view of CBridge traffic from HamDigital.
There is some load on the servers generated by the data collection process. This is
about the same or less as a user leaving a dashboard open.
