We recommend that you set up your goose by directly connecting it to a computer using the following steps:

1. Power the unit using the supplied power supply.
2. Ensure that the green power indicator is on. Soon after powering on, the green Ethernet status indicator will blink three times.
3. Connect the unit to a local system using a cross-over cable.
4. The orange Link indicator will turn on if a good link has been established. If the indicator does not light, then check the connections and/or try a new cross-over cable.
5. The unit has now been connected to a local system, it is time to setup the network card, so that the system can communicate with the unit.

1. Click on the Start button.
2. Select the Control Panel. If the control panel is not an option you may need to choose Settings -> Control Panel.
3. Click on the Network Connections icon.
4. You should now see one of more icons that represent network cards installed on your system. Choose the network card you connected the Goose to and right click it and select Properties.
5. Find and double-click Internet Protocol (TCP/IP).
6. This opens a window that shows your current network card settings. It should like similar to the window shown in Figure 2. Make a note of the current settings, so that they can be restored later.
7. Ensure that "Use the following IP address" is selected and enter the following settings in the appropriate fields.

   IP Address: 192.168.123.100
   Subnet Mask: 255.255.255.0
   Gateway: 192.168.123.1

8. You can leave the DNS fields blank. Click the OK button on the TCP/IP window to save the changes. Then click OK on the Local Area Connection window to finalize the process.

Sensors

This page shows the current value of the sensors and a graph of all the stored sensor data on a goose, this is also where it shows the webcams.

Logs

On this page you can graph your choice of sensors over your choice of a time period, this is also where you download the log data as well as clear the log data.

Display

This page allows you to set the names of your remote sensors, and choose the unit the temperatures are measured in.

Alarms

Here you can set and test your alarms for the sensors, there is an event log at the bottom of the screen that shows you the history of the alarms.

Control

This tab allows to control anything linked to the goose. Currently the only thing that is controllable from a goose is a Power Egg II.

Configuration

This tab allows you to setup many of the features of the goose including SNMP, email, user account, and IP camera.

Below are the instructions to update the firmware on the unit. These instructions can also be found in the firmware zip file.

1. Download the latest firmware for your device from: www.itwatchdogs.com/downloads.shtml
2. Connect the unit with a CROSS-OVER CABLE to the computer that will be used for the update. Trying to update a unit not directly attached to a computer MAY damage the unit and WILL VOID YOUR WARRANTY.
3. Change your Network Interface Card's (NIC) settings to the following:
   

   IP Address: 192.168.123.100
   Subnet Mask: 255.255.255.0
   Gateway: 192.168.123.1

4. If you have enabled the built-in Windows firewall or any third-party firewall, disable it before continuing.
5. Extract the zip file to an easy to find location (ie a folder on your desktop or at the root level of your hard disk)
6. Open the folder in Windows Explorer.
7. Double-click on the 'updater.exe' file and follow the on-screen instructions.
8. If everything works properly, the device should be available for use about two minutes after the update is complete.
9. Restore the NIC's previous settings once the firmware update is complete.

Should you run into any trouble while updating, please DO NOT reset your Goose. Contact ITWatchdogs at:
Phone: 512-257-1462
E-mail: support@itwatchdogs.com

Email us at support@itwatchdogs.com and we will send you a new password so you can access the goose the change the password.

• WeatherGoose unit running firmware version 2.51 or higher
• Computer with Internet Explorer 6.x or higher with Active enabled
• Windows XP/2000/Me

You can use a telephone-type RJ-12 splitter with at least four conductors per jack to expand the number of ports. You can order one from us, or use one from your parts box or your local Radio Shack. (Note that RTAF and RTAFH sensors will require an RJ-12 splitter with all six conductors per jack.) Make sure it's a straight-through splitter and not a crossover type, otherwise the signals will not be passed through correctly and the devices will not appear on the bus.

We have tested the one we sell. Other Web Cams may work, but are not supported.

The MIB for the unit can be found in two places. In the header of the unit web page, under Alternate Formats, is a link to the MIB. A copy of the MIB is also included in the firmware zip file of version 2.53 and higher.

In the zip file for firmware versions 2.53 or higher there is a CSV file that contains the list of OID's for the unit.

The Test Alarms feature can be used to turn the buzzer off remotely. The following step will lead you through this process.

1. Go to the Alarms tab.
2. Scroll down to the Test Alarms section.
3. Pick one of the internal sensors from the Sensors drop-down.
4. From the Alarm State drop-down, choose Buzzer.
5. Select Clear from the Trap Type drop-down.
6. Click on the Test button.
7. The buzzer should turn off in a few seconds.

This is not a problem, the web firmware is for the web server in the goose, but the firmware on the LCD is the firmware on the processor so they should be different.

