Date   

locked Re: 2.16.1 Worked B4

Matt M0LMK
 

Thanks Laurie.

As usual, always happy to help test.
--
Matt
M0LMK/KI5GXV


locked Re: No Alert Sounds

Dwight Bosselman
 

That is part of what I did, please see:

Under Settings, Misc. Alerts, I have "End of TX/RX Period", "Start of TX Period" and "TX Watchdog" all enabled with Waves Files Defined, and Test works in all of them.

On 3/10/2020 10:31 PM, HamApps Support (VK3AMA) wrote:
On 11/03/2020 8:14 am, Dwight Bosselman wrote:
I just updated to 2.16.1.

I know the version isn't related but for the last 3 versions I've got no audio for my Alerts.

I have the SC card defined correctly and when I do the two "test sounds" , from the main screen under Sound On and Settings, they work. Sound is set to On.

Under Settings, Sound Card, I have it defined properly and the Test Play works.

Under Settings, Misc. Alerts, I have "End of TX/RX Period", "Start of TX Period" and "TX Watchdog" all enabled with Waves Files Defined, and Test works in all of them.

Under Alerts in the main screen I have all of them checked.

What am I missing? At one time they all worked fine. ;-)

73 Dwight NS9I

From you description it appears you manually tested all the Sounds except those for the Wanted Alerts.  Visit each Alert type in the Settings and ensure there is a wav file set for the Alert. You can Test each Alert individually.

de Laurie VK3AMA


locked Re: 2.16.1 Worked B4

HamApps Support (VK3AMA)
 

On 11/03/2020 4:36 pm, Matt M0LMK wrote:
I've also tested with SQLITE and the same thing happens.

Hovering over the callsign shows Worked B4 as False.



Matt
M0LMK/KI5GXV
_._,_._,_

OK. This is the same defect that was corrected in the last release for the "NO Log" users. At that time, there were no other reports of similar behavior with Log4OMV2.

I'll release a new public build as soon as I have corrected the problem and affected users have reported that the issue is corrected.

de Laurie VK3AMA


locked Re: 2.16.1 Worked B4

Matt M0LMK
 
Edited

I've also tested with SQLITE and the same thing happens.

Hovering over the callsign shows Worked B4 as False.



Matt
M0LMK/KI5GXV


locked Re: 2.16.1 Worked B4

Matt M0LMK
 

I may have the same issue.

First decode of a new station and everything is fine.
Second and subsequent decode of the same station then shows as Worked B4 (regardless of their worked status)

Not sure if that is the same as Fred but I am also running v2.16.1 with Log4OM v2.5 and MYSQL DB.

Matt
M0LMK/KI5GXV


locked Re: Download Link SSL Error

WB8ASI Herb
 

Laurie,  I understand.  Just another over aggressive protection.  Just wish Comcast/Xfinity would let you know that they were the ones blocking.  My only clue was a new icon I saw on the blocking page, and later saw the same icon by chance on my Xfinity homepage telling me I got the extra protection for free.  I don't mind extra protection, but it didn't ID itself upon the blocking.  So hard to find the workaround.  Anyways,  I totally trust your software and understand why it triggers a low user base.  We'll probably see more and more security added.  Just need to know how to adjust, and get the good stuff thru. 73, Herb WB8ASI 

On March 10, 2020 at 10:39 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 11/03/2020 8:08 am, Kevin Utzy wrote:
Thanks Herb.  Sure enough that did it.

73,
Kevin
KX4KU

FYI,

There is not an actual SSL problem with HamApps, All its certificates and supported protocol levels are current. The problem is that all your Internet traffic is now passing though the
xfinity service and it is interfering with the SSL connection such that your Browser receives an SSL error. The SSL error type reported by your Browser is its attempt at providing a description of the fault it encountered.

de Laurie VK3AMA


 


locked Re: No Alert Sounds

WB8ASI Herb
 

and maybe just double check that you have each Alert Enabled at the top of every Alert's page.  Just a thought. 73, Herb WB8ASI

On March 10, 2020 at 10:31 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 11/03/2020 8:14 am, Dwight Bosselman wrote:
I just updated to 2.16.1.

