Other spots, Logging, and Third Partyu Integration

[rclewen]

Good day! I bought a prebuilt SotaCat from Inverted Labs and set it up yesterday and I am loving it! I do have some ideas for enhancements if you are open to them.

1. Is it possible to incorporate spots from WWFF and a DX Cluster?
2. Have you thought about any type of logging integration? Upload to QRZ would be great, but a local ADIF file would be fine.
3. Have you looked at integration with any third party apps? Ham2K PoLo would be ideal. That could become an alternate UI.
4. One other thought... How about a respotting feature?

I also have one question... Is it possible to access the SotaCat remotely? It would be interesting to try. Is it just port 80?

Thanks!

...ron
N7BBQ

[jeffkowalski]

Hi Ron N7BBQ, glad you're enjoying SOTACat.

1. The branch https://github.com/SOTAmat/SOTAcat/tree/kowalski/wip unifies all of the spots onto one page, and contains all WWFF and DX Cluster spots, and many more types as well. If you're comfortable building the firmware (I recommend PIO, you can try that branch). Otherwise I'd be happy to send you a firmware.bin file for you to try.
2. Yes, logging would be great but without information about the current location (peak or park) it's not as valuable. And there are still some hurdles to getting that info. I am also a bit nervous about storing the log. It's challenging to come back to the same browser session, so if the session drops before the log is written to the phone, the log is lost.
3. Yes, integration would PoLo would require a deep link to that app. I have been contemplating what exactly to ask for so that I don't overburden that developer.
4. Self-spotting is currently handled by SOTAMat (not SOTACat). Re-spotting of other operators from SOTACat would require call to the respective agencies (POTA, etc.). That could be a bit easier.
5. Yes, SOTAcat is listening on port 80. You can open that port, or forward it, or reverse-proxy it for remote access. But remember, the audio isn't going to be available remotely. That said, I use SOTAcat from my browser all the time.
   I will mention too that the SOTA-NA Slack has a sotacat-sotamat channel that might interest you.
   73,
   Jeff KC6X

[rclewen]

Hi Jeff! Thanks for the quick response!  My responses in  line below... - The branch https://github.com/SOTAmat/SOTAcat/tree/kowalski/wip unifies all of the spots onto one page, and contains all WWFF and DX Cluster spots, and many more types as well. If you're comfortable building the firmware (I recommend PIO, you can try that branch). Otherwise I'd be happy to send you a firmware.bin file for you to try. I would love to try it! If you don't mind sending a bin file I would appreciate it. It has been a very long time since I did any firmwaqre work. - Yes, logging would be great but without information about the current location (peak or park) it's not as valuable. And there are still some hurdles to getting that info. I am also a bit nervous about storing the log. It's challenging to come back to the same browser session, so if the session drops before the log is written to the phone, the log is lost. Good point!  My use case is hunting, so I don't need to log the park info since it is just for me use, but I understand.  Also, the loss of the log data would be a concern. - Yes, integration would PoLo would require a deep link to that app. I have been contemplating what exactly to ask for so that I don't overburden that developer. Understood. They seem to be great guys, but I know that they are also very busy.  My thought is a way to use their spotting tab to trigger the QSY on the radio.  The actual spotting, logging, eetc. would still be handled by PoLo. - Self-spotting is currently handled by SOTAMat (not SOTACat). Re-spotting of other operators from SOTACat would require call to the respective agencies (POTA, etc.). That could be a bit easier. I was thinking mostly about re-spotting. I saw the self spotting via SOTAMat but haven't tried it yet. - Yes, SOTAcat is listening on port 80. You can open that port, or forward it, or reverse-proxy it for remote access. But remember, the audio isn't going to be available remotely. That said, I use SOTAcat from my browser all the time. Ah!  I forgot about the audio :-D  I have been using it via my laptop this morning and that is what made me think about remote. - I will mention too that the SOTA-NA Slack has a sotacat-sotamat channel that might interest you. Thanks! I haven't used Slack in a while. I take a look. ....ron Ron Lewen - N7BBQ ***@***.*** N7BBQ Callsign Page On Wednesday, November 19, 2025 at 12:33:18 PM CST, Jeff Kowalski ***@***.***> wrote: Hi Ron N7BBQ, glad you're enjoying SOTACat. - The branch https://github.com/SOTAmat/SOTAcat/tree/kowalski/wip unifies all of the spots onto one page, and contains all WWFF and DX Cluster spots, and many more types as well. If you're comfortable building the firmware (I recommend PIO, you can try that branch). Otherwise I'd be happy to send you a firmware.bin file for you to try. - Yes, logging would be great but without information about the current location (peak or park) it's not as valuable. And there are still some hurdles to getting that info. I am also a bit nervous about storing the log. It's challenging to come back to the same browser session, so if the session drops before the log is written to the phone, the log is lost. - Yes, integration would PoLo would require a deep link to that app. I have been contemplating what exactly to ask for so that I don't overburden that developer. - Self-spotting is currently handled by SOTAMat (not SOTACat). Re-spotting of other operators from SOTACat would require call to the respective agencies (POTA, etc.). That could be a bit easier. - Yes, SOTAcat is listening on port 80. You can open that port, or forward it, or reverse-proxy it for remote access. But remember, the audio isn't going to be available remotely. That said, I use SOTAcat from my browser all the time. I will mention too that the SOTA-NA Slack has a sotacat-sotamat channel that might interest you. 73, Jeff KC6X — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>