The LCD will display anything that the logs page is set to display.

The web server on the goose is limited, and if there is higher traffic on the site, or if you try to change between tabs rapidly it will slow down while it processes the requests.

The following is a guideline for using the graph CGI query:

timerange

A negative value of -1 means all data points available. A positive values means the last N seconds of data. Values under 100 are too small to be effective and ignored by the unit.

width

This argument refers to width of the image rendered. The maximum value is 416. Values less than 1 or greater than 416 are undefined and result in undefined behavior.

height

This argument refers to the height of the image rendered. The maximum value is 300. Values less than 1 or greater than 300 are undefined and result in undefined behavior.

device

This argument includes ALL sensors from a given device into the graph. The device value must be a valid 16 character ID.

sensor-

Notice the dash after the sensor label. This argument includes a sensor from a device into the graph. The sensor- value must be a valid 16 character device ID followed by the 0-based index of the sensor of intereste. Sensor offsets to non-existant sensors result in undefined behavior.

Notes: Mixing device and sensor- arguments in the same graph CGI query may produce undefined results.

Examples:

Query all data points for all sensors in main weathergoose device
http://www.weathergoose.com/graph.bmp?width=256&height=150& timerange=-1&device=010307640B00006A

Query last 15 minutes of data points for light level sensor in main weathergoose device
http://www.weathergoose.com/graph.bmp?width=256&height=150& timerange=900&sensor-=010307640B00006A3

Query all data points for relative humidity and sound level sensors in main weathergoose device
http://www.weathergoose.com/graph.bmp?width=256&height=150& timerange=-1&sensor-=010307640B00006A1&sensor-=010307640B00006A4

You can use 3rd party software like IP Sentry or you could write a script to provide the glue logic that parses the Goose's XML and then sends the correct HTTP POST transaction to the Goose to turn on or off the controllable relay based on parsed sensor values.

Every 60 seconds, for faster refreshes please hit the refresh tab. Cameras on the page refresh every 20 seconds.

By device, so all the sensors in a Power Egg with show up on one graph, and the one sensor in an remote temperature will show up in one graph.

PDA: A small version of the Sensors page, used on PDA's and cell phones.
WAP: A special version of the Sensors page, used by WAP-enabled cell phones.
XML: The current data, along with device information, displayed in XML.
MIB: Check on this link to download the MIB for the Goose. Used in SNMP.

This error is most commonly caused when the graphing routine cannot recognize or interpret a data point correctly. At present, we are still investigating the exact cause of this, but in the meantime there is a simple workaround:

First, download your log data (only if you want to keep the data; otherwise, you can skip this step). Second, clear the unit's log history by going to the logs page, checking the clear log history box, then press the button marked save changes. Your graphs should come back in a few minutes (the exact time will depend on your logging frequency setting) once the unit has accumulated sufficient new data to begin graphing again.

This can be caused if the Goose is having trouble connecting to an NTP server. Check the time shown on the Goose's web page in the upper-left corner; if the time shown is incorrect, or the unit says no NTP service is available, this is likely to be the source of the problem. If your goose cannot access an external NTP server (due to, for example, being behind a firewall), there is software available from AdjustTime.com that will allow a PC server to act as an NTP service.

No, this page cannot be modified by an end user.

On the Logs Tab is a set of controls for the Logs graph. You can select sensors and the time span to use for the graph. The Y-axis shows the sensor values and the time is shown on the X-axis. The legend at the bottom of the graph, provides the sensor name for each color used on the graph. On the left side of the screen is a series of checkboxes, one for each sensor. To graph the sensor, make sure its box is checked. Use the Time range drop-down above the graph to adjust the time range for the graph. Click on an Update Graph button to get a new graph, when a change is made. On a unit with a LCD display the checkboxes also control which sensors will be displayed on the LCD.

To download the log history, select the "Click here to download raw log data" link. The log file is in CSV format and will be called "log.csv". This download can take quite a while, if the unit has been running for some time.

The Goose saves log data on a set interval, determined by the logging frequency. To change the frequency, edit the value in the Logging Frequency input field and click Save Changes. The acceptable range is 15 to 250 seconds. A lower frequency saves data more often, but at a cost of fewer days of saved data. The text under the graph, gives the number days that can be logged at the current logging frequency. The data log is a circular buffer. Once it fills up, old data is overwritten by the newer data.

To clear the log data, check the Delete Log History checkbox and click on the Save Changes button. In a few seconds the graphs should clear and graphing will resume in a few minutes, depending on the logging frequency.

An account level of Control or Admin Access is required to change the logging frequency or delete the log data. It will grayed out if the current access level is not high enough. To change this, do the following:

1. To change to Control access click on the Control tab. For Admin click on Configuration.
2. Enter the appropriate username/password for the appropriate account.
3. Click on the Logs tab and the Logging Frequency and Delete Log History checkbox should not longer be grayed out.

