|
|
SUMMARYThis technical note discusses some of the issues that you be aware of when using weather data. This is intended to supplement and not replace the information contained in the HCA User Guide Appendix 10. You must have already read Appendix 10 before you read this technical note or you will be confused!
Using weather dataOnce HCA has obtained weather data, you can use that data in one of two ways. The first is the weather test visual programmer element. This is fully described in the HCA User Guide Weather appendix. The other method is to use the Compute element with the _weather functions. As described in the HCA User Guide Expressions chapter the _weather function looks like this: _weather (itemName) What are valid item names? And what type of data does it produce: a number, date, time, or string? All these questions are answered in an Excel worksheet - named WeatherKeys.xls - that we prepared. It can be downloaded from here. The start of this table looks like this:
In the keyword column are the exact strings that you would use in the _weather function. For example: _weather(insideTemp) The other columns are:
Lets take an example weather item and see what this table tells us. The weather item we will focus on for this is example is WindGust. Let's assume that you are using the Davis WeatherLink II station.
As we said before, some data comes direct from the station and some data is computed by HCA. Where does WindGust come from? To answer this, look in weatherKeys.xls. There is a row for each weather item. There are columns for each weather provider (columns C to H). Find the row with the key you care about and look in the column for your provider. If there is an "x" in that cell you can get that data directly from your weather provider so you can use it in the _weather function. WindGust is supported by the METAR, WDisplay, and VWS providers but not by the directly connected WeatherLink II. Since that is the unit you have, it can't be used in the _weather function in your design. Next question: Can windGust be used in a _weatherHigh, _weatherLow, etc. function? To answer that, look in the Wind Gust row and the "Put in database?" column (column I). If there is an "x" in that cell you can use that weather item in one of the historical weather functions. In this case the cell is blank so you can't use WindGust with _weatherHigh or _weatherLow.
If we repeat the same lookup with WindSpeed
you can see that the Weather Monitor II
Metar weather dataAs described in the appendix 10, you can read weather data periodically from the internet. The one piece of information you will need to configure this is the four letter station identifier of the station you want to read data from. This is found by poking around on this web site: http://www2.faa.gov/asos/map/map.htm Here are some tips for setting up METAR data retrieval. When you go to the station map by the link given above
and drill down to your
state, make sure that you click through to the station
you selected and see if the data displayed is reasonably current.
Sometime station you selected is not
operational. c:\Program Files\Home Control
Assistant\Logs This retrieval was very fast. Sometimes the FTP action can take quite a while. The NOAA servers can be swamped at times. Finally, as you examine the weather data in the log, you will see observation times in what is know as Universal Coordinated Time, also called Zulu time. Converting to local time is sometimes confusing. These web pages will help you do the conversions. http://www.nwhiker.com/timeconversion3.html http://www.nwhiker.com/timeconversion2.html If you are having problems with internet retrieval, make sure that it is not something in your internet connection. One user recently traced his problem down to out-of-date firmware in his Linksys router. Once he upgraded the firmware to the latest available all his problems were solved. Third party weather programsIf you have a Davis Instruments weather station you can work with it in one of two ways:
While method #1 sounds like the simplest, it has several limitations. The first is that while HCA is talking to the weather station, no other program can. There are a lots of things to do with weather data beyond what you use it for in your automation solution. HCA is not a weather program. So working in this way you may not get the most out of your weather station. The other problem is that, in the Davis case, there are some sensor data that HCA can't retrieve when directly connected. For example, the soil and leaf sensors, and the secondary temperature and humidity sensors. If you use method #2, you will be able to use your weather station for, well, weather stuff. Also you will be able to retrieve all the sensor data from it. What if you don't have a Davis Weather Station? In this case you can't use method #1, but you can use method #2. Let's say that in another way: If you have almost any weather station you can have HCA use weather data from it. What you must do is to have a program that talks to that kind of station, and to periodically produce an export file with the weather data. There are three programs that HCA supports. WeatherLink
|