so ive been running a remote station for about two years now using a combination of hamachi, some custom scripts, and a flrig/fldigi setup over rdp and honestly its gotten pretty janky. works most of the time but theres always something weird happening with latency or the audio sync falls apart when my upstream bandwidth does anything funny.

a buddy at the club keeps pushing me toward RemoteHams and the SDR remote client and i finally sat down and watched some videos on it last weekend. the SDR remote piece actually looks pretty slick for just listening and monitoring but im not totally sure how it handles actual transmit control — like does it just pass the CAT commands through or is there more going on under the hood there.

also curious if anyone has tried combining this with some kind of internet linking setup, like using it as a gateway into an echolink node or IRLP reflector from the remote end. i have a 2m rig at the remote site too and the idea of being able to key that up remotely and hit a repeater from across the country seems like it should work but im not sure if the audio routing gets complicated when youre also running HF through the same interface.

anyone gone down this road? is RemoteHams actually worth the subscription or is it one of those things that looks better in demos than real life

i ran RemoteHams for probably 18 months before switching back to a custom setup with KiwiSDR and a separate VoIP path. the client is genuinely well done and the latency handling is better than anything ive cobbled together myself, but the subscription thing started bugging me mostly on principle i guess. the SDR remote piece works great for monitoring, i used it to keep an eye on my remote QTH while i was at work and it handled the waterfall display way better than i expected over a mediocre connection.

the transmit side goes through their server infrastructure for the CAT and PTT which some people dont love from a latency standpoint but honestly in practice it was fine for SSB and even reasonably okay for CW if you kept your eye on the buffer settings. never tried chaining it into an echolink node so cant help you there but i dont see why it wouldnt work if you got the audio routing sorted out on the remote machine first, maybe just use a virtual audio cable and route things manually before RemoteHams even sees it

the internet linking question is actually interesting, i did something kinda similar last year. had a pi running at my remote site handling a 70cm link into a local DMR network and separately running the HF remote through a different software stack. keeping them from fighting over the audio hardware was the annoying part, ended up using a cheap USB audio dongle for one and the built in soundcard for the other and that mostly solved it.

if youre already thinking about RemoteHams you might also just look at what SDRangel can do with its remote input plugin, its not quite the same thing and the learning curve is real but it gives you a lot of flexibility for routing audio wherever you want it once you get the hang of it. the echolink integration would probably be cleaner that way since youre in control of all the plumbing