This skin (or theme, or template) is for the weewx weather software and is modeled after my website BelchertownWeather.com. I originally developed that website with custom coded features but always used weewx as the backend archive software. It was a good fit to remove my customizations and port the site to a weewx skin that anyone can use.

Features include:

• Real-time streaming updates on the front page of the webpage without neededing to reload the website. (weewx-mqtt extension required and an MQTT server with Websockets required.)
• Extensive graphing system with full customized control on observations, historical timescale, grouping and more. Graphs also update automatically without needing to reload the website.
• Light and Dark Mode with automatic switching based on sunset and sunrise.
• Forecast data updated every hour without needing to reload the website. (A free AerisWeather API key required. You qualify for a free key by submitting weather observations to pwsweather.)
• Information on your closest Earthquake updated automatically.
• Weather records for the current year, and for all time.
• Responsive design. Mobile and iPad landscape ready! Use your mobile phone or iPad in landscape mode as an additional live console display.
• Progressive webapp ready enabling the "Add to homescreen" option so your website feels like an app on your mobile devices.

Screenshot of light and dark modes

• Belchertown weewx skin
  • Table of Contents
  • Install weewx-belchertown
  • Requirements
    • weewx.conf
    • weewx database requirements
    • AerisWeather Forecast API (optional)
    • Forecast Units
    • Forecast Translation
    • MQTT and MQTT Websockets (optional)
    • MQTT Brokers
      • Install your own MQTT Broker
      • Use a Public Broker
  • Chart System
  • Belchertown Skin as Default Skin
  • Using Metric
  • Dark Mode Theme Options
    • Theme Override with URL Option
  • Custom CSS
  • Skin Options
    • General Options
    • MQTT Websockets (for Real Time Streaming) Options
    • Forecast Options
    • Earthquake Options
    • Social Options
  • Creating About Page and Records Page
  • Creating a sitemap.xml File
  • Add Custom Content to the Front Page
  • Translating the Skin
  • A Note About Date and Time Formatting in Your Locale
  • How to use debug
  • How to install the development version
  • Frequently Asked Questions
  • Raspberry Pi Console
    • Kiosk Page
  • Donate
  • Credits

1. Download the latest release.

2. Run the installer as below. Replace x.x with the version number that you've downloaded.

sudo wee_extension --install weewx-belchertown-x.x.tar.gz

3. Edit your weewx.conf to add the required information.

4. Tailor the skin to meet your needs using the custom option variables. There's a lot of them.

5. Restart weewx:

sudo /etc/init.d/weewx stop
sudo /etc/init.d/weewx start

6. Wait for an archive period, or run sudo wee_reports to force an update

7. Browse to your website to see the skin. It may be in a belchertown subdirectory.

These settings need to be enabled in order for the skin to work. Within weewx.conf, under [Station] make sure you have:

• latitude - used for forecasting and earthquake data
• longitude - used for forecasting and earthquake data

Belchertown assumes that the weewx database uses the 'wview-extended' schema that has been the weewx default since v4 was released in April 2020. Users whose database was created using the original wview compatible schema prior to weewx v4 may see significant performance issues processing the Belchertown skin after they upgrade to weewx v5. This is due to a change in weewx behavior in which it will now calculate elements referenced in a skin that are not in the actual weewx database.

This change in weewx behavior is documented at some length in many weewx-user google group threads and in Issue 924 (link) here. The simplest way to deal with this is to add the 'appTemp' element to your database if it is missing, or alternately run "weectl station reconfigure" and switch to the v4 and above default 'wview-extended' schema that contains the required database elements. For details and some ways to do so, please see the issue 924 link above.

AerisWeather's Forecast API is where the current observations and forecast data comes from. The skin will work without this integration, however it is used to show current weather observations and icons as well as the forecast.

You must sign up to use their service. This skin does not provide any forecast data. You need to join their website and get a free developer key. In order to get a free developer key, you have to send your weather data to pwsweather.com - which is an integration built into weewx. You just need to activate it! Once enabled, by default the skin will download and cache every hour.

