Skip to content
Branch: master
Find file Copy path
Find file Copy path
1 contributor

Users who have contributed to this file

executable file 59 lines (32 sloc) 4.61 KB

Installation Guide

Before you start it is a wise precaution to backup your databases, settings1.php and any customised files you wish to keep.

This installation guide assumes that you are already reasonably familiar with WeeWX and that it is already installed on your computer along with a webserver, php and curl. For a light-touch webserver, Lighttpd is a good choice. A good guide for installing PHP 7.0 and Lighttpd on a RaspberryPi can be found at

If you have not already done so, you must update your WeeWX installation to version 3.9.2 or later. This is required to facillitate nested copying during the skin install process. Follow the various installation type links on this page for instructions on updating.

If you are carrying out a fresh install of WeeWX, my own personal preference is to use the method ( However, this increases the chances of requiring more path edits in the configuration files. Alternatively use one of the dedicated packaged installs (,, or

  • Please familiarise yourself with the location of your WeeWX system files including your bin/user folder, skins folder and weewx.conf file. If you are unsure where to find these, please refer to the installation processes here: - which shows various WeeWX installation scenarios.

IMPORTANT. After installing PHP please make sure you install all the PHP modules appropriate for your version of PHP. Failure to due so may mean that forecasts and current conditions fail to update. This is an example for PHP7.3 modules on a Debian based distribution: -

sudo apt-get install php-cli php-fpm php-json php-pdo php-sqlite3 php-zip php-gd  php-mbstring php-curl php-xml php-pear php-bcmath
sudo apt-get install libapache2-mod-php
sudo a2enmod php7.3
sudo systemctl restart apache2

Once completed, make sure you save weewx.conf

  • If you have have the CRT extension (Cumulus Real-Time) extension installed, unless you require it for another purposes, you can remove it now. (sudo ./wee_extension --uninstall crt)

  • Download the current version of file at to your bin folder (/home/weewx/bin for a install or /usr/bin for a DEB install).

  • From the command line run the following code: -

      cd /home/weewx/bin (or cd /usr/bin)
      sudo ./wee_extension --install
  • After installation edit the weewx-conf file. Go to the [Weather34RealTime] stanza which will likely be near the end of the script. If your path to your web root is different from below, please amend the path in front of 'weewx/w34realtime.txt' accordingly.

      		filename = /var/www/html/weewx/w34realtime.txt
      		binding = loop
  • Once completed, make sure you save weewx.conf

  • Restart WeeWX.

  • After around 5min your should find that folder the weather34 folder has been created in the weewx folder. [your_path]/weewx/weather34 will now be the location of the Weather34 skin in your web server.

  • Stop WeeWX and change all files and folders recursively in the root of your server to 0775 using CHMOD and user to your Linux login name and groups to www-data using CHOWN, either via the CLI or your server Control Panel (if you employ one). I use Webmin, an open source control panel which will make your tasks much easier.


  • Restart weeWX.

  • You can now test that the template is working by opening it up in your browser. Initially you will see random demo data. Click on the menu button at the top-left corner and select settings. This will open up a web form in which you apply your own settings. Pay particular attention to the location of the w34realtime.txt file being generated on a loop cycle by weeWX. The default location is “/[html_root]/weewx/w34realtime.txt” (for example /var/www/html/weewx/w34realtime.txt).

  • For an in depth guide on configuring a remote server please refer to 'taylormia_remote_server_setup.pdf'

  • Finally re-start weewx and refresh your browser and you should see your own live weather station data. If things go wrong, check your settings carefully ensuring that the w34realtime.txt file and API keys and tokens have been correctly entered.

  • If you have any issues please raise directly with

You can’t perform that action at this time.