Use the Temperature drop-down box to change the unit of measurement for temperature. Then select Save Changes to finalize the change.

All the sensors are connected to a common serial bus, so if one sensor goes down they may all go down if the bad sensor "jams" the bus or refuses to release it so other devices can talk. Another thing which can make sensors appear to go offline is EM interference with the 1-wire signals; check to see if the sensor cables are routed close to something that creates a lot of EM interference such as a generator, a large motor, or a large backup-battery charger, or if the sensor wiring runs parallel to the main power cables for any equipment that draws a lot of current such as an arc-welder, air compressor, or an HVAC unit. If this is the case, try moving the sensor wiring away from these EM-interference sources, and this should fix your problem.

If this is not the case, check the environment the sensors are in to see if it is pushing them past their built-in limits. Temperatures below freezing can cause ice or condensation to form, creating shorts across the sensor terminals, which will make the sensor appear dead; also, if the temperature exceeds the range of the sensor (-4° F to 122° F) it may show up as unplugged.

If neither of these is the case, then one of the sensors could be dead. Try disconnecting all sensors from the unit,then reconnecting them one at a time until you find the one that causes the problem. Once you have isolated the faulty sensor, disconnect it, and the other sensors should work normally. Email support@itwatchdogs.com for service and support options on the faulty sensor.

The list of friendly names includes all devices that are attached to the unit as well as those that were. This way if a device is unplugged and reattached later, the settings for the device are restored. However, these unplugged sensors count toward the 16 external sensors limit. If you need to remove these to make room for other sensors, then check the "Remove all unplugged devices" checkbox and click Save Changes

From the Alarms tab you can setup the unit to notify you if a sensor's value goes outside of an acceptable range. For each sensor there is a Low Trip, High trip and Alarm State. Use the low and high trips to set the acceptable range for the sensor. If the current value of the sensor goes below the Low Trip or higher than the High Trip, or the device is unplugged the alarm is considered tripped. When the value goes back into the acceptable range or the device is reattached, the alarm is cleared. To control how you will be notified of alarm trips and clears use the Alarm State drop-down. The choices are Email, SNMP trap, Buzzer( if the unit has one), or a combination of these. One notification is sent when the alarm is tripped and another notification is sent when the alarm clears. Set the alarm state to Disabled if you do not want to set an alarm for a sensor. Make sure to click Save Changes after adjusting the alarm settings.

The goose will send 1 email when the value of the sensor exceeds the norm then 1 more email when/if the reading goes back into the norm. Example, you set the max. temperature trip to 80° F and the temperature rises to 81° F the goose will send an alarm, then if it falls to 79° F you will get an additional message saying it is happy again. If the alarm is set to 80° F and the temperature is oscillating between 79-81° F this can result in large numbers of emails being sent. To correct this set the alarm higher or lower but not where the temperature will normally fluctuation

The Test Alarms section is used to send test alarm trip and clear notifications. The following instructions describe how to use this feature.

1. Select a sensor to test from the Sensors drop-down.
2. Choose the method of notification from the Alarm State drop-down.
3. Use the Trap Type drop-down to pick between trip or clear.
4. Click the Test button to send the notification.

The Event log is a chronological list of events that have taken place on the unit. This is where errors, and warnings are listed as well as alarm notifications. The Event Log is also useful for debugging email and SNMP issues. The default logging level is Verbose. To change this use the drop-down box to select the logging level and then click Set Mode.

From this tab you are able to manipulate any control devices that might be attached to the system. For instance, a Power Egg 2 would have the status of receptacles and buttons to turn them on and off. An example of this is shown in figure 8.

The main network settings for the unit can be set in configuration. To assign the unit a static IP address, fill in the Static IP address field, Static Net Mask, and Static Gateway fields. Make sure the DHCP checkbox is uncheck if using a static IP address. The next two drop-downs let you enable/disable Telnet and SNMP. The HTTP Services drop-down lets you choose if you want to allow HTTP, HTTPS, or both. The last two input fields let you set the HTTP and HTTPS ports. The default port for HTTP is 80, and 443 for HTTPS.

For the unit to know the date, it needs to be able to connect to an NTP server. The IP address for two servers can be entered. If these fields are left blank the unit will use the default addresses of 192.5.41.40 and 192.5.41.41. To adjust the time retrieved from the NTP server for time zone and/or Daylight Savings, use the "Time zone offset from GMT" field.