I know the version isn't related but for the last 3 versions I've got no audio for my Alerts.

I have the SC card defined correctly and when I do the two "test sounds" , from the main screen under Sound On and Settings, they work. Sound is set to On.

Under Settings, Sound Card, I have it defined properly and the Test Play works.

Under Settings, Misc. Alerts, I have "End of TX/RX Period", "Start of TX Period" and "TX Watchdog" all enabled with Waves Files Defined, and Test works in all of them.

Under Alerts in the main screen I have all of them checked.

What am I missing? At one time they all worked fine. ;-)

73 Dwight NS9I

From you description it appears you manually tested all the Sounds except those for the Wanted Alerts.  Visit each Alert type in the Settings and ensure there is a wav file set for the Alert. You can Test each Alert individually.

de Laurie VK3AMA


 


locked Re: Download Link SSL Error

HamApps Support (VK3AMA)
 

On 11/03/2020 8:08 am, Kevin Utzy wrote:
Thanks Herb.  Sure enough that did it.

73,
Kevin
KX4KU

FYI,

There is not an actual SSL problem with HamApps, All its certificates and supported protocol levels are current. The problem is that all your Internet traffic is now passing though the
xfinity service and it is interfering with the SSL connection such that your Browser receives an SSL error. The SSL error type reported by your Browser is its attempt at providing a description of the fault it encountered.

de Laurie VK3AMA


locked Re: 2.16.1 Worked B4

HamApps Support (VK3AMA)
 

On 11/03/2020 2:48 am, PA0FVH wrote:
I am afraid Version JTAlert v2.16.1 didn't fix the Worked B4 issue for me.
I do have logging enabled in the title bar (LOG4V2+)
Log4OM v2.4 on MySQL DB.

73
Fred PA0FVH
What B4 issue are you experiencing?

de Laurie VK3AMA


locked Re: No Alert Sounds

HamApps Support (VK3AMA)
 

On 11/03/2020 8:14 am, Dwight Bosselman wrote:
I just updated to 2.16.1.

I know the version isn't related but for the last 3 versions I've got no audio for my Alerts.

I have the SC card defined correctly and when I do the two "test sounds" , from the main screen under Sound On and Settings, they work. Sound is set to On.

Under Settings, Sound Card, I have it defined properly and the Test Play works.

Under Settings, Misc. Alerts, I have "End of TX/RX Period", "Start of TX Period" and "TX Watchdog" all enabled with Waves Files Defined, and Test works in all of them.

Under Alerts in the main screen I have all of them checked.

What am I missing? At one time they all worked fine. ;-)

73 Dwight NS9I

From you description it appears you manually tested all the Sounds except those for the Wanted Alerts.  Visit each Alert type in the Settings and ensure there is a wav file set for the Alert. You can Test each Alert individually.

de Laurie VK3AMA


locked Re: JTAlert version 2.16.1? Worked Before U.S.A. State difference

HamApps Support (VK3AMA)
 

On 11/03/2020 5:23 am, pphiliphome@... wrote:
I noticed a slight difference in worked before works for US stations. In the past, if a US station was flagged next to the call, the State was displayed alongside U.S.A below the call.

This does not happen now. I found it sometimes useful to jog the memory. No big deal if this is the way it is now. Just thought I would point it out.

73, Paul AC9O

Paul,

An undocumented change. The relevant code block was commented out as part of the new VE Province Alert integration. Looking at the code, I can see why it was disabled, but I don't know why I didn't go back and re-enable it. I will look getting it back in for the next release.

de Laurie VK3AMA


locked Re: Worked B4

HamApps Support (VK3AMA)
 

On 11/03/2020 12:40 pm, N8GMY@... wrote:
I am frustrated by the worked B4 function. I am using ACLog. Sometimes it works and sometimes it doesn't. I have started bringing ACLog to the front. Hamapps is telling me that is a new contact. And ACLog tells me when I worked it before. I have scanned the log in Hamapps to no avail. What am I missing here?

Ross
N8GMY
Sounds like you don't have ACLog set as the enabled logger in JTAlert, is that the case? If so, then there are no guarantees with respect to B4 accuracy if your manually logging QSOs to ACLog without JTAlert being aware that the logging occurred.