• If you haven't already; sign up for pwsweather at https://www.pwsweather.com/register
• Add a new station, and configure your weewx.conf to start sending your weather data to pwsweather.
• Then sign up for a free AerisWeather developer account by linking your pwsweather account here https://www.aerisweather.com/signup/pws
• Once you are logged in, you should make a Demo Project as part of the sign up process, then go to https://www.aerisweather.com/account/apps and and save these keys as forecast_api_id and forecast_api_secret.
• The rest of the options can be found below in the Forecast Options table.

DarkSky has been shut down, but if you still have an API key, you can continue using it until DarkSky shuts your API key down.

AerisWeather provides all units in 1 API call which is great but the skin still needs a way to determine what units you want it to show. This is why I've decided to keep the Dark Sky unit method so you can determine which units you'd like AerisWeather to show. All of the unit determination is now being done within the skin, not the API.

Here's the differences and what's available.

• us: Imperial units (the default)
• ca: same as si, except that wind speed and wind gust are in kilometers per hour
• uk2: same as si, except that visibility is in miles, and wind speed and wind gust in miles per hour
• si: SI units

SI units are as follows:

• chance of precipitation: Centimeters.
• temperature: Degrees Celsius.
• temperature min: Degrees Celsius.
• temperature max: Degrees Celsius.
• wind speed: Meters per second.
• wind gust: Meters per second.
• visibility: Kilometers.

AerisWeather provides the observations in "weather codes" which allows you to translate these codes to your language. Take a look at the skin.conf and all the forecast_ labels. As with anything in skin.conf, it's advised to copy this to weewx.conf so your changes aren't lost on upgrades. See how to do this in the Translating the Skin section.

MQTT is a publish / subscribe system. Mostly used for IoT devices, but it works great for a live weather website.

MQTT Websockets allows websites such as this to connect to the MQTT broker to subscribe to a topic and get updates.

You will need to use an MQTT broker (aka server) to publish your data to. You can install your own broker pretty easily, or use a public one (some free, some paid).

Your weewx server will publish it's weather data to a broker (using the weewx-mqtt extension) and visitors to your website will subscribe to those updates using MQTT Websockets built in to this skin. When data is published the subscribers get that data immediately by way of the website updating without reloading.

With the weewx-mqtt extension installed, everytime weewx generates a LOOP it'll automatically publish that data to MQTT which will update your website in real time. Once ARCHIVE is published, your website will reload the forecast data, earthquake data and graphs automatically.

A sample weewx-MQTT extension config is below. Update the server_url, topic, and unit_system to suit your needs. Keep binding as archive and loop. Remove the tls section if your broker is not using SSL/TLS. Update the unit_system if needed.

    [[MQTT]]
        server_url = mqtt://username:password@mqtt.hostname:port/
        topic = the/topic/to/publish/to
        unit_system = US
        binding = archive, loop
        aggregation = aggregate
        [[[tls]]]
            tls_version = tlsv1
            ca_certs = /etc/ssl/certs/ca-certificates.crt

Note: I did not write the MQTT extension, so please direct any questions or problems about it to the user forums.

If you want to run your own MQTT broker, you can follow these instructions that I've put together.

Setting up an MQTT server on DigitalOcean is quick and easy. BelchertownWeather.com runs on DigitalOcean. Click this referral link to get started on DigitalOcean with a free credit!

These public brokers have been tested as working with MQTT and Websockets. If you have others to add the to the list, let me know.

• HiveMQ Public Broker
• test.mosquitto.org
• You can also try some from this list

Starting in version 1.0 you have full control over the charts. Version 1.0 comes with 4 charts by default to get you started. There are so many options and things you can do that it's best to read the Chart Wiki Page.

This is what worked for me to make Belchertown the default skin for your site. This is an example config and may need a little fine-tuning site-per-site.

I changed it so the standard skin would be in a subfolder, and the main folder has my skin files. So when you go to my website you're seeing the Belchertown skin, with the default skin under /weewx.

1. Edit weewx.conf, then look for [StdReport] and under it change HTML_ROOT to be /var/www/html/weewx. Note, your HTML directory may be /home/weewx/public_html, so you'd want /home/weewx/public_html/weewx.

2. Then modify the Belchertown skin options with these minimal updates. Note, you may need to change the path as mentioned above.

    [[Belchertown]]
        HTML_ROOT = /var/www/html
        skin = Belchertown

3. This is optional, but advised: Delete all contents of the HTML_ROOT folder and let Belchertown create an entire new site. This prevents stale duplicate data.

