Clayton Smith

I suspect https://github.com/urlgrey/hsmm-pi/issues/32 and https://github.com/urlgrey/hsmm-pi/issues/80 are both BeagleBone installation issues arising from a bug in Ubuntu 14.04's version of pear.

Service protocol name is whatever protocol your service is accessed by, probably `http`. Port is the port number that the Raspberry Pi will forward to your service. Normally that can...

By the way, the "service protocol name" only affects the URL that is announced on the mesh.

Try these settings: - Service Protocol Name: mumble - Host: IP address that the Raspberry Pi assigns to the machine running your mumble server; it should be something like 172.27.2.5...

And of course, be sure to reboot the Raspberry Pi after applying the settings above.

Thanks for this! Unfortunately I'll be quite busy for the next two weeks, so I won't be able to review until after that. But I will definitely have a look...

@ferrellsl Your comment is unrelated to the topic of this issue (transmitting using FL2K). Please open a new issue if you'd like to discuss something else.

Hi @RadarFolf, and thanks for your interest in the project. First off, I should point out that I created this project in my spare time for the fun of it,...

It would definitely be good to add other messages to the SIS encoder. Currently it only encodes "Station Name – short format" messages: https://github.com/argilo/gr-nrsc5/blob/master/lib/sis_encoder_impl.cc I don't have any immediate plans...

The specification indicates that "Station Name - long format" is "Not recommended for new designs." Universal Short Station Name (MSG ID 1000) seems to be its replacement.