OH3CUF
July 30, 2024, 7:36am
1
It would be really cool if HamAlert would follow CQGMA cluster for more spots - especially WWFF (non-CW). Also SOTA/IOTA etc. are available there.
The “smartWWFF” spots appear also on this server.
Their cluster / dx spider is at: www.cqgma.org 7300
OH3CUF
July 30, 2024, 7:54am
2
A bit related to this one but I think it would increase trigger performance to use data directly from GMA.
For example this spot from DX Cluster was not triggering my “all OHFF spots” rule:
OH3CUF
July 30, 2024, 7:55am
3
It was seen on GMA cluster:
“DX de OH2NOS: 10123.0 OH2NOS/P x01f OHFF-1785 New one! 0750Z”
VK2MET
August 6, 2024, 6:32am
4
Actually, consuming this resource will bring back WWFF parks most reliably:
https://www.cqgma.org/api/spots/wwff/
OH3CUF
January 14, 2025, 8:09am
5
@VK2MET any progress on this? It would be nice to get all WWFF spots to HamAlert.
VK2MET
January 14, 2025, 9:07am
6
This thread with Manuel has info on the Cluster format required. I still cannot get FF- parks spots to come thru on HamAlert though
[Screenshot 2024-06-10 at 07.33.22]
According to the data on the HamAlert server, the 0130Z spot for VK4FE was sent to your app. The one at 0216Z on 6m did not match your trigger, as the mode could not be determined unambiguously. 50.150 is a frequency that the IARU Region 1/2/3 band plans give as mixed CW/phone/digi. I don’t do enough 6m to know whether anybody actually does CW around that frequency, or if it’s safe to assume that anything > 50.100 is SSB. Inputs welcome. To err on the side o…
OH3CUF
January 14, 2025, 10:27am
7
The CQGMA DX Spider is own entity and yes as you noticed is hardly linked to anything. I don’t know the reason for that. It shouldn’t matter however in this case.
I think there is something broken in HamAlert as the CQGMA cluster spots are not triggered on HamAlert. I assume you are using https://www.cqgma.org/api/spots/wwff/ or the direcly to dxspider at www.cqgma.org / 7300 ?