4. Restart weewx and let it generate the files upon the next archive interval.

If you want to use metric units in your website,you can display the metric values in the skin. Just like with the Standard weewx skins, there are group units available to switch to.

If your weewx version is 3.9.1 or newer, to change your site to metric you would modify weewx.conf [StdReport] section. Here's an example:

[StdReport]
    [[Defaults]]
        [[[Units]]]
            [[[[Groups]]]]
                group_altitude = meter
                group_degree_day = degree_C_day
                group_pressure = mbar
                group_distance = km
                group_rain = mm
                group_rainrate = mm_per_hour
                group_speed = meter_per_second
                group_speed2 = meter_per_second2
                group_temperature = degree_C

Restart weewx when you've made these changes.

If your weewx version is older than 3.9.1 (not recommended), to change the site to metric you would need a configuration in weewx.conf, like below. Restart weewx when you have made the changes.

[StdReport]
    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = belchertown
        [[[Units]]]
            [[[[Groups]]]]
                group_altitude = meter
                group_degree_day = degree_C_day
                group_pressure = mbar
                group_rain = mm
                group_rainrate = mm_per_hour
                group_speed = meter_per_second
                group_speed2 = meter_per_second2
                group_temperature = degree_C

There are 3 options for a theme with the skin. Dark, Light and Auto modes. Dark mode will set your site in dark mode always. Light mode will set your site in light mode always. Auto mode will use the sunset, and sunrise times in your location (based on latitude, longitude in your weewx.conf) to automatically change the website from light to dark. Automatic dark mode happens at the sunset hour and automatic light mode happens at the sunrise hour.

At the top of the website next to the menu bar is a toggle button. This will toggle the site from light to dark modes.

A note about auto mode, and the toggle slider: If you have auto mode enabled for your site, and a visitor clicks the toggle slider, auto mode is disabled for that visitor for their session. To have the visitor restore auto mode, they will need to close the tab and re-open the tab.

This way when a visitor is on your site and they don't want auto mode but want dark mode always, by using the toggle button to go dark mode 100% it will keep the site on dark mode even after sunrise. Same idea for light mode if a visitor wants only light mode. Visitors can override your auto setting using the toggle switch. Closing the tab or the browser, or adding ?theme=auto to the end of your URL will remove this override if the visitor wants to go back to auto mode.

You can also override the theme using a URL setting. Simply add ?theme=dark or ?theme=light at the end of the website URL to force a theme. For example: https://belchertownweather.com/?theme=dark will force my website to dark mode. Using a URL override will also disable auto theme mode. To reset back to normal auto theme mode, you can add ?theme=auto to the URL, or the tab or browser must be closed and re-opened.

If you have custom CSS you want to persist across upgrades, simply create a custom.css file in your HTML_DIR. Any overrides here will be present on the site right away and will persist across upgrades of the skin.

The Belchertown skin will work as a very basic skin once installed using the default values in the table below.

To override a default setting add the setting name and value to the Extras section for the skin by opening weewx.conf and look for [StdReport]. Under will be [[Belchertown]]. Add [[[Extras]]] (with 3 brackets) and then add your values. For example:

[StdReport]
    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = belchertown
        [[[Extras]]]
            logo_image = "https://belchertownweather.com/images/content/btownwx-logo-slim.png"
            footer_copyright_text = "BelchertownWeather.com"
            forecast_enabled = 1
            forecast_api_id = "your_id"
            forecast_api_secret = "your_secret_key"
            earthquake_enabled = 1
            earthquake_server = USGS
            twitter_enabled = 1

The benefit to adding these values to weewx.conf is that they persist after skin upgrades, whereas skin.conf could get replaced on skin upgrades. Always have a backup of weewx.conf and skin.conf just in case!

Restart weewx once you add your custom options and wait for an archive period to see the results.

For ease of readability I have broken them out into separate tables. However you just add the overrides to the config just like the example above.

These are the options for the social media sharing section at the top right of each page. This does not link your site to anything, instead it gives your visitors a way to spread the word about your page on social media.

The About Page and Records Page offer some areas for custom HTML to be run. To create or edit these pages, go to the skins/Belchertown folder. These files should not be overwritten during skin upgrdades, but it's always best to have a backup just in case!

