= Installation =
'''WARNING:''' Please do not use the Internet Explorer "IE" Browser to install this plugin.  There have been multiple reported problems with IE being used to upload plugins via Vera's Luup Plug installation pages.

 1. Configure the physical location of your Vera, using the ''Location'' settings UI [#point1 (1)]
 1. Download the ZIP file directly from [changeset:40/tags/1.48?old_path=%2F&format=zip Source control] 
 1. Expand the ZIP File to extract the 4x files, their names should be exactly as follows:
   * `D_Weather.xml`
   * `S_Weather.xml`
   * `I_GoogleWeather.xml`
   * `D_Weather.json`
 1. Follow the [http://wiki.micasaverde.com/index.php/Install_LUUP_Plugins Generic Installation instructions] using "`D_Weather.xml`" and a description of "Google Weather".
 1. At this point you should have a working Weather component

'''NOTES:'''
   * [=#point1 (1)] Users in France need to use the ''Location override'' parameter of this plugin, using a Location such as "`Paris,France`" ''or'' "`Nice,France`", as automatic !GeoLocation doesn't work in France.  See the ''Extras'' section below for details.

= Extras =
[[Image(WeatherDialogUI4.png, align=right, 30%)]]
Support has been added for the following Device Variables:
 *  `Location` (String) a Location override for the settings configured within Vera.[[br]]
  This can be set to any value that the Google API supports.  These options aren't officially documented by Google, but there are various websites that show examples.  You can use values like "New York, USA" (etc) and it'll override the !Lat/!Long values in the Vera's [http://wiki.micasaverde.com/index.php/Location Location] settings.
 *  `Metric` (Boolean) an override to force the calculations to produce values in Metric instead of Imperial.[[br]]
  This parameter defaults to "0" (Imperial), but can be set to Metric by changing the value to "1".  Visually, Vera will still display ("F" or "C") after the values, depending upon what has been set in Vera's [http://wiki.micasaverde.com/index.php/Location Location] settings.
 *  `Condition` (String) something representing the current Weather state.[[br]]
  From postings on the internet, this seems to have values in the list (potentially more):
  *  `Clear`
  *  `Cloudy`
  *  `Fog`
  *  `Haze`
  *  `Light rain`
  *  `Mostly Cloudy`
  *  `Overcast`
  *  `Partly Cloudy`
  *  `Rain`
  *  `Rain Showers`
  *  `Freezing Rain`
  *  `Showers`
  *  `Thunderstorm`
  *  `Isolated Thunderstorms`
  *  `Chance of Showers`
  *  `Chance of Snow`
  *  `Chance of Storm`
  *  `Mostly Sunny`
  *  `Partly Sunny`
  *  `Scattered Showers`
  *  `Sunny`
  *  `Light snow`
  *  `Snow`
  *  `Snow Showers`
  *  `Snow Storm`
  *  `Flurries`
  *  `Rain and Snow`
  *  `Ice/Snow`
  *  `Fog`
  *  `Windy`
  *  `Heavy Rain`
  *  `Drizzle`
  *  `Freezing Drizzle`



 *  `WindCondition` (String) a value like "`W at 2 mph`".
 *  `WindSpeed` (Number) a value like "`2`" extracted from the `WindCondition`, specified in Local units (either kph or mph depending upon the setting of `Metric`)
 *  `WindDirection` (String) a value like "`W`" extracted from the `WindCondition`
 *  `Period` (Number) the number of seconds to delay before automatically polling the Google Weather feed.  If blank, the default is 1800 seconds (30 minutes).  This value cannot be < 10 or > 3600.
 
Changes to the values of Variables requires a '''(Save)''' Operation to be performed in Vera after the change has been made.

= Errors =
 *  The Weather device requires [http://wiki.micasaverde.com/index.php/Location Location] data to start[[br]]
  If the Vera's Location has not been configured by the user, then the Weather plugin will not startup, and will indicate an error to the User in Vera's Device pane.
 *  The Weather device is dependent upon data from Google's Weather API[[br]]
  Through the discussion thread below we've discovered that some of the values, such as the Humidity, for a given [http://wiki.micasaverde.com/index.php/Location Location] are extrapolated from nearby Weather stations.  This process isn't 100% accurate and can lead to anomalies.  If the information that's derived from Vera's [http://wiki.micasaverde.com/index.php/Location Location] settings is not accurate enough, you can use the Weather Device's `Location` variable to override it.  You can then specify ZIP Codes (etc) to get more accurate information.
 *  The values don't display in Metric[[br]]
  Vera's luup API's, as of 1.0.900 don't support retrieval of the User-specified ''Temperature format'' in Vera's [http://wiki.micasaverde.com/index.php/Location Location] settings.  When this API is added, we can make changes to have the temperature values presented in that format.
 *  It doesn't display correctly using http://findvera.com/mobile [[br]]
  As of Vera firmware release 1.0.900 there are problems in the Mobile renditions of multiple components.  `TemperatureSensor` and `HumiditySensor` devices seem to be among those not implemented.
 * There's no Scene awareness, due to Vera Bug [http://bugs.micasaverde.com/view.php?id=1038 1038] and the related discussion [http://forum.micasaverde.com/index.php?topic=3492.0 thread]

= Releases =
 * 23-Jul-2010[[br]]
  Moved codebase to UI4 functionality
 * 3-Oct-2011[[br]]
  Published v1.44 of the code directly from source control, breaks out the discrete components of the Wind Speed (when possible)
 * 25-Mar-2012[[br]]
  Publish v1.48, move to using HTTPS