Not a bug, but

6 posts / 0 new

Sun, 04/12/2020 - 16:49

w6bi

Not a bug, but

So, the AREDN alerts are working properly, but what's to be done with this:

AREDN Alert(s):

(QST): AREDN v3.20.3.0 has been released

When the node is running a nightly build more current than that? Maybe add it as a second line ("Latest nightly build is xxxx")?

Orv W6BI

Mon, 04/13/2020 - 15:21

K5DLQ

(That QST was just a sample

(That QST was just a sample broadcast message.). ;-)
I "fixed" it. (BTW, you can force a refresh on the AdvConfig page)

Mon, 04/13/2020 - 18:14

(Reply to #2) #3

w6bi

Thanks.

Thanks, Darryl - something to consider is putting a broadcast when a new nightly build is available, and what features it provides and/or bugs eliminates.

Orv W6BI

Mon, 04/13/2020 - 19:42

(Reply to #3) #4

K5DLQ

Yeah. I've been considering

Yeah. I've been considering writing a few AREDN Map database query scripts to generate messages for things like:

nodes running non-current firmware
nodes running nightly builds (with current nightly build version info, ie. current nightly build number
nodes with obviously incorrect lat/lon values
nodes that have not updated map locations in over 1 year
nodes running channel -2 and 20Mhz channel width

Tue, 04/14/2020 - 16:17

KD1HA

I agree with Damon

I agree with Damon isn't it the point of AREDN collaboration and communication? Sending and receiving alerts is on top of the list? Thanks guys keep up the great work!

Denis

Tue, 04/14/2020 - 19:57

K6CCC

Granted it will take years

Granted it will take years before everyone has updated to a new enough firmware in order to see the alerts, but the ability to push limited messages is highly useful. The current best one I can think of is Night Build announcements. Avoids having to go check every morning.

Amateur Radio Emergency Data Network

Menu SF

You are here

Not a bug, but

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Not a bug, but