• Create (or edit) the skins/Belchertown/about.inc and skins/Belchertown/records.inc files with your text editor, such as Notepad or Nano.
  • These files take full HTML, so you can get fancy if you want.
  • You can view, and use the sample file about.inc.example and records.inc.example. Just rename to remove the .example, edit and you should be good to go.
• Wait for an archive interval for the pages to be generated.

Sitemap files are part of the SEO strategy which helps the Search Engine crawlers index your site more efficiently. The result (in addition with other SEO practices) helps visitors find your website through web searches.

Currently with the way that weewx creates websites there is no built-in method which can create a sitemap file automatically.

I have forked and updated a sitemap generator script which will crawl your website and generate the sitemap.xml for you. Run it on the same server as your webserver, and add it to your crontab for automatic sitemap.xml updates.

There's also the option to use one of the many online sitemap.xml generator tools to create one for you. They will do the same thing by crawling your website and creating a sitemap.xml file that you download and place into your HTML_ROOT directory.

Note: Since the NOAA reports update frequently, you may need to determine a process that works for you to update the sitemap.xml if SEO is important to you.

You can then submit the full URL to your sitemap to search engine tools. Example:

• Google
• Bing
• Yandex
• Baidu

Then insert the following line at the bottom of the skins/Belchertown/robots.txt file, specifying the URL path to your sitemap.

Sitemap: http://YOURWEBSITE/sitemap.xml

Restart weewx for the changes to robots.txt to update.

There are 4 locations on the front page where you can add your own content. Full HTML is supported. To add content, create a new file in skins/Belchertown with the naming convention below. Wait for an archive period for the content to update.

• Below the station info: skins/Belchertown/index_hook_after_station_info.inc
• Below the forecast: skins/Belchertown/index_hook_after_forecast.inc
• Below the records snapshot: skins/Belchertown/index_hook_after_snapshot.inc
• Below the charts: skins/belchertown/index_hook_after_charts.inc

Check out this visual representation:

The skin uses the "default labels" for every text and title on the page. This allows you to translate, or simply just change the words to something else easily. You can either edit the [Labels] [[Generic]] section within skin.conf, or (preferred) copy these labels to your [Belchertown] skin settings within weewx.conf's. If you edit them within skin.conf, your changes will be lost on upgrades. Here is a sample weewx.conf config:

    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = belchertown
        [[[Extras]]]
            forecast_enabled = 1
            ... other Extras options here ...
        [[[Labels]]]
            [[[[Generic]]]]
                home_page_header = "Belchertown Weather Conditions"
                twitter_owner = PatOBrienPhoto
                twitter_hashtags = "PWS #weewx #weather #wx"
                rain = My Custom Rain Label
                graphs_page_day_button = Today

In version 0.9 of the skin I decided to move most of the date and time formats to moment.js using JavaScript. You can read my thoughts, comments and commits here. I feel that moment.js formats the date and time a lot more elegantly than Python. There are so many areas in this skin that use date and time that I've made the decision to let moment.js format these automatically based on your server's locale and timezone.

You can modify the moment.js string formats using the skin.conf Labels section and look for the moment.js section beneath. For a list of all string formats that moment.js can use, check https://momentjs.com/docs/#/parsing/string-format/

If you notice that there are date, time and timezone formatting that looks wrong for your locale, you can set the proper locale and timezone on your weewx server, and restart your server, or don't use moment.js locale aware string formats and use a manual definition instead. For example if you want Wednesday 15 May 20:25 you would use this formatting: dddd DD MMM HH:mm.

Explanation (this comes right from the moment.js documentation):

• dddd gives you full day name, like Saturday. ddd would give you short day name like Sat
• DD would give you the day's date as a number with a leading 0, like 05. If you want just 5 it would be D
• MMM gives you the short name of the month like "Jan". If you want "January" it'd be MMMM
• HH is the hour in 24 hour format with a leading 0, like 02. If you don't want the leading 0 it would be H.
• mm is the minute with a leading 0, like 08. If you don't want the leading 0, use m.

Belchertown skin comes with a smaller website tailored for the Raspberry Pi 3.5" TFT screen. I personally use this as a second console, and it works great. When used with MQTT Websockets, the timeout is disabled by default so it's always connected. If there's a connection error, the Pi page will keep retrying to connect to the MQTT Websocket server. This means once you're setup you can set it and forget it.