If you do have ACLog logging enabled in JTAlert, then the usual source of discrepancies is that your current Mode & Band  is not the same as the Log entry your examining. JTAlert by default considers both Band, Mode & Grid in determining the B4 status of a Callsign.

de Laurie VK3AMA


locked Worked B4

Gator
 

I am frustrated by the worked B4 function. I am using ACLog. Sometimes it works and sometimes it doesn't. I have started bringing ACLog to the front. Hamapps is telling me that is a new contact. And ACLog tells me when I worked it before. I have scanned the log in Hamapps to no avail. What am I missing here?

Ross
N8GMY


locked Re: JTAlert Setup issue

WB8ASI Herb
 

I notice you have a Comcast email.  I ran into a similar problem.  I found it to be some new xFi Advanced Security added by my ISP.  So if you have Comcast/Xfinity, you might try disabling this new security on your Gateway/Router just long enough to make the download.   You can access it thru your Account, but it wasn't easy to find.  Here's the path to take you where you can disable/enable.     https://internet.xfinity.com/more/my-services/my-services-disabling  Good luck. Herb WB8ASI

On March 10, 2020 at 7:55 PM Jim Denneny <57JNDenneny@...> wrote:

Win 10 is blocking download of JTAlert updates.  I have shutdown Virus & Threat Protection in Settings in Windows Security.  I don't see how to whitelist the setup file. What am I missing?

73, Jim K7EG

 


locked JTAlert Setup issue

Jim Denneny
 

Win 10 is blocking download of JTAlert updates.  I have shutdown Virus & Threat Protection in Settings in Windows Security.  I don't see how to whitelist the setup file. What am I missing?

73, Jim K7EG


locked No Alert Sounds

Dwight Bosselman
 

I just updated to 2.16.1.

I know the version isn't related but for the last 3 versions I've got no audio for my Alerts.

I have the SC card defined correctly and when I do the two "test sounds" , from the main screen under Sound On and Settings, they work. Sound is set to On.

Under Settings, Sound Card, I have it defined properly and the Test Play works.

Under Settings, Misc. Alerts, I have "End of TX/RX Period", "Start of TX Period" and "TX Watchdog" all enabled with Waves Files Defined, and Test works in all of them.

Under Alerts in the main screen I have all of them checked.

What am I missing? At one time they all worked fine. ;-)

73 Dwight NS9I


locked Re: Download Link SSL Error

Kevin Utzy
 

Thanks Herb.  Sure enough that did it.

73,
Kevin
KX4KU


locked Re: Download Link SSL Error

WB8ASI Herb
 

Yes,  I had similar SSL error blocking the download.  Try disabling the xFi Advanced Security long enough to download.   https://internet.xfinity.com/more/my-services/my-services-disabling

On March 10, 2020 at 2:21 PM Kevin Utzy <krutzy62@...> wrote:

Herb,  As a matter of fact I do.  Are implying that new xFi advanced security junk might be it?  

Mike, I did try incognito mode and Opera's VPN.  Not real I know but no joy.

73,
Kevin
KX4KU


 


locked Re: Download Link SSL Error

km4djo
 

It is the  new xfinity security suit.... go here and you can shut it off temporarily......

https://internet.xfinity.com/more/my-services/my-services-disabling

Then re-enable it after your fine downloading.  Herb, wb8asi figured this problem out.

Sent from my Samsung Galaxy smartphone.


-------- Original message --------
From: Kevin Utzy <krutzy62@...>
Date: 3/10/20 14:21 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Download Link SSL Error

Herb,  As a matter of fact I do.  Are implying that new xFi advanced security junk might be it?  

Mike, I did try incognito mode and Opera's VPN.  Not real I know but no joy.

73,
Kevin
KX4KU


locked JTAlert version 2.16.1? Worked Before U.S.A. State difference

Paul AC9O
 

I noticed a slight difference in worked before works for US stations. In the past, if a US station was flagged next to the call, the State was displayed alongside U.S.A below the call.

This does not happen now. I found it sometimes useful to jog the memory. No big deal if this is the way it is now. Just thought I would point it out.

73, Paul AC9O