How to integrate pywws with various weather services

This guide gives brief instructions on how to use pywws with some other weather services and software. It is not comprehensive, and some services (such as Twitter) are covered in more detail elsewhere.


YoWindow is a weather display widget that can display data from an internet source, or from your weather station. To display data from your station pywws needs to write to a local file, typically every 48 seconds when new data is received. This is easy to do:

  1. Stop all pywws software

  2. Copy the yowindow.xml example template to your text template directory.

  3. If you haven’t already done so, edit weather.ini and set the local_files entry in the [paths] section to a suitable directory for your yowindow file.

  4. Add the yowindow template to the [live] tasks in weather.ini. Set its flags to 'L' so the result is copied to your local directory instead of being uploaded to an ftp site:

    text = [('yowindow.xml', 'L')]
  5. Restart pywws live logging.

You can check the file is being updated every 48 seconds by using more or cat to dump it to the screen.

Finally configure yowindow to use this file. See for instructions on how to do this.


See How to configure pywws to post messages to Twitter for full instructions.

Other “services”

The remaining weather service uploads are handled by the pywws.toservice module. See the module’s documentation for general configuration options. The following subsections give further information about some of the available services.

Citizen Weather Observer Program

New in version 14.02.dev1156.

  • Web site:

  • Create account:

  • API:

  • Example weather.ini section:

    designator = EW9999
    latitude = 5130.06N
    longitude = 00008.52E
    template = default
    services = ['cwop', 'underground']
    services = ['cwop', 'underground_rf']

    or, for radio hams:

    designator = G4XXX
    passcode = xxxxxx
    latitude = 5130.06N
    longitude = 00008.52E
    template = default
    services = ['cwop_ham', 'underground']
    services = ['cwop_ham', 'underground_rf']

Note that the latitude and longitude must be in “LORAN” format and leading zeros are required. See question 3 in the CWOP FAQ for more information.

Licensed radio hams use their callsign as the designator and need a passcode. They should use the service name cwop_ham instead of cwop when running pywws.toservice directly and in the weather.ini services entries. (The same [cwop] config section is used for both.)

CWOP uploads are rate-limited by pywws, so you can safely add it to both the [live] and [logged] sections in weather.ini.

The CWOP/APRS uploader is based on code by Marco Trevisan <>.


New in version 14.12.0.dev1260.

MQTT is a “message broker” system, typically running on localhost or another computer in your home network. Use of MQTT with pywws requires an additional library. See Dependencies - MQTT for details.

  • MQTT:

  • Mosquitto (a lightweight broker):

  • Example weather.ini section:

    topic = /weather/pywws
    hostname = localhost
    port = 1883
    client_id = pywws
    retain = True
    auth = False
    user = unknown
    password = unknown
    template = default
    multi_topic = False
    services = ['mqtt', 'underground']

pywws will publish a JSON string of the data specified in the mqtt_template_1080.txt file. This data will be published to the broker running on hostname, with the port number specified. (An IP address can be used instead of a host name.) client_id is a note of who published the data to the topic. topic can be any string value, this needs to be the topic that a subscriber is aware of.

retain is a boolean and should be set to True or False (or left at the default unknown). If set to True this will flag the message sent to the broker to be retained. Otherwise the broker discards the message if no client is subscribing to this topic. This allows clients to get an immediate response when they subscribe to a topic, without having to wait until the next message is published.

auth, user and password can be used for MQTT authentication.

multi_topic is a boolean and should be set to True or False. If set to True pywws will also publish all the data each as separate subtopics of the configured topic; i.e., with the topic set to /weather/pywws pywws will also publish the outside temperature to /weather/pywws/temp_out and the inside temperature to /weather/pywws/temp_in.

If these aren’t obvious to you it’s worth doing a bit of reading around MQTT. It’s a great lightweight messaging system from IBM, recently made more popular when Facebook published information on their use of it.

This has been tested with the Mosquitto Open Source MQTT broker, running on a Raspberry Pi (Raspian OS). TLS (mqtt data encryption) is not yet implemented.

Thanks to Matt Thompson for writing the MQTT code and to Robin Kearney for adding the retain and auth options.

UK Met Office

Open Weather Map

When choosing a user name you should avoid spaces (and probably non-ascii characters as well). Having a space in your user name causes strange “internal server error” responses from the server.

The default behaviour is to use your user name to identify the weather station. However, it’s possible for a user to have more than one weather station, so there is an optional name parameter in the API that can be used to identify the station. This appears as id in weather.ini. Make sure you choose a name that is not already in use.

PWS Weather

  • Web site:

  • Example weather.ini section:

    hash = ???
    template = default
    services = ['temperaturnu', 'underground']

You receive the hash value from the admins during sign up. It looks like “d3b07384d113edec49eaa6238ad5ff00”.

Weather Underground

Weather Underground “RapidFire” updates

Weather Underground has a second upload URL for real time updates as little as 2.5 seconds apart. If you run pywws in ‘live logging’ mode (see How to set up ‘live’ logging with pywws) you can use this to send updates every 48 seconds, by adding ‘underground_rf’ to the [live] tasks section in weather.ini:

station = ABCDEFGH1
password = xxxxxxx
template = default

services = ['underground_rf']

services = ['underground', 'metoffice']

Make sure you still have an ‘underground’ service in [logged] or [hourly]. This will ensure that ‘catchup’ records are sent to fill in any gaps if your station goes offline for some reason.

Custom Request Headers

The pywws.toservice module does support the injection of one or more custom request headers for special cases where you want to integrate with a service that, for example, requires you to pass an authentication key header along with each request, such as x-api-key.

These headers can be added to your a_service.ini file in the format of key value pairs:

url         =
catchup             = 100
interval    = 0
use get             = True
result              = []
auth_type   = None
http_headers        = [('x-api-key', 'my-api-key'), ('x-some-header', 'value')]

Comments or questions? Please subscribe to the pywws mailing list and let us know.