If you're interested in this type of setup, you'll need these items:

• A Raspberry Pi. I'm using the Raspberry Pi 3 B+ model
• An SD Card for your Raspberry Pi
• The Adafruit 3.5" Raspberry Pi TFT Screen Hat (other models may work, your experience may vary)
• Get the Raspberry Pi setup with the easy NOOBS installer and get it updated.
• Once it's setup and the screen is also setup run this tutorial for getting it into Kiosk mode.
• Point your new Raspberry Pi Kiosk to your weather website's /pi page, and you should be good to go!

The Kiosk page is similar to the Pi Console page, but with a bit more information, as it is designed to be displayed on a 1280x800 resolution screen. It can be run from the display of Raspberry Pi (connected via HDMI), a laptop, or as part of a "Home Information Center". Just like the Pi Console page, when used with MQTT Websockets, the timeout is disabled by default.

It looks similar to the layout of the homepage, but the only has the current observations, and forecast, as it is designed for a 1280x800 resolution screen. As such, does not include the navigation bar, logo, the header.inc file, or any charts. The index_hook_after_*.inc checks are also commented out, remove the comment markers from kiosk.html.tmpl if you wish to re-enabled them.

To have a Raspberry Pi display this page on reboot, you can either follow the tutorial above, or put the following into /home/pi/.config/lxsession/LXDE-pi/autostart if running the desktop version (or have lxde installed on the lite version) of Raspberry Pi OS.

@sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' /home/pi/.config/chromium/Default/Preferences
@sed -i 's/"exit_type":"Crashed"/"exit_type":"Normal"/' /home/pi/.config/chromium/Default/Preferences
@chromium-browser --start-fullscreen --kiosk --disable-site-isolation-trials --enable-low-end-device-mode --renderer-process-limit=2 --app=http[s]://<localhost|hostname|IP>/[path_to_skin/]kiosk.html
@unclutter -idle 0.1

For the most part, the Kiosk page will follow the same settings as the main homepage. Below are the settings specific to the Kiosk page, they go under the [Extras] section of the skin config in weewx.conf.

It is also suggested, if you are going to display the inside temperature and humidity, to shorten the labels for inTemp and inHumidity.

    [[[Labels]]]
        [[[[Generic]]]]
            inTemp = In Temp
            inHumidity = In Humid

Debug information will show a lot of useful information for troubleshooting a problem. Information such as MQTT messages, to skin theme and time settings to re-creating a chart for external debugging. If you need to use debug to find a problem with the skin, there are 2 ways to do this.

1. Preferred method: Add /?debug=true to your website's URL to enable it on adhoc. Example: http://example.com/?debug=true
2. Set the skin option belchertown_debug to 1 and restart weewx.

In both cases, you'll need to open the browsers console to find the debug information. Refer to this to find the developer console for your browser.

If you want to try out the latest features the skin has to offer, you can install the master branch. To start download the master zip file. Then you can

1. upload it to your weewx system and install it using wee_extension --install master.zip

or

2. manually replace the files from the zip file with your weewx Belchertown skin files.

Either way, we need to overwrite your current Belchertown skin install in the skins folder and the bin/user foler with the development files. Then you can configure the new features you want and restart weewx when done.

• Q: How do I change my site title and page headers? I don't want to be called "My Weather Website"...
• A: As of version 1.0, the skin has a lot of labels which are used for Translating the Skin. As a result certain Extras options which were all text are now under Labels so that they are more in line with the other text items which can be translated. Take a look in skin.conf and you'll find all the text items which can be translated under Labels --> Generic. My advice would be to copy the labels you want to change to weewx.conf under [Belchertown] so that they are not lost during upgrades since skin.conf gets erased and reinstalled on upgrades. Here's how you do that in weewx.conf:

    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = belchertown
        [[[Extras]]]
            forecast_enabled = 1
            ... other Extras options here ...
        [[[Labels]]]
            [[[[Generic]]]]
                home_page_header = "Belchertown Weather Conditions"
                twitter_owner = PatOBrienPhoto
                twitter_hashtags = "PWS #weewx #weather #wx"
                rain = My Custom Rain Label
                graphs_page_day_button = Today

