forum.pistar.uk

Another option is to use the normal config page and turn callsign routing off, apply that, and then turn it back on and apply that.

This will also swap the hosts over for you

Jason, I have not followed up regarding the openquad.net as you have suggested, I had thought that part of the problem may have been with the DExtra Host files, which at this time does not seem to be the solution?? As far as I understand the hotspot to hotspot callsign routing is handled exclusivel...

Ben, Do you have "Use DPlus for XRF:" enabled on the config page? This will do exactly what you are seeing, the idea here is that old XRF / DExtra hosts actually required a port forward on your local router to work correctly. XLX hosts that use the XRF protocol don't require that - but the...

It's still possible to do it, I've build some shell command lines for this, but it's overkill in anyway, and still won't work when you have few enabled networks, as entries are mixed, so a connection can hide a disconnected network. Interesting point, but connected networks stop logging that they a...

I was adding the repeater IDs from RadioID.net to the Pi-Star DMRIds.dat output, but this has been causing more confusion than its worth.

After a couple of requests, those are no longer included in the output, that should stop the unusual output in the "Target" column of the dashboard.

I have a couple of duplex boards by VR2VYE/BI7JTA. One of them is on my DMR hotspot, and BM went missing today. Shows "off" in Self Care. Then I read about BM protecting themselves from "misconfigured" hot spots by requiring all of them to use the same TX and RX frequencies. Thi...

just one word - stability, we do update them from time to time, but if I manage to push an update and the system doesn't add the extra stuff to your config files, oh boy do I hear about it. It wont be long before new MMDVMHost and DMRGateway binaries are coming. Out of interest Andy, do you have a ...

I'm going to say I don't *think* I can do that, MMDVMHost does not exactly have a status output, so there would be some guesswork, but, I like the idea.

Might take me a few days, but I'll see what I can come up with.

I added a fix for this yesterday morning, you might have just missed it, update, head to the config page, press apply with no changes, should now be working fine.

Not surprised, its not built for that board