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 most 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:
Stop all pywws software
yowindow.xmlexample template to your text template directory.
If you haven’t already done so, edit
weather.iniand set the
local_filesentry in the
[paths]section to a suitable directory for your yowindow file.
Add the yowindow template to the
weather.ini. Set its flags to
'L'so the result is copied to your local directory instead of being uploaded to an ftp site:
[live] text = [('yowindow.xml', 'L')]
Restart pywws live logging.
You can check the file is being updated every 48 seconds by using
cat to dump it to the screen.
Finally configure yowindow to use this file. See http://yowindow.com/pws_setup.php for instructions on how to do this.
See How to configure pywws to post messages to Twitter for full instructions.
The remaining weather service uploads are handled by modules in the pywws.service sub-package.
||Upload weather data to Citizen Weather Observer Program.|
||Upload weather data to UK Met Office “WOW”.|
||Upload weather data to MQTT message broker.|
||Upload weather data to Open Weather Map.|
||Upload weather data to PWS Weather.|
||Upload current temperature to temperatur.nu.|
||Upload data to Weather Underground.|
||Upload weather data to wetter.com.|
These each use a separate thread to upload the data so that a slow or not responding service doesn’t delay other processing or uploads.
The service uploaders are all used in a similar fashion:
Create an account with the service.
Stop all pywws software.
Run the service module directly to initialise its entry in
weather.ini. For example:
python -m pywws.service.underground /home/jim/weather/data
weather.iniand add your account details to the appropriate section (e.g.
Run the service module directly (with high verbosity) to make sure your account details are correct:
python -m pywws.service.underground -vvv /home/jim/weather/data
Each service’s server software responds differently to correct or incorrect uploads. You should be able to tell from the response if it was successful or not.
weather.iniand add the service to the
[live]) sections, e.g.:
[logged] services = ['underground'] [live] services = ['underground']
Restart pywws live logging.
Many of the services will upload the last seven days of data (referred to as “catchup” mode) when first run. This may take an hour or more, but the use of separate threads means this doesn’t adversely affect the rest of pywws.
Writing your own uploader¶
If you’d like to send data to a service which is not (yet) included in pywws you can write your own uploader module and put it in your
You should start by copying one of the existing modules from pywws.service.
Choose one with an API most like the service you want to upload to.
Give the module a one word lowercase name that will be used as the uploader service name.
Testing the module is a little different from before:
python ~/weather/modules/myservice.py -vvv ~/weather/data
~/weather/modules/myservice.py is the full path of your new module.
Note what sort of response you get from the server.
Some servers, such as Weather Underground, send a single word
'success' response to indicate success, and a longer string indicating the cause of any failure.
Other servers use HTTP response codes to indicate failure.
upload_data method must return a
(bool, str) tuple where the
bool value indicates success (if
True) and the
str value contains any message from the server.
(If the server returns no message this string should be set to
Under normal operation pywws will log this message whenever it changes.
Once your uploader is working you could contribute it to pywws if it’s likely to be useful to other people. Don’t forget to document it fully, then either send it to Jim or create a GitHub pull request. See Contributing to pywws for instructions on doing this.
Comments or questions? Please subscribe to the pywws mailing list http://groups.google.com/group/pywws and let us know.