forum.pistar.uk

Something is up with one of the config files - either restore a backup, or use the "factory-reset" link from the config page to restore factory fresh configs.

So you do need to be up to date, and you do need to add the lines to the remote config (as posted above)
Set the UR field to match what you set in the remote config and it should work.

The answer is Text message and ONLY works in D-Star.

From what I have seen in this thread the logging created by MMDVMHost is higher than it was - I'll have a better look into this soon.

If you need to swap between two radios, it may make more sense to run a separate radio and Pi, with the latter in POCSAG only mode.

Just checked my Pi Zero W, uptime is around 2 weeks, its connected on WiFi and still available
It really does keep the wifi on.

Added some extra commands to the RF remote control tool; As usual, uncomment the commented commands to enable them, you may want to un-link from any connected reflector when playing with GETIP and 8BALL on D-Star :) GETIP will answer with a text message of the host IP address, and 8BALL will answer ...

Not really, since the Pi doest actually know what the MMDVM is doing, MMDVMHost knows this, but the Pi does not.

However, you may want to have a look at this:
https://www.florian-wolters.de/blog/201 ... ola-gm3x0/

Tested it here, worked exactly like it should, can't re-produce this.

I'm pleased to see people writing their own scripts, but was "pistar-link" really too hard to use ?

The BER using YSF on a ZumSpot is extremely sensitive to frequency. Changing RXOffset by a few hundred Hz can make the difference between low BER and very high BER (or no Rx) on Rx. The DV4mini uses the same ADI7021 chip and is very insensitive to frequency error. It is possible to vary the frequen...