• Q: My units are wrong in the station observation or other MQTT enabled field.
• A: You need to configure your MQTT extension to send the units you want. For example if you're using METRIC and your rain in MQTT is in centimeters, but you want to show rain as MM, you need to use the code below as an example:

[[MQTT]]
        [[[inputs]]]
                [[[[dayRain]]]]
                        name = dayRain_mm
                        units = mm

• Q: How do I make this skin my default website?
• A: Click here to take a look at this section of the readme file which explains how to set this up.

• Q: My NOAA reports are blank.
• A: If this is right after you installed the skin, give weewx an archive interval (or two, or three...) in order to populate this data

• Q: I see errors like these:
  • No such file or directory '/home/weewx/skins/Belchertown/about.inc'
  • No such file or directory '/home/weewx/skins/Belchertown/records.inc'
• A: You probably skipped the step Creating About Page and Records Page. Please give that a try.

• Q: Do I have to use MQTT?
• A: Nope! If you disable the MQTT option, then weewx will still create a website for you, it just will be done on the archive interval. weewx will still generate these pages for you if you have MQTT enabled, the benefit is that you do not have to reload the website.

• Q: What MQTT broker should I use?
• A: Check the MQTT Brokers section of this page which has more information on a free one that works, as well as running your own secure broker. If you want to use a free one, there are a number of them out there and they all have different limitations. Check their terms to make sure it will suite your needs.

• Q: Do I have to use forecasts?
• A: You do not need to use forecasts, but it is recommended to use forecasts so you take advantage of the theme's design with icons and observations.

• Q: Do I have to use earthquake data?
• A: Nope! If you leave it disabled, it won't show on the site nor will any data be downloaded.

• Q: Do I have to use the radar?
• A: Nope! If you leave it disabled you'll just have a big blank box on the website. But windy.com provides a free animated radar, so why not include it? :)

• Q: Do I have to use the graphs?
• A: Nope! If you have it disabled we will hide those portions of the site. It comes packaged with this theme already though, so you can leave it enabled.

• Q: Why does the skin take a while to generate sometimes?
• A: This is because of the graph system. That file goes through your archive's day, week, month and year values, and all time values to generate the graphs. Depending on how big your database, and how slow your system is (like a Raspberry Pi) is this could take a little longer. If you want to speed it up you can disable the charts or upgrade to better hardware.

• Q: How come the forecast's "Last Updated" time jumps when I load the page?
• A: This is because the page loads with the default Python's format for your locale. When it connects to MQTT websockets, moment.js updates that timestamp to it's format of your locale. This locale format fragmentation is hard to avoid when using locale formatting.

• Q: I noticed my graphs don't update right away on an archive period. How come?
• A: Because the highcharts can take a few extra seconds, I've put in a 30 second delay on the graphs automatic update. This way it's loading the newest data.

• Q: Do the charts on the Graphs page update automatically with MQTT?
• A: No, only the front page is automatically updated. All the other pages are normal pages that need to be refreshed to see new information.

• Q: How do I change my about page, or records page?
• A: See above on how to do that.

• Q: How can I tell if the skin downloaded new forecast or earthquake data?
• A: Check your system log file. You should see the skin output something along the lines of "New forecast file downloaded" or "New earthquake file downloaded". It will also display errors and what the error was if there was a failure.

• Q: How come I'm seeing NAN in some areas?
• A: This is because weewx hasn't gathered enough data from your station yet. Give it a few more archive intervals.

• Q: I'm seeing cheetahgenerator: **** Reason: could not convert string to float: N/A, how do I fix this?
• A: Upgrade to 0.8.1 or newer which resolves this error

• Q: How do I uninstall this skin?
• A: sudo wee_extension --uninstall Belchertown

• Q: Why is Belchertown so slow after upgrading to weewx v5 ?
• A: See above.

This project took a lot of coffee to create. If you enjoy this skin and find some value from it, click here to buy me another cup of coffee :)

• AerisWeather API for current weather conditions and weather forecasts.
• Windy.com for the iFrame embedded weather radar.
• Bootswatch Darkly for the Bootstrap dark mode.
• Highcharts Dark Unica CSS for the Highcharts dark mode.
• Gary for the initial Highcharts help from skin version 0.1 through to 0.9.1.
• Brian at weather34.com for the weather icons from the simplicty 2015 theme. Used with agreement.
• Some icons remixed by michaelundwd. Thanks!