Sending to CWOP

For those that have developed an application to send data to CWOP, what are you putting for equipment.

I think it would be nice to have a standard parameter that indicates the WeatherFlow equipment.

I’m still using what I had set for my old station, an Acurite 5n1 so “400” is the equipment type value in my software right now.

1 Like

I am using the ID of my upload software. But, I agree, we should have a common WF designation.


1 Like

My 2 cents is I’d like to see a HUB link to CWOP, the same that is used to to send data to WU. Eliminates running extra hardware 24/7 just to send the data to CWOP.


I’m not sure if there’s a definitive list of codes to use for equipment type. I used this:

And a list of software that supports upload to CWOP

Looking at the spec, it looks like you can have up to 5 characters so maybe ‘wflow’?

And I am sending whatever Meteobridge decided to use for uploading to CWOP, which is Meteobridge 3.7.


1 Like

Did you write your own or are you using Meteobridge?

I am referring this to developers here that write their own applications.

Weewx is sending “.weewx-3.8.0-Vantage” on my APRS packets, the Vantage part is the weewx driver name for the Davis Vantage/VP2 station that is running as my primary setup right now…

1 Like

Thank you. I looked at Weewx and saw part of what it was sending.

I am inquiring about applications that are not part of a bigger application. It looks like no one else has developed an add-on to send to CWOP.

So, am going to send “WFArchive_1.6.12_WeatherFlow”

1 Like

Unless someone else is using underscores, I’d suggest sticking with hyphens as delimiters to follow weewx’s lead…

1 Like

I’m from the school where a - means subtract and a _ replaces a [space].

1 Like

I am from the school of RegEx, and am suggesting following weewx’s lead to standardize parsing unless other packages are already using underscores…


Your code, your rules. I can’t find any evidence there is a wrong answer or any limitation.

Check out the right side of each line in for some examples

1 Like

Weewx 3.8.0 is not sending the leading “e” on the equipment. That’'s not nice.

1 Like

Does anyone know what data the “L” in cwop is used to send?

I see nowhere the syntax is defined on the CWOP site, but if you feel it’s a bug in weewx, put in an Issue on their github page. FWIW, I see lots of values in there that ‘seem’ to use a ‘.’ as the delimiter, which is what weewx does. That said, you’re probably going to have to reference their requirements document for anybody to work it as a bug. The CWOP posting code has been in weewx since 2013 according to their github repo.


This packet uses a space in the equipment and a leading “.”
FW0140>APRS,TCPXX*,qAX,CWOP-7:@132155z -3.363514709472/-3.363514709472_335/000g000t053r000p000P000b10241h88.WD 31

This packet uses an underscore and a leading “.”

This packet does not use anyhing to qualify the equipment and has the “L” parameter

This packet uses underscore in the equipment.

I’m getting the impression that CWOP is a free-for-all and there are few rules that are enforced.

Here is a list of equipment. Several use “_” as a seperator.

1 Like

Sure seems that way. Go appropriately wild.


It get worse. One document states wind direction and speed is sent using:


while the official PDF spec states:


What do I do?

The “L” data is solar radiation

There are two places where you can specify equipment; the ident field and embedded in the data itself.

The information in the ident seems to be free form. I’m using “linux-acu-link 1.00” which is based on the original software I wrote to upload data from my Acurite 5n1.

The equipment type embedded in the data is at the end of the data and based on my reading of the spec. it’s between 3 and 5 characters long. But given that it’s at the end, there may not be any checking to enforce that length.

There does appear to be multiple data formats that can be used. See

My data looks like: