There is a typo in the above configuration. In [D-APRS], AX_PEERS should be MAX_PEERS. Other than that, your configuration looks good.

#hblink

No, put in the name(s) of they MASTER or PEER instances where you want private calls to be routed. You'll find these in hblink.cfg, where you define an instance for hotspots to connect to and what hbl

#mmdvm_bridge #hblink

First, be sure you have the latest commit from https://github.com/HBLink-org/hblink3. You shouldn't need to do a PCRewrite if your Pi-Star will only be connecting to your hblink server. In your hblink

#mmdvm_bridge #hblink

I have also set up a demonstration server. See https://demo.hbnet.xyz. Feel free to register and test it out. Let me know if you would like to test the admin side.

If you have any issues, problems, comments, etc., email me directly or use the GitHub repository. Let's keep the mailing list clear for now as this project is still under heavy development and may be

It should be, don't think anything was broken as of last commit. I still have a lot of work to do, including documentation, restructuring of some code, more testing, etc. It will be fully ready in a f

I have been doing extensive work with my fork to make HBLink3 easier to setup, use, and administrate. I've created a web front end to handle hblink configuration, user registration and management, and

A systemd entry may be able to automatically restart it if it stops.

Yes, you would set that up in rules.py.

The Web Admin doesn't rely on any IP stuff from hblink, rather, it just reads/writes the config and rules.py files. You can start it by running: python3 -m http.server --cgi 8090 . This will start the

#hblink

Development update: Over the last month, I have been working on the ability to generate and send SMS from within HBlink. As of last week, it is now possible to generate and send Motorola type SMS mess

#hblink

Sorry for late response. I made a diagram that might help you understand the layout of which config goes to which script.

#hblink

Perhaps the addition of a timeout condition in line 128 could work? I'll play with this idea a little later.

#parrot #closed #hblink #echo #dudestar

This looks similar to a problem that has popped with 2 other servers. For some reason, if the radio sending a position doesn't have an entry in user_settings.txt, the block countdown will go negative

#hblink

For the most part. I am working off of the ETSI 102 361-1 stuff, while looking at the output from my Anytone. It is a long process to go from text string to sequenced and encoded SMS. I am presently a

Looks good. Heads up, after your next update, the dashboard will be configured in the [GPS_DATA] stanza of your config. See gps_data-SAMPLE.cfg for the additional parameters.

#hblink

My work with hblink: https://github.com/kf7eel/hblink3 https://github.com/kf7eel/DMRlink My work with the Openspot 1: https://github.com/kf7eel/shark-py-sms

I wrote some code to do this using an Openspot last year (on github here). Have not worked on it on a long time, currently using my energy to create SMS functionality in HBlink.

I am working on that now. It is incredibly complicated to go from a text string to a formatted DMR SMS sequence encapsulated in an MMDVM packet. It will likely be a while before this is a possibility.

IV3JDV: The passcode for the receive script is pulled from the same value for sending APRS positions. I intended the use of the same callsign for sending and receiving, which would share the same pass

#hblink