Under configuration go to email. Enter the IP address of the Email server in the SMTP Server IP Address field. This needs to be in the numeric form. A named version will not work. You can ping the name of the email server to get this number. The unit needs a From address to send email. The unit can send email to up to 5 addresses. Enter these in the To fields. Using commas or semicolons to concatenate email address is not supported, so make sure to only enter one address per line. Some email servers require a POP3 connection to be made before it will accept an email via SMTP. The last three fields are used for this purpose. You can leave these blank, if this is not required by your email server. Normally, the POP3 IP address will be the same as the SMTP Server IP address.

Under configuration go to SNMP. The community string for traps can be set using the SNMP Trap Community String field. This only sets the community string for traps. Currently the unit only supports the "public" community string for SNMP requests. The unit can send SNMP traps to up to 4 addresses. Enter these in the SNMP Trap IP address fields.

Use the Name and Password section to control access to the unit. There are three levels of access. The highest is admin, which allows full access to the unit. The second level of access is Control. This allows access to the Sensors, Logs and Control tab. Control access also lets the user change the logging frequency and delete the logs from the Logs tab. The lowest access level is Read-only. The user can view the Sensors and Logs tab. At the Read-only level, the user can not change the logging frequency nor delete log history on the Logs tab.

The Goose needs to be running firmware version 2.51 or higher for DLink 950/950G to work.

1. Make sure the Camera has an IP address that the Goose can reach.
2. Use a browser to connect to the Goose.
3. Click on the Configuration tab.
4. Scroll down to the bottom of the page to find the Camera Configuration.
5. Enter the IP address of the camera in the Camera IP Address field.
6. Select the camera model using the drop-down list.
7. Click on Save Changes to save the camera configuration

Information from the fields in this section is displayed in the footer of each web page. Normally, this is information helps identify the Goose and the person responsible for its maintenance.

The first thing you should try is to update the firmware. The most recent firmware can be found at http://itwatchdogs.com/downloads.shtml. Note that all versions of the WeatherGoose -- standard, Mini, or Super -- use the same firmware update package; the firmware will automatically detect the type of device it is running on and configure itself accordingly. Installation instructions are in the file.

If this does not fix your problem, or you are already running the latest firmware version, please look through this FAQ page to see if your problem has already been covered elsewhere. If you don't find the answer here, you can send an email to support@itwatchdogs.com or call us at 1-512-257-1462 for further assistance.

1. If DHCP is enabled, the IP address for the unit may have changed. Check with the DHCP server to find out the current IP address for the unit.
2. If the IP address of the unit was changed by DHCP or by the Configuration tab, make sure to use the new IP address to connect to the unit. Even if the IP address was changed, the unit can still be reached at 192.168.123.123.
3. Check the connections to the unit and the network. The power and link indicators should both be on and stable. The activity light should blink periodically. If the power light is not on, check the connection on both ends. If the link light is out then check the network cable connections. A cross-over cable should be used for connecting directly to a computer and a straight-through should be used for connecting to a network.
4. Ensure the network card settings are appropriate for the IP address of the unit. The recommended network settings for a unit at the default IP address are:
   

   IP Address: 192.168.123.100
   Subnet Mask: 255.255.255.0
   Gateway: 192.168.123.1

5. Try to contact the unit using ping, telnet or ftp. For instance at the default IP address these commands would look like the following:
   

   ping 192.168.123.123
   telnet 192.168.123.123
   ftp 192.168.123.123

6. If the unit is not at the default IP then the correct IP address would need to be substituted for the 192.168.123.123.
7. If the unit is still unreachable, it may be on a different subnet, could be blocked by a firewall, or a proxy could be preventing access. These are networking issues beyond the scope of this document.

1. Check the Event Log for email errors. This may help diagnose the problem.
2. Make sure a numeric IP address is used for the SMTP Server IP address (and POP3 IP address if used).
3. The unit needs a From address to send an email.
4. There should only be one email address in each To field.
5. Some email servers require the POP3 fields to be filled in. If POP3 isn't required these fields should be left blank.
6. If an Exchange server is being used, then it needs to be configured to allow 3rd party emails. There is a checkbox for this purpose in the Exchange server configuration.

A SNMP manager must be configured to receive traps from the unit. Most SNMP programs have a database of traps, they are monitoring for. The possible traps that can be sent by the unit must be added to this database. Some programs can take the unit MIB and extract the trap information. With other programs the trap data has to be entered manually. A CSV file is included in the firmware zipfile of version 2.53 and higher. The CSV includes the OID's for the unit as well as the information for each trap. Below is a list of issues that might stop you from getting traps from the unit.

1. See if there are errors in the Event Log.
2. Not all SNMP software is able to receive traps. Check if the software can receive version 1 traps.
3. Make sure the IP address configured on the unit, matches the IP address of the SNMP manager.
4. Ensure that the Trap Community String on the unit, corresponds to the community string expected by the manager.
5. On some SNMP software, you have to enable trap monitoring and SNMP requests.