Log4OM

I just made it work by checking not confirmed on band or emission type. But will not work on not confirmed alone.

I do not have LOTW confirmation on 5H4WZ but I have worked them.

Test spots are not triggering audio alerts properly at this time


Try the same filters in the cluster and watch the highlight colours change

In my example Argentina is worked and was confirmed by QSL but not by EQSL or LOTW hence the red new one highlight

OK will watch it. But I have seen Tanzania spotted on the cluster over the last few days several times and have not received an alert for days.

I already have several alerts set up that worked in 2.2 and I have noticed this behavior when checking alert configuration in 2.3

If I go into the alert configuration, the first time I look at the settings for the dxcc's that I have chosen, it indicates that I have "0 items selected".

If I then look at a different alert configuration and then return to the first one, the setting shows the correct number of dxcc's which I have selected.

Not sure if this is related to the fact that alerts are not being displayed.

W2GTR wrote: ↑11 Feb 2020, 19:17
If I then look at a different alert configuration and then return to the first one, the setting shows the correct number of dxcc's which I have selected.

I guess to make sure, I assume we do not have to check off DXCC countries. It should be dynamic based on what is in the log as worked/verified.

I just heard the alert work for a country I have never worked. But it is not working on countries I have worked but have no confirmation via LOTW.

Nolan, Rich and Terry

To sum up my problem is that i should not use admin privileges if i want alarms to work.

Had similar issue with cluster alerts.

Finally I separated to several alerts (i.e. One alert per call sign, one alert per DXCC, etc) and it works fine.