The store will not work correctly in the case when cookies are disabled.
Click here to learn about cookie settings.
Server LED turns on when reporting to AmbientWeather.net or Wunderground.com. Before, it only turned on with Wunderground.com.
Adds support for PM2.5 sensor.
Fixes lock up issue introduced in Version 4.5.5.
Fixes issue with Relative Pressure Correction that was introduced in Version 4.5.2.
Adds support of PM2.5 particulate air quality sensor (coming Q2 2019).
Fixes Rain Event bug.
Fixes UV Scaling Error.
Fixes issue with Daily Rain sometimes not resetting to 0.
Added normal / low battery tile.
Added Event Rain.
Reduced the number of DNS look ups to once ervery 15 minutes.
Fixed issue with rain calibration gain. This update is only required if you set your rain gain to any value other than 1.00.
Fixed issue with both outdoor sensor and Channel 1 sensor reporting as outdoor temperature and humidity for WS-0900-IP Weather Stations.
Fixed issue with barometer not reporting to WeatherUnderground for WS-0900-IP Weather Stations.
You can now add up to 8 additional wireless indoor-outdoor thermo-hygrometers (the model number of the 8-channel sensors is WH31B).
Fixes Wunderground.com reboot loop introduced in 4.4.2.
Fixes Wunderground.com bug introduced in 4.4.1.
There was a wind scaling issue introduced in Version 4.1.4. The wind speed is 0.46 actual wind speed. The work around is to choose the WS-1400-IP weather station instead of the WS-1200-IP.
The released version was pulled. There was a Wunderground.com reporting bug in the new release.
Fixes time stamp issue introduced in Version 4.3.8.
Some users have reported conditions where their ObserverIP has become totally, or partially unresponsive (or very slow) to requests for web pages by either a browser, or secondary device (such as WeatherBridge or MeteoBridge, or computer running software that “interrogates” the ObserverIP web pages). In all cases the problem would occur somewhat unpredictably, and was seen as frequent as once a week, but most often less frequently. The problem manifests as web page timeouts, seen by a browser user or by a secondary device or software. Sometimes the problem is transient, sometimes it is (semi) permanent. To recover, the only solution is a “cold restart” which can be affected by removing power from the ObserverIP for 5 seconds, or by pressing the reset button located on the rear of the ObserverIP.
The latest ObserverIP firmware, version 4.3.8, has resolved several issues that related to this problem. In the process of these fixes, we have determined, however that due to fundamental limitations in hardware and firmware, the ObserverIP is not capable of handling more than 4 simultaneous, or overlapping, web page requests without there being a possibility of the stated problem occurring.
This is not a limitation when the ObserverIP is used as advertised, either used stand alone and occasionally observed through a browser (never more than 1 overlapping request), or even if also connected to a single secondary device, provided that such a device is properly programmed to not make more than one simultaneous request. WeatherBridge and MeteoBridge, in recent firmware versions, are known to not do this and are supported secondary devices. When such secondary devices are in use, combined with a browser making requests (automatically or manually) in rapid succession, there is a small possibility of temporarily reaching over the safe limit and slow responses may occur. In such cases a cold restart may be needed.
Users that use the ObserverIP, in particular those that use secondary devices, are encouraged to upgrade to the latest firmware (version 4.3.8 or later), available on the Ambient Weather web site and to not use more than one secondary device.
Improves overall stability of uploads to Wunderground.
Removes Telnet capability.
Resolves bug introduced in 4.2.0.
Resolves bug introduced in 4.1.9.
Fixed calibration issue with WS-0800-IP only. Would always return invalid. Note that 4.1.9 had a significant bug and will be updated to 4.2.0 shortly.
In Version 4.1.0, the update timer for Wunderground.com was mistakenly changed to 60 seconds. The timer has been returned to 14 seconds for wind speed and direction.
Fixes small Wunderground formatting error. Does not impact users unless you are attempting to read the string from application you wrote.
Now supports WS-1600-IP weather station.
Minor cosmetic changes to the user interface.
Fixed bug introduced in 4.1.1 where it would not upload to AmbientWeather.net if Wunderground.com was not entered correctly.
Removed unnecessary time delay when closing connection to Wunderground.com
Fixed rain total initial condition issue after power cycle or firmware upgrade.
Improved stability and timing issues with Wunderground.com.
Fixed minor issue when Wunderground settings are left blank.
Fixed issue when Wunderground settings are left blank. The module was still trying to write to Wunderground.com when the fields were blank.
Fixed jittery temperature graph with WS-1200-IP and WS-1400-IP introduced in Version 4.0.0.
Fixed problem with outdoor LED flashing when WS-1200-IP is selected.
Fixed lost outdoor sensor reception issue introduced in Version 4.0.0.
Incorrectly displaying “invalid” for MAC address when no Wunderground.com settings are defined on the network panel.
AmbientWeather.net supports indoor and outdoor parameters with a mobile friendly interface.
Send email and text message alerts.
Features robust graphing features and data analysis.
Reduced bandwidth usage with Wunderground.com, removing some duplicate transmissions
Reduced network socket resource consumption by closing socket immediately after response from Wunderground.com. Wunderground.com is no longer contacted if the Station ID and/or Password is empty.
Time is now set from Wunderground.com whether or not a correct Station ID and Password is supplied.
Overall network traffic improvements, also resulting in more timely updates to Wunderground.com where occasionally an update interval could be missed.
Final fix for Wundeground March 1 update (see 3.1.3 and 3.1.4).
Turns off uploads to Wunderground if Station ID is blank.
Fixes bug when switching between static and DHCP. The DNS was not properly addressed.
On March 1, 2017, Amazon Web Services’ servers slowed down to requiring up to 30 seconds to open, read, write and close TCPIP sessions. This causes other tasks to slow down, and manifests itself in the indoor temperature-humidity-barometer to act sporadically, or updates to slow or completely stop. This version changes how the connection is established.
On March 1, 2017, Amazon Web Services’ servers slowed down to requiring 5 seconds to open an http session. This causes other tasks to slow down, and manifests itself in the indoor temperature-humidity-barometer to act sporadically. This version did not completely resolve this issue. See Version 3.1.4.
On January 31, 2017, Weather Underground.com migrated their data center from their offices in San Francisco to Amazon Web Services in Seattle. The firmware did not work properly if you selected a static IP address for the ObserverIP. We will need to fix this by installing Firmware Version 3.1.2.
Humidity calibration range issue was not fixed in 3.0.9. This version fixes it.
Increases calibration range for humidity from ±10% to ±50%.
Fixes issue with Port 80 being left open after an http write command. This slows down the ObserverIP connection.
Allows you to re-enter the daily, weekly, monthly and yearly rain totals, which is useful if you clean the rain gauge or replace the batteries and record false rain in the process.
Allows multiple browsers open communicating to the same IP Module (in the event you are reviewing from two different computers).
Improved update rates due to efficiency changes.
If IP connection lost for 20 minutes, resets ObserverIP.
Fixed issue with stopped Wunderground.com updates.
Fixed issue with not accepting “&” character is password.
Increased password length from 15 characters to 50 characters.
Added Rain Reset button to bottom of Live Data panel. This reset allows you to clear rain totals that may have occurred due to vibration during installation.
The sea-level barometer adjustment range was not large enough for altitudes above 1,000 feet.
If the module was powered down and up again, it would lose the Daylight Savings Time setting.