QTH.app v0.3.1

83 views
Skip to first unread message

Weston Bustraan

unread,
Apr 26, 2021, 10:21:33 PM4/26/21
to qthapp-users
New build available: QTH-0.3.1.dmg

Changelog:
- Filter changes on the APRS-IS config window will now automatically be sent to the server if the connection is active
- Implemented message authentication
- Fixed a bug with parsing patterns in the tocall database
- Now detects OS sleep and wake, disconnecting and reconnecting connections respectively
- Last path for stations is now stored in the entity table and displayed on the info panels
- Refreshing canSend whenever the message to: address changes #87
- Fixed bug where MeasurementFormatter was not behaving as expected and temperatures were displayed in the wrong units #86

Weston Bustraan

unread,
Apr 27, 2021, 7:03:29 AM4/27/21
to qthapp-users
Just a note on the message authentication: As far as I know, YAAC is the only other APRS client that supports this. Currently, there is a bug in the signatures sent by YAAC, so QTH cannot validate messages coming from YAAC until that is fixed. I filed a bug with Andrew. YAAC can validate messages sent by QTH, though.

Andrew says that he will be changing the hash algorithm from MD5 to SHA256 because Oracle is disabling older, insecure algorithms in Java. When he makes that change, I will update QTH to match.

Some time, it might be fun to have an authenticated chat over APRS-IS. I will say that any time you see me my station show up on the map, you’re welcome to send me a message, signed or not. Just know that I might be doing the “change code, restart QTH, debug” cycle, so I might not receive it on the first shot.

The main challenge yet with authenticated messages is the process of exchanging symmetric keys out of band. However, I have some ideas on that, involving the license certificates you get when you get a QTH license. They are full public/private key certificates, allowing for encrypting payloads (as long as those payloads don’t go over RF, of course) Stay tuned!

- Wes, W8WJB 

Kevin Reeve

unread,
Apr 29, 2021, 11:24:15 AM4/29/21
to qthapp-users
Installed 0.3.1 
I am connected to my Kenwood D74 and receiving stations.  Love the new path feature.   
My Beacon button at the top of the screen is now grey'd out.
TX box is checked on my Connection
Beacon is enabled and set to All, have also tried local.
Nothing seems to enable the beacon button.   

Ideas?

Kevin - N7RXE

Weston Bustraan

unread,
Apr 29, 2021, 8:28:51 PM4/29/21
to Kevin Reeve, qthapp-users
I think there was a race condition where conditions that enable the button were occurring before the button had appeared on the screen. 

Try the new build from tonight, 0.4.0 and see if that helps.

- Wes, W8WJB

--
You received this message because you are subscribed to the Google Groups "qthapp-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qthapp-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qthapp-users/06e6f0a4-6dab-483a-99f7-cfd9f2c00d1fn%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kevin Reeve

unread,
Apr 29, 2021, 10:38:21 PM4/29/21
to qthapp-users
beacon working on o.4.0 connected to Kenwood D74 and also to T2 Oregon.

Thanks

Weston Bustraan

unread,
Apr 30, 2021, 7:20:48 AM4/30/21
to Andy McMullin, qthapp-users
Ah, the factor is probably the manual location. With both Location Services and GPS, there is a natural source of incoming location updates, whereas it has to be simulated with a manual location. There is probably a bug with the timer that fires off manual location updates. I'll look into it and hopefully have an update this evening.

As far as remembering the map location goes, that was a feature that was added in v0.2.0. Whatever windows you have open when you close QTH should be saved and restored when you next start QTH. However, there is a setting in macOS System Preferences that can prevent this from working.

Go to System Preferences -> General and look for the checkbox labeled, "Close windows when quitting an app".

Screen Shot 2021-04-30 at 7.15.24 AM.png





On Fri, Apr 30, 2021 at 3:41 AM Andy McMullin <andy.m...@icloud.com> wrote:
Hi All,

I am only connecting to IP at the moment. It has authenticated my callsign and “password” and I am receiving apparently just fine. However, I can’t seem to send a beacon either! It was fine with 0.3.0 but stopped with 0.3.1 and has not recovered with 0.4.0

I have TX enabled on the connection and tried switching it off then back on again after while in case it’s a startup issue. I have location services disabled, but have the position entered manually. I have tried both “internet" and “both" as scope. I have set both Manual and a fixed 30 minute interval in rate. No difference and the beacon icon remains grey.

As a secondary idea, which I don’t think is related, any chance the application could remember the previous zoom level of the map? It defaults when I open it to showing the whole of the UK which means a massive flood of stations before I can zoom back in to a reasonable range.

Regards
Amdu

Andy McMullin

unread,
Apr 30, 2021, 9:11:28 AM4/30/21
to Weston Bustraan, qthapp-users
Wes,

Thanks for that. I look forward to trying an update in the future.

I can confirm that “Close windows when quitting an app” was selected. When turned off, the application restarted with the window zoomed in as I had left it. Thank you.

Regards
Andy



On 30 Apr 2021, at 12:20, Weston Bustraan <wbus...@gmail.com> wrote:

Ah, the factor is probably the manual location. With both Location Services and GPS, there is a natural source of incoming location updates, whereas it has to be simulated with a manual location. There is probably a bug with the timer that fires off manual location updates. I'll look into it and hopefully have an update this evening.

As far as remembering the map location goes, that was a feature that was added in v0.2.0. Whatever windows you have open when you close QTH should be saved and restored when you next start QTH. However, there is a setting in macOS System Preferences that can prevent this from working.

Go to System Preferences -> General and look for the checkbox labeled, "Close windows when quitting an app".

Reply all
Reply to author
Forward
0 new messages