v4.1.3

December 27, 2013

• Resolved an issue that could prevent network settings from saving with certain combinations of subnet mask entries.
• Updated field size limits for High and Low thresholds on Analog Sensors.
• Updated field size limits for Adjust on Analog Sensors.
• Resolved some issues with Adjust values for Humidity Sensors that could cause entries to be rounded.
• Resolved an issue that could cause custom values calculated from analog sensors to be displayed incorrectly in email alert messages.
• Improved the validation performed on entries made on the Settings pages to prevent errors saving configuration changes.
• Resolved an issue that could cause the internal temperature reading to be too high when Heat Index was enabled.
• Updated the factory default process to reset the Auto Negotiate settings to the default value.

v4.1.2

November 25, 2013

• Resolved an issue that could prevent high and low humidity thresholds from being saved.
• Resolved an issue that could prevent sensor labels and thresholds from saving for Temperature & Analog Sensors.
• Added an ID to the ‘Accept Changes’ button to help facilitate automated unit testing.
• Updated the Network Settings page to require users to enable at least one of the available Auto Configuration Methods if ‘Obtain IP Address Automatically’ is selected.
• Resolved an issue that could cause AVTECH.com to appear in the inner frame of the Settings page if the AVTECH.com link was clicked in the page footer.
• Resolved an issue that could cause the ‘Adjust’ to be calculated incorrectly if a negative number was entered for internal and external temperature sensors.

v4.1.1

August 30, 2013

• Resolved an issue that could prevent the accurate calculation of custom values for analog sensors that could have negative readings.

v4.1.0

August 23, 2013

• Added support for AVTECH’s new Digital Temperature & Analog Sensor. This new sensor is compatible with all Room Alert products and allows users to monitor temperatures and analog voltages between 0-5VDC. This greatly increases the types of sensors that can be monitored by Room Alert as there are many third party sensors that output 0-5VDC readings.
• Added support for Internet Explorer 9 and 10 (IE9 and IE10).
• Tested and confirmed compatibility with all current popular browsers, including Google Chrome, Mozilla Firefox, Internet Explorer and Safari.

v4.0.1

March 9, 2012

• Resolved an issue that could cause the values for voltage on a Digital Power Sensor to be scaled improperly.
• Resolved an issue that could cause sensor values to not be returned properly when queried via SNMP.

v4.0.0

February 27, 2012

• Added support for all modern web browsers. The Room Alert web interface should now be fully functional in all web browsers, including IE8/9, Firefox, Chrome, Safari, Opera and others that conform to modern web standards. With full support for Chrome and Safari, the web interface can now also be viewed in mobile devices running Android and iOS.
• Added support for the new ‘Push’ technology for use with Device ManageR. Previously, Device ManageR would query the device for sensor values at defined intervals. If the device was installed at a remote location, this could cause additional configuration steps because of firewalls that might be in place between locations. The new ‘Push’ technology allows users to configure Room Alert to proactively send sensor updates to Device ManageR at regular intervals. Since Room Alert will be sending data out to Device ManageR, firewall configurations can typically be simpler since outgoing connections are usually allowed. In addition, if Room Alert detects an alarm condition, it will immediately send an update to Device ManageR, regardless of the interval setting. This allows for more immediate notification of alarm conditions that is no longer tied to the Discovery Interval configured in Device ManageR. Please contact AVTECH for additional details about this exciting new feature.
• Updated the core embedded operating system and network drivers. This should improve the communication between our Room Alert devices and high end network switches to improve interoperability.
• Added support for the JSONP protocol. This makes it much easier for users to incorporate sensor data from Room Alert devices into their own web pages without the challenges previously posed by cross-domain scripting restrictions.
• Updated the sensor output to conform to valid JSON formats.
• Added the ability to configure the date format displayed on the web interface and in email notifications to allow for customization in different international locales.
• Improved the way time is displayed in email notifications to more fully conform to the RFC standard.
• Added timestamps to the trace output to make it easier for our Technical Support team to identify the timing of certain background activities to facilitate quicker resolutions.

v3.4.1

August 23, 2010

• Resolved an issue that could cause the Heat Index to be calculated incorrectly when the humidity or temperature was too low.
• Resolved an issue that could prevent a valid 0 Volt reading from being applied as the low reading for the Digital Power Sensor.
• Resolved an issue that could cause alerts for the internal Temp/Humidity Sensor to not be triggered or cleared properly.
• Resolved an issue that could cause valid ‘0’ readings to not be applied to the High or Low values.
• Added the ability to disable periodic Gratuitous ARP packets from being sent.
• Added a new feature that allows the Room Alert 24E to optionally automatically synchronize the date and time with the configured NTP server at regular intervals. Available intervals include 10 minutes, 60 minutes and 6, 12 and 24 hours.
• Added current sensor values to SNMP Trap messages.

v3.3.0

February 11, 2010

• Resolved an issue that could cause Digital Power Sensors to report false 0V alarms that would immediately clear. Most of these false readings are now properly filtered out.
• Added additional false alarm checking to all Digital Power Sensor readings.
• Increased the size of internal variables used for email messages to prevent possible overruns due to longer email messages.
• Improved the formatting of the date and time sent in the headers of email alerts to prevent some email clients from interpreting the date incorrectly.
• Added the ability to configure the timeout value used for email communication on the ‘SMTP Email’ screen in Settings. The default value is 5 seconds and the setting supports values from 1-99 seconds.
• Resolved an issue that could cause unexpected behavior if sensor data was not parsed properly.

v3.2.1

April 9, 2009

• Added the ability to modify the port used for HTTP requests. This was previously hard-coded to use port 80.
• Added the ability to modify the URL that is displayed at the bottom of email alert notifications. This allows users to define a WAN IP or DNS name so the link can be clicked and viewed from outside the local network if external access is configured.

v3.2.0

March 3, 2009

• Improved the progress bar used when saving setting via the web interface. It is now smoother and more accurately represents the current status of the setting save and device reboot.
• Improved false alarm checking for Digital Power Sensors. This will result in increased accuracy and reduced invalid spikes that can interfere with accurate high and low values, logging and graphing. This improved false alarm checking will also reduce the number of alert emails sent for invalid spikes.
• Added support for decimal ‘Adjust’ values to be used to calibrate temperature sensor values.
• Added a progress bar to the initial settings page load to allow the settings to be read properly from the device before displaying the configuration page. This should eliminate the occasional error loading settings from the device.
• Modified the SMTP email process to recognize the last response code sent instead of the first. This resolves an issue that could occur with some email servers that sent back more data in the response than expected.

v3.1.3

January 13, 2009

• Resolved an issue that could cause Digital Power Sensor alarms to occur incorrectly if there was an error retrieving sensor data.
• Improved the formatting of the timestamp used when sending email messages so it is correctly interpreted by most mail servers in most locales.

v3.1.2

December 23, 2008

• Added the ability to define and save the default refresh interval of the Status page via the Advanced section of the Settings.
• Resolved an issue that could cause the dates of December 29, 30 and 31 to be calculated incorrectly. These dates should all display properly with this version.
• Corrected a slight pixel offset issue on the Status page that could appear in some browsers.

v3.1.1

December 10, 2008

• Resolved an issue that could cause sensor data to momentarily freeze for a period of time.
• Addressed an issue that could cause false alarms from Digital Power Sensors that were not connected at the time.

v3.1.0

November 14, 2008

• Improved the speed of sensor data processing which will result in slightly faster threshold checking and alarm triggering.
• Added an option to the telnet configuration menu to allow users to configure the level of desired false alarm checking when processing switch sensor alarms.
  • By default, a switch sensor needs to be in an alarm state for 3 consecutive scans before triggering an alarm. This is now configurable from 0 to 5 scans before triggering an alarm.
• Changed the default MTU setting to 1024 instead of 1400. This should reduce the occurrence of network connectivity issues when connected to managed switches that drop packets that do not match the stated MSS request.
• Added additional error checking to SMTP requests to better diagnose email sending issues.

v3.0.3

September 19, 2008

• Updated fields and labels on the Settings screens to be consistent across all screens and options.
• Resolved an issue that could cause Digital Power Sensors to not send alarms if unplugged from main power.
• Increased the maximum voltage allowed for a Digital Power Sensor to 255VAC from 250VAC.
• Added a timeout check to the SMTP sending function so a communication loss with the mail server does not cause the unit to stall while waiting for a response.
• Added support for displaying the ‘Heat Index’ value in Celsius in addition to the default of Fahrenheit.
• Added switch sensor initialization checks to prevent false alarms from being sent when the unit first boots.
• Added an ‘Uptime’ value to the trace output as a way to determine how long the device has been powered on.

v3.0.2

June 20, 2008

• Combined the Email Server IP and Domain Name fields into a single field in the SMTP Email Settings Screen.
  • It will now automatically determine whether an IP address or a domain name was entered and use the appropriate method to send the email.
  • This previously caused an issue if a user entered a local IP address for their mail server and also added a domain name. In this situation, Room Alert 24E would attempt to resolve the IP address from the domain name instead of using the configured local IP address.
• Resolved an issue that could cause the value entered in the ‘Adjust’ field to change values due to incorrect rounding on sequential Sensor Settings saves.
• Resolved an issue that could cause email messages to fail to send if the mail server replies with a long response to the EHLO command.
  • We now check for a 250 response indicating it is ‘OK’ to send and discard the remaining unused message.
• Resolved an issue that could cause email messages to fail to send if the mail server responded with an alternative error code to the EHLO command.
  • We now correctly fall back to using HELO if the initial EHLO attempt fails and returns a code other than the 250 ‘OK’ message.
• Added a status message when sensor labels are saved so a blank web page does not display before the ‘Saving…’ progress bar.

v3.0.1

May 2, 2008

• Resolved an issue that could cause SNMP Queries to stop responding after a period of time. The SNMP Community Name passed from the SNMP client was sometimes interpreted incorrectly resulting in an ‘Access Denied’ error.
• Resolved an issue that could cause the MTU setting to not be applied correctly, preventing web access over VPN and other secure protocols.
  • MTU settings from 512 to 1400 can now be configured for users experiencing an issue viewing the web interface over a VPN connection.
• Resolved an issue that caused SNMP Trap messages to always be sent with a ‘public’ community string instead of the configured SNMP Community Name.
• Added a ‘View Tracing Output’ option to the Advanced Settings screen.
  • This is especially useful for determining the cause of SMTP email issues as it shows all activity happening ‘behind the scenes’, including communication with the email server.
• Added the ‘AM/PM’ time formatting to email alerts if this time format is configured in the settings.
• Added an option to disable the web interface for use in highly secure environments.
• Added an option to disable TFTP firmware updates for use in highly secure environments.
• Added an option to disable SNMP for use in highly secure environments.
• Added additional entry validation checks to the settings pages to prevent against invalid settings entry.
• Modified the ‘getData.htm’ output to be fully compatible with our new Device ManageR application.
• Modified the ‘Monitor Heat Index’ label for Temp/Humidity Sensors on the Sensor Settings screen to open a popup linking to the explanation of what Heat Index is from the AVTECH.com Knowledge Base when clicked.
• Modified the Security Settings screen to require the current password when changing to a new password.

v3.0.0

April 9, 2008

• Completely redesigned the Settings screen to use HTML forms instead of the Java Applet previously used.
  • This provides a much more user friendly configuration interface that does not require any additional browser plugins to operate properly.
• Modified the way sensor thresholds are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, thresholds could only be configured in Fahrenheit.
  • If thresholds were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor thresholds are configured correctly.
• Modified the way sensor calibration values entered in the ‘Adjust’ field are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, the ‘Adjust’ value could only be entered in Celsius.
  • If ‘Adjust’ values were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor calibrations are configured correctly.
• Modified the Settings authentication to prompt for a password using the standard browser authentication entry display. The username field will *always* be left blank and the password (if configured) should be entered in the password field.
• Added SMTP Authentication capabilities to the email configuration and sending modules. A username and password can now optionally be provided for SMTP Authentication for use on servers that do not allow anonymous SMTP email messages.
• Added the ability to modify the SMTP port used for sending email. This will also benefit users who have mail servers that use alternate ports or do not allow mail submission on port 25.
• Modified the trace output feature to allow the port number to be modified. By default, a port of 143 is used if tracing output is enabled.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages and logging data.
• Added the ability to configure the DNS Server IP address via the telnet configuration menu.
• Added the MAC Address to the Status screen display to make it easier to identify multiple devices on the network.
• Added a new feature that allows users to send a test email by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=SendTestEmail’.
  • A button is also provided on the SMTP Email section of the Settings screen that will trigger a test email to be sent.
  • Both of these new functions will only work if valid email settings are configured on the SMTP Email section of the Settings screen.
• Added a function to check the return code from a SMTP server on the initial connection instead of after each command.
  • This resolves an issue that could occur if a SMTP server responds with an error code on the initial connection.
• Added a URL alias so sensor data can be accessed in JSON format at both ‘/getData.htm’ and ‘/getdata.htm’.
• Resolved an issue that could cause DHCP Names less than 8 characters long to save incorrectly.
• Resolved an issue that could cause the SNMP ‘SysObjectID’ variable to return an incorrect value.

v1.6.2

October 26, 2007

• Resolved an issue that could cause some temperature sensors not to display properly on the Status screen.
• Added additional tracing output to help diagnose temperature sensor issues.

v1.6.1

October 24, 2007

• Improved support for AVTECH’s Digital Power Sensor. This firmware version adds support for Digital Power Sensor v1.2 and above.
• Added additional tracing output for the Digital Power Sensor.
• Modified the MTU setting in the telnet configuration menu to be consistent with other Room Alert models.
• Resolved an issue that caused the last eight (8) characters in the DHCP Name not to be cleared when modified to a label that is shorter than eight (8) characters.
• Resolved an issue that caused the Temperature Sensor to stop updating if the temperature dropped below zero degrees Celsius.

v1.6.0

August 22, 2007

• Added a new webpage display option designed specifically for mobile devices such as mobile phones and PDAs. The new URL ‘http://(IP of Device)/mobile’ will display a text only output of all current sensor data.
• Added a new feature that allows users to reset the high and low values for sensors by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=ResetHighLow’.
• Added the ability to modify the SMTP port used for email via the Telnet configuration menu.
• Added an option to return sensor values in a two digit format instead of the default four digit format when queried via SNMP. This option can be configured through the Telnet configuration menu.
• Resolved an issue that could prevent alarm notifications from being sent for switch sensors set to alarm on an ‘Open’ condition.
• Increased the timeout used when saving settings via the Settings applet to resolve an issue that occurred on Mac OS X and Windows Vista.
• Resolved an issue with the Email tab of the Settings applet that could prevent email settings from saving if the ‘Email Enabled’ checkbox was not selected.

v1.5.2

August 16, 2007

• A network driver provided by the chip manufacturer was found to cause a reboot loop condition under certain circumstances when settings were saved from the Settings applet. We worked with the manufacturer to resolve this issue and have included the updated network driver in this version.
• Added additional verification code to be sure the timezone offset is within an acceptable range. Users who previously had a timezone selected on the
• Advanced tab of the Settings applet should verify that the correct timezone is selected after installing this update.
• Added additional verification code to be sure valid IP addresses are entered on the Network tab of the Settings applet.
• Added additional verification code to be sure a valid DHCP Name is entered on the Network tab of the Settings applet.

v1.5.1

August 9, 2007

• Resolved an issue with the Status screen display introduced by the latest update to Microsoft Internet Explorer. Other browsers such as Mozilla Firefox and Safari were unaffected.

v1.5.0

August 8, 2007

• Added Heat Index monitoring.
• Added Digital Power Sensor monitoring. Room Alert 24E can now generate alarms for Voltage (V), Current (A), Power (W) and Apparent Power (VA) detected by AVTECH’s Digital Power Sensor.
• Added a ‘tracing’ function to help diagnose issues such as email alerts not being sent.
  • When enabled through the telnet menu, tracing information will now be output to port 87223. This tracing information can be saved to a file that can be sent to AVTECH Support by executing the command ‘telnet *IP* 87223 -f C:\RA24E.tra’, replacing *IP* with the IP address of the Room Alert 24E and modifying the file path if desired.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Improved the error checking code so incorrect readings from sensors caused by EMI or other interference will be filtered and ignored.
• Updated the timezones so now intermediate timezones such as Newfoundland (GMT-3:30) and India (GMT+5:30) are supported.
  • As a result of this change, some users might have to update their timezone setting on the ‘Advanced’ tab after the firmware upgrade. Most should be updated automatically.
• Added a link to our ‘Live Sales Support’ on the About screen.
  • This makes it easy to speak with one of our Product Specialists regarding purchasing additional sensors or devices.
• Resolved an issue that could cause Switch Sensor false alarms to be sent if a normally closed sensor such as a Power Sensor was connected and the unit rebooted.

v1.0.1

May 21, 2007

• Resolved an issue that could cause sensors to stop updating if the temperature is below zero degrees.
• Resolved an issue that could cause alarms not to clear on external Temp/Humidity Sensors.

v1.0.0

March 15, 2007

• First official release of the Room Alert 24E firmware.

The post Room Alert 24E Firmware Release Notes appeared first on AVTECH.

v3.0.1

April 10, 2013

• Resolved an issue that could cause the readings on the Status page to display inconsistently when temperatures were below 0C.

v3.0.0

March 14, 2012

• Added support for all modern web browsers. The TemPageR web interface should now be fully functional in all web browsers, including IE8/9, Firefox, Chrome, Safari, Opera and others that conform to modern web standards. With full support for Chrome and Safari, the web interface can now also be viewed in mobile devices running Android and iOS.
• Added support for the new ‘Push’ technology for use with Device ManageR.
  • Previously, Device ManageR would query the device for sensor values at defined intervals. If the device was installed at a remote location, this could cause additional configuration steps because of firewalls that might be in place between locations.
  • The new ‘Push’ technology allows users to configure TemPageR to proactively send sensor updates to Device ManageR at regular intervals. Since TemPageR will be sending data out to Device ManageR, firewall configurations can typically be simpler since outgoing connections are usually allowed.
  • In addition, if TemPageR detects an alarm condition, it will immediately send an update to Device ManageR, regardless of the interval setting. This allows for more immediate notification of alarm conditions that is no longer tied to the Discovery Interval configured in Device ManageR. Please contact AVTECH for additional details about this exciting new feature.
• Updated the core embedded operating system and network drivers. This should improve the communication between our TemPageR devices and high end network switches to improve interoperability.
• Added support for the JSONP protocol. This makes it much easier for users to incorporate sensor data from TemPageR devices into their own web pages without the challenges previously posed by cross-domain scripting restrictions.
• Updated the sensor output to conform to valid JSON formats.
• Added the ability to configure the date format displayed on the web interface and in email notifications to allow for customization in different international locales.
• Improved the way time is displayed in email notifications to more fully conform to the RFC standard.
• Added timestamps to the trace output to make it easier for our Technical Support team to identify the timing of certain background activities to facilitate quicker resolutions.
• Modified the way the Device Name is handled so the Serial Number is used as the default Device Name when factory default settings are reset.
• Resolved an issue that could allow a Device Name to be configured that was one character longer than supported.
• Improved the verification performed before saving sensor labels to be sure invalid characters cannot be used for sensor labels.

v2.5.0

December 23, 2011

• Improved support for all major web browsers. Each page of the web interface has now been tested and updated to work in Chrome, Firefox, Safari, Opera and IE8/9.
• Improved the formatting of the ‘getdata’ output to be fully validated JSON. This resolves an issue caused in some browsers that could cause sensor data to fail to load.
• Added support for permanently storing the Serial Number in flash memory. This Serial Number will not be modifyable and will be restored when factory default settings are restored.
• Improved the alert checking process so multiple alerts can be triggered on the same sensor simultaneously. This allows alerts for Temperature and Humidity at the same time on a Temp/Humidity Sensor.
• Added support for sending the current sensor value for the sensor that triggered an alert with SNMP Traps. Please update the MIB file used in your SNMP software to benefit from this new feature.
• Added an intermediate Settings page to help explain the default username and password for initial access to the Settings configuration pages.
• Added timestamps to the tracing output to help our Technical Support team better diagnose any issues.
• Updated the SNMP MIB files to support the new features. Please be sure to download the latest version of the TemPageR 3E MIB files.
• Added the ability to configure the date format displayed on screens and in email alerts to better support international variations.

v2.0.0

December 8, 2010

• Added a new feature that allows the TemPageR 3E to optionally automatically synchronize the date and time with the configured NTP server at regular intervals. Available intervals include 10 minutes, 60 minutes and 6, 12 and 24 hours.
• Added a new feature to optionally disable periodic Gratuitous ARP broadcasts from being sent.
• Improved how sensor packets are handled to better prevent against periodic sensor disconnect false alarms.

v1.6.1

November 12, 2009

• Added the ability to configure the SMTP Timeout on the SMTP Email page of the Settings. This was previously hard coded to 5 seconds and can now be set to any value between 1-99 seconds.
• Resolved an issue that could cause the web interface to stop responding and require a reboot if repeated authentication attempts failed when accessing the Settings screen.

v1.6.0

July 22, 2009

• Modified the way the ‘EHLO’ command is sent to mail servers so it uses the local IP address instead of the ‘From’ address. This is more consistent with what most email servers expect and should prevent periodic SMTP timeouts.
• Added the Device Name to the subject of email alerts that are sent, making it easier to identify which device the alert was sent from for customers with multiple devices.
• Added the ability to configure the ‘sysContact’ SNMP value via the SNMP Settings screen.
• Added the ability to configure the ‘sysLocation’ SNMP value via the SNMP Settings screen.
• Configured the ‘sysName’ SNMP value to report the Device Name. This was previously blank.
• Modified the ‘sysDescr’ SNMP value to report the device type and version. This previously reported the Device Name.
• Adjusted the Sensor Disconnected SMS text to report the timestamp on its own line so it is consistent with the other SMS alerts.
• Resolved an issue that could cause false alarms when SNMP Traps were broadcast on the network.

v1.5.1

June 1, 2009

• Resolved an issue that could cause sensor values to stop updating for periods of time due to false alarm checking that was too sensitive for some environments.

v1.5.0

April 23, 2009

• Added the ability to modify the port used for HTTP requests. This was previously hard-coded to use port 80.
• Added the ability to modify the URL that is displayed at the bottom of email alert notifications. This allows users to define a WAN IP or DNS name so the link can be clicked and viewed from outside the local network if external access is configured.
• Resolved an issue that could cause the Status page to not load properly if values of -6C or lower were displayed.

v1.1.0

December 29, 2008

• Changed the default MTU to 1024 instead of 1400. This should reduce the occurrence of network connectivity issues with some managed switches and VPN connections.
• Added a MTU option to the Network settings so the MTU can be set to whatever is appropriate for the network it is connected to.
• Added additional error checking to SMTP requests to better diagnose email sending issues.
• Added the ability to define and save the default refresh interval of the Status page via the Advanced section of the Settings.
• Added the Device Name to email messages to make it easier to identify which unit the alert message was sent from when multiple units are installed.
• Modified how low thresholds are checked to be sure the current value rises one degree above the threshold before clearing to avoid repetitive alarms. This was previously only being applied to high thresholds.
• Resolved an issue that could cause the dates of December 29, 30 and 31 to be calculated incorrectly. These dates should all display properly with this version.
• Resolved an issue with the header response of the /mobile.txt page that could prevent it displaying in the BlackBerry browser.
• Corrected an issue with the trace output that could erroneously report an invalid humidity spike on the internal sensor.

v1.0.1

September 25, 2008

• Updated fields and labels on the Settings screens to be consistent across all screens and options.
• Added a timeout check to the SMTP sending function so a communication loss with the mail server does not cause the unit to stall while waiting for a response.
• Modified the SMTP sending function so it quits if authentication fails instead of continuing with an attempt to send an unauthenticated email if email authentication is enabled.
• Resolved an issue that could cause SNMP and TFTP functions to still respond even when configured as ‘Disabled’.
• Added a new webpage display option designed specifically for mobile devices such as phones and PDAs that required a ‘Content Type’ to be passed with the page data. The new URL ‘http://(IP of Device)/mobile.txt’ will display a text only output of all current sensor data with a Content Type of ‘text/plain’. The URL ‘http://(IP of Device)/mobile’ will still display a text only output of all sensor data without the Content Type header.

v1.0.0

July 30, 2008

• First official release of TemPageR v1.0.0 Firmware.

The post TemPageR 3E Firmware Release Notes appeared first on AVTECH.

v4.0.0

April 27, 2012

• Added support for all modern web browsers. The Room Alert web interface should now be fully functional in all web browsers, including IE8/9, Firefox, Chrome, Safari, Opera and others that conform to modern web standards. With full support for Chrome and Safari, the web interface can now also be viewed in mobile devices running Android and iOS.
• Added support for the new ‘Push’ technology for use with Device ManageR. Previously, Device ManageR would query the device for sensor values at defined intervals. If the device was installed at a remote location, this could cause additional configuration steps because of firewalls that might be in place between locations. The new ‘Push’ technology allows users to configure Room Alert to proactively send sensor updates to Device ManageR at regular intervals. Since Room Alert will be sending data out to Device ManageR, firewall configurations can typically be simpler since outgoing connections are usually allowed. In addition, if Room Alert detects an alarm condition, it will immediately send an update to Device ManageR, regardless of the interval setting. This allows for more immediate notification of alarm conditions that is no longer tied to the Discovery Interval configured in Device ManageR. Please contact AVTECH for additional details about this exciting new feature.
• Updated the core embedded operating system and network drivers. This should improve the communication between our Room Alert devices and high end network switches to improve interoperability.
• Added support for the JSONP protocol. This makes it much easier for users to incorporate sensor data from Room Alert devices into their own web pages without the challenges previously posed by cross-domain scripting restrictions.
• Updated the sensor output to conform to valid JSON formats.
• Added the ability to configure the date format displayed on the web interface and in email notifications to allow for customization in different international locales.
• Improved the way time is displayed in email notifications to more fully conform to the RFC standard.
• Added timestamps to the trace output to make it easier for our Technical Support team to identify the timing of certain background activities to facilitate quicker resolutions.
• Modified the way the Device Name is handled so the Serial Number is used as the default Device Name when factory default settings are reset.
• Resolved an issue that could allow a Device Name to be configured that was one character longer than supported.
• Improved the verification performed before saving sensor labels to be sure invalid characters cannot be used for sensor labels.

v3.4.1

October 3, 2011

• Added a page that displays when a user clicks the ‘Settings’ link that explains the default password and how to enter the username and password into the web browser prompt.
• Resolved an issue that could cause the time displayed in email alert notifications to be off by one hour depending on Daylight Savings Time settings.
• Improved the formatting of the ‘getdata.htm’ file so that it now passed full JSON validation.

v3.4.0

February 8, 2011

• Added the ability to query the currently configured sensor labels via SNMP.
• Resolved an issue that could prevent TFTP from being disabled when selected from the telnet menu.
• Resolved an issue that could cause inconsistent temperature readings to display when the current temperature was between -1.0C and 0.0C.

v3.3.0

December 28, 2010

• Added a new feature that allows the Room Alert 11E to optionally automatically synchronize the date and time with the configured NTP server at regular intervals. Available intervals include 10 minutes, 60 minutes and 6, 12 and 24 hours.
• Added the ability to disable periodic Gratuitous ARP packets from being sent.
• Resolved an issue that caused some MODBUS registers to return invalid values.
• Updated the MODBUS documentation to match the register values reported by Room Alert 11E.
• Resolved an issue that could cause email timestamps to display incorrectly with Daylight Savings Time enabled.

v3.2.3

May 4, 2010

• Added switch sensor initialization checks to prevent false alarms from being sent when the unit first boots.
• Added the ability to configure the number of scans that should elapse before a switch sensor state triggers an alert. This helps prevent false alerts caused by rapidly changing switch sensor inputs.

v3.2.2

November 23, 2009

• Resolved an issue that caused the device type and version number to be displayed on the Status screen instead of the Device Name as in previous versions.

v3.2.1

November 12, 2009

• Added the ability to configure the timeout value used for email communication on the ‘SMTP Email’ screen in Settings. The default value is 5 seconds and the setting supports values from 1-99 seconds.
• Resolved an issue that could cause the web interface to stop responding and require a reboot if repeated authentication attempts failed when accessing the Settings screen.

v3.2.0

August 10, 2009

• Modified the way the ‘EHLO’ command is sent to mail servers so it uses the local IP address instead of the ‘From’ address. This is more consistent with what most email servers expect and should prevent periodic SMTP timeouts.
• Added the Device Name to the subject of email alerts that are sent, making it easier to identify which device the alert was sent from for customers with multiple devices.
• Added the ability to configure the ‘sysContact’ SNMP value via the SNMP Settings screen.
• Added the ability to configure the ‘sysLocation’ SNMP value via the SNMP Settings screen.
• Added support for Modbus. Users can now query the Room Alert 11E for sensor information via Modbus, allowing easy integration with SCADA applications.
• Configured the ‘sysName’ SNMP value to report the Device Name. This was previously blank.
• Modified the ‘sysDescr’ SNMP value to report the device type and version. This previously reported the Device Name.
• Improved the progress bar used on the web interface when settings are saved.
• Resolved an issue that prevented the device password and sensor labels from being reset with factory default settings.

v3.1.2

April 8, 2009

• Added the ability to modify the port used for HTTP requests. This was previously hard-coded to use port 80.
• Added support for the ‘/mobile.txt’ URL which will return a properly formatted text-only sensor status return that is easily viewable from devices with smaller screens.
• Added the ability to modify the URL that is displayed at the bottom of email alert notifications. This allows users to define a WAN IP or DNS name so the link can be clicked and viewed from outside the local network if external access is configured.
• Resolved an issue that could cause the Status page to not load properly if values of -6C or lower were displayed.
• Resolved an issue that could cause SNMP Traps to be interpreted incorrectly by some SNMP managers.

v3.1.1

January 12, 2009

• Resolved an issue that could cause a periodic reboot to occur on devices with a large number of consecutive web interface requests.
• Resolved an issue that could cause the time displayed in email messages to be off by one hour depending on the daylight saving time setting.

v3.1.0

December 23, 2008

• Changed the default MTU to 1024 instead of 1400. This should reduce the occurrence of network connectivity issues with some managed switches and VPN connections.
• Added a MTU option to the Network settings so the MTU can be set to whatever is appropriate for the network it is connected to.
• Resolved an issue that could cause the dates of December 29, 30 and 31 to be calculated incorrectly. These dates should all display properly with this version.
• Added the ability to use the SNMP Community that is defined in the SNMP section of the Settings with SNMP Traps that are sent.
• Added the ability to define and save the default refresh interval of the Status page via the Advanced section of the Settings.
• Added additional error checking to SMTP requests to better diagnose email sending issues.
• Resolved a display issue with the Sensors section of the Settings screen.

v3.0.3

September 23, 2008

• Added support for displaying the ‘Heat Index’ value in Celsius in addition to the default of Fahrenheit.
• Added a timeout check to the SMTP sending function so a communication loss with the mail server does not cause the unit to stall while waiting for a response.
• Modified the SMTP sending function so it quits if authentication fails instead of continuing with an attempt to send an unauthenticated email if email authentication is enabled.
• Added support for AM/PM time display in email alerts.
• Added an ‘Uptime’ value to the trace output as a way to determine how long the device has been powered on.
• Resolved an issue that prevented ‘512’ and ‘1024’ from being entered as valid MTU settings.
• Resolved an issue that could cause SNMP and TFTP functions to still respond even when configured as ‘Disabled’.

v3.0.2

June 19, 2008

• Resolved an issue that could cause the value entered in the ‘Adjust’ field to change values due to incorrect rounding on sequential Sensor Settings saves.
• Resolved an issue that could cause email messages to fail to send if the mail server replies with a long response to the EHLO command. We now check for a 250 response indicating it is ‘OK’ to send and discard the remaining unused message.
• Resolved an issue that could cause email messages to fail to send if the mail server responded with an alternative error code to the EHLO command. We now correctly fall back to using HELO if the initial EHLO attempt fails and returns a code other than the 250 ‘OK’ message.
• Added a status message when sensor labels are saved so a blank web page does not display before the ‘Saving…’ progress bar.

v3.0.1

May 28, 2008

• Resolved an issue that could cause the Room Alert 11E to show up as an unknown device in Device ManageR.
• Combined the Email Server IP and Domain Name fields into a single field in the SMTP Email Settings Screen. It will now automatically determine whether an IP address or a domain name was entered and use the appropriate method to send the email.
  • This previously caused an issue if a user entered a local IP address for their mail server and also added a domain name. In this situation, Room Alert 11E would attempt to resolve the IP address from the domain name instead of using the configured local IP address.
• Improved the validation of IP address fields in the Settings screens to prevent invalid IP address entry.
• Resolved an issue with values entered in the ‘Adjust’ field in the Sensor Settings being rounded too low on each save.

v3.0.0

March 20, 2008

• Completely redesigned the Settings screen to use HTML forms instead of the Java Applet previously used. This provides a much more user friendly configuration interface that does not require any additional browser plugins to operate properly.
• Modified the way sensor thresholds are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, thresholds could only be configured in Fahrenheit.
  • If thresholds were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor thresholds are configured correctly.
• Modified the way sensor calibration values entered in the ‘Adjust’ field are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, the ‘Adjust’ value could only be entered in Celsius.
  • If ‘Adjust’ values were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor calibrations are configured correctly.
• Modified the Settings authentication to prompt for a password using the standard browser authentication entry display. The username field will *always* be left blank and the password (if configured) should be entered in the password field.
• Added SMTP Authentication capabilities to the email configuration and sending modules. A username and password can now optionally be provided for SMTP Authentication for use on servers that do not allow anonymous SMTP email messages.
• Added the ability to modify the SMTP port used for sending email. This will also benefit users who have mail servers that use alternate ports or do not allow mail submission on port 25.
• Modified the trace output feature to allow the port number to be modified. By default, a port of 143 is used if tracing output is enabled.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages and logging data.
• Added the ability to configure the DNS Server IP address via the telnet configuration menu.
• Added the MAC Address to the Status screen display to make it easier to identify multiple devices on the network.
• Added a new feature that allows users to send a test email by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=SendTestEmail’. A button is also provided on the SMTP Email section of the Settings screen that will trigger a test email to be sent. Both of these new functions will only work if valid email settings are configured on the SMTP Email section of the Settings screen.
• Added a function to check the return code from a SMTP server on the initial connection instead of after each command. This resolves an issue that could occur if a SMTP server responds with an error code on the initial connection.
• Added a URL alias so sensor data can be accessed in JSON format at both ‘/getData.htm’ and ‘/getdata.htm’.
• Resolved an issue that could cause DHCP Names less than 8 characters long to save incorrectly.
• Resolved an issue that could cause the SNMP ‘SysObjectID’ variable to return an incorrect value.
• Resolved an issue that caused sensor values and thresholds returned via SNMP to be in a non-standard table format with an OID that did not end in ‘.0’. This has been corrected so all OID SNMP values now end in ‘.0’. Be sure to update any MIBs used for SNMP monitoring after applying this firmware update.

v2.8.2

December 21, 2007

• Resolved an issue that caused the SNMP ‘sysObjectID’ variable to report the incorrect value. This now correctly reports ‘1.3.6.1.4.1.20916.1.3’.
• Added the MAC address and device type to the ‘/getData.htm’ output page.
• Added an alias so ‘/getdata.htm’ returns the same page as ‘/getData.htm’.

v2.8.1

November 5, 2007

• Resolved an issue that could cause Digital Temperature Sensors to stop updating if the temperature dropped below 32 degrees Fahrenheit. Digital Temp/Humidity Sensors were not affected.
• Improved support for modifying the MTU network setting.
• Added the ability to modify the TCP port used for trace output.
• Changed the default tracing port to ‘911’ instead of ‘87223’ so it is within the valid TCP port range.

v2.8.0

August 23, 2007

• Added a new webpage display option designed specifically for mobile devices such as mobile phones and PDAs. The new URL ‘http://(IP of Device)/mobile’ will display a text only output of all current sensor data.
• Added a new feature that allows users to reset the high and low values for sensors by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=ResetHighLow’.
• Added the ability to modify the SMTP port used for email via the Telnet configuration menu.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Added an option to return sensor values in a two digit format instead of the default four digit format when queried via SNMP. This option can be configured through the Telnet configuration menu.
• Reduced the time required to generate an alarm for switch sensors.
• Resolved an issue that could cause Sensor2-1 to not appear when the sensors were queried via SNMP.

v2.7.7

August 17, 2007

• A network driver provided by the chip manufacturer was found to cause a reboot loop condition under certain circumstances when settings were saved from the Settings applet. We worked with the manufacturer to resolve this issue and have included the updated network driver in this version.
• Added additional verification code to be sure the timezone offset is within an acceptable range. Users who previously had a timezone selected on the Advanced tab of the Settings applet should verify that the correct timezone is selected after installing this update.
• Added additional verification code to be sure valid IP addresses are entered on the Network tab of the Settings applet.
• Added additional verification code to be sure a valid DHCP Name is entered on the Network tab of the Settings applet.
• Improved SNMP performance through memory and code optimizations.

v2.7.5

August 2, 2007

• Added a ‘tracing’ function to help diagnose issues such as email alerts not being sent. When enabled through the telnet menu, tracing information will now be output to port 87223. This tracing information can be saved to a file that can be sent to AVTECH Support by executing the command ‘telnet 87223 -f C:\RA11E.tra’, replacing with the IP address of the Room Alert 11E and modifying the file path if desired.
• Resolved an issue that could cause humidity values to be calculated incorrectly. This could cause the reported humidity readings to appear to ‘spike’ periodically resulting in false alarms.
• Improved the error checking code so incorrect readings from sensors caused by EMI or other interference will be filtered and ignored.
• Updated the timezones so now intermediate timezones such as Newfoundland (GMT-3:30) and India (GMT+5:30) are supported.
  • As a result of this change, some users might have to update their timezone setting on the ‘Advanced’ tab after the firmware upgrade. Most should be updated automatically.
• Added a link to our ‘Live Sales Support’ on the About screen. This makes it easy to speak with one of our Product Specialists regarding purchasing additional sensors or devices.
• Improved the performance of the web interface by modifying the way dynamic pages are generated.

v2.7.0

June 15, 2007

• Added Heat Index monitoring.

v2.6.0

May 3, 2007

• Improved the accuracy of the humidity sensor calculation.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Resolved an issue that could cause the humidity reading to stop updating for higher humidity readings.
• Resolved an issue with email notifications that caused email not to be sent if the mail server sent telnet control characters to Room Alert 11E.

v2.5.4

January 22, 2007

• Added a ‘SMS Format’ option to the Email tab in Settings. This will send shorter email messages formatted specifically for mobile devices such as phones and pagers.
• Resolved an issue with email messages that could cause an email error to occur after multiple email messages were sent.
• Added a feature that disables the web interface while firmware updates are in progress to help prevent incomplete firmware updates.

v2.5.3

December 22, 2006

• Improved email alert messages so they include additional information regarding what caused the alert to be triggered.
• Resolved an issue with Internet Explorer 6 and 7 that caused the settings password to not be accepted. Other browsers were unaffected.
• Added a progress bar to the settings applet to indicate when the device is saving settings or rebooting.
• Modified the field validation for the email tab to allow email addresses with extra periods (.).

v2.5.2

November 1, 2006

• Resolved web interface issues introduced with the release of Internet Explorer 7.
• Added a ‘Help’ screen to the web interface that provides quick access to various support resources.
• Improved the Sensor Loading function on the Status screen to retry if the initial connection fails.
• Removed the ‘X-Priority’ header from email messages and added an extra line break before the body text to resolve an issue with certain mail servers.
• Resolved an issue with the Telnet interface that caused both input and output to be echoed twice.
• Resolved an issue with the field verification on the Email tab that prevented the contents of the field from being deleted.

v2.5.1

October 6, 2006

• AVTECH Device Discovery Utility v2.5.2 or higher *MUST* be used to install this update.
• Modified the Time Server IP field to load the default NTP Server IP address if an invalid address is saved.
• Increased the size of the ‘Return Address’ field and modified the field filter on the Email tab so email addresses up to 42 characters may be entered.
• Improved the email validation function to allow email addresses with uncommon domain names.
• Resolved an issue that caused email alerts to only be sent to the first recipient if multiple sensors were in an alarm state.
• Modified the Network tab on the Settings screen to notify the user if the network settings have changed and prompt them to reload the page at the correct IP address.
• Added a ‘Reboot Unit’ option to the telnet interface to allow users to remotely reboot the unit through a telnet session.

v2.5.0

October 2, 2006

• This is a major update of the Room Alert 11E operating system. AVTECH Device Discovery Utility v2.5.2 or higher *MUST* be used to install this update.
• As a result of this update, any custom sensor labels will have to be reconfigured. All other settings will remain intact.
• Increased the memory available for the web interface which will result in increased responsiveness.
• Increased the size of the ‘Return Address’ field on the Email tab so email addresses up to 42 characters may be entered.
• Modified the ‘Recipients’ field on the Email tab. Multiple email addresses can now be entered in a single field and separated by a semi-colon. If an email address had previously been entered in the ‘Email Recipient 2’ field, it should be re-entered in the new field.
• Added support for Dynamic DNS. The name of the device should now be registered as the hostname on the DHCP and DNS servers if the network is configured to allow this.
• Improved the Alarm engine to reduce repetitive alarms. The temperature or humidity will have to return one (1) degree below the defined threshold before the alarm will be cleared. This prevents alarms from being set and cleared repetitively if the current temperature or humidity is very close to the threshold defined.
• Resolved an issue that caused the Settings page not to display after entering a valid password.
• Added a ‘Help’ menu option that provides links to support resources on AVTECH.com and lists the available Technical Support contact methods.
• Added the data and time the alert was generated to the body of email alerts.

v2.0.1

March 9, 2006

• Resolved an issue that caused the humidity sensor high and low readings to be reversed on some sensors.
• Improved the response of the Status page to make initial page loads more reliable.
• Added a version number display to the Status page. Clicking the version number will check to see if an update is available from AVTECH.com.
• Resolved an issue with humidity sensor thresholds.
• Added support for floating point alert thresholds.

v2.0.0

February 7, 2006

• Added the ability to syncronize the time via URL (http://IP of device/cmd.cgi?a=SyncTime). When the URL is called, Room Alert 11E will use current NTP settings to update the current date and time.
• Major updates were made to the ‘Status’ page.
  • Only the sensor data is updated on refresh to greatly increase refresh speed.
  • Custom refresh rates can be specified to update the sensor data.
  • Users can choose to display all sensors or only connected sensors.
  • Users can choose to display Fahrenheit or Celsius temperature values.
  • The thermometer graphic was enhanced for realism and now displays a different scale for Fahrenheit and Celsius values.
• Improved the alert cleared functionality to only clear an alert after the temperature is at least one degree above or below the defined threshold. This greatly reduces multiple alerts caused when the current temperature hovers close to a defined threshold.
• Added a link to the ‘About’ page to connect to AVTECH.com and check for firmware updates.
• Improved the NTP feature to try to obtain the network time before logging sensor data if the time has not been set yet. It will attempt to obtain the network time up to 5 times. This is in addition to obtaining the network time when TemPageR boots and should eliminate an issue where the time is not obtained if TemPageR boots before the NTP server in the event of a power loss.
• Improved the Alarm engine to reduce repetitive alarms. The temperature will have to return one (1) degree below the defined threshold before the alarm will be cleared. This prevents alarms from being set and cleared repetitively if the current temperature is very close to the threshold defined.
• Modified the ‘Network’ tab to only save static IP settings if a valid Gateway and Subnet Mask has been specified.
• Resolved an issue that caused incorrect status icons to be displayed when certain alarm thresholds were defined.
• Edited some text and default field values in the Settings applet.

v1.1.0

November 4, 2005

• Added Date and Time support to display the current date and time on the Status screen. This includes support for Daylight Saving Time (DST).
• Added the ability for users to specify their own Network Time (NTP) server to obtain the current time and date.
• Improved the Settings Applet layout to display consistently and prompt the user on invalid entries.
• Resolved an issue with humidity thresholds that caused some thresholds to be evaluated incorrectly.
• Resolved an issue with the Settings password that caused pages not to display in some cases.

v1.0.3

September 26, 2005

• Modified the ‘ROOMALERT11E.MIB’ file to support HP Systems Manager (HPSIM).
• Resolved an issue that caused SNMP traps to be sent at rapid intervals for humidity alarms.

v1.0.0

• First official release of Room Alert 11E firmware.

The post Room Alert 11E Firmware Release Notes appeared first on AVTECH.

v4.5.0

April 3, 2012

• Added support for all modern web browsers. The TemPageR web interface should now be fully functional in all web browsers, including IE8/9, Firefox, Chrome, Safari, Opera and others that conform to modern web standards. With full support for Chrome and Safari, the web interface can now also be viewed in mobile devices running Android and iOS.
• Added support for the JSONP protocol. This makes it much easier for users to incorporate sensor data from TemPageR devices into their own web pages without the challenges previously posed by cross-domain scripting restrictions.
• Updated the sensor output to conform to valid JSON formats.
• Added the ability to configure the date format displayed on the web interface and in email notifications to allow for customization in different international locales.
• Improved the way time is displayed in email notifications to more fully conform to the RFC standard.
• Added timestamps to the trace output to make it easier for our Technical Support team to identify the timing of certain background activities to facilitate quicker resolutions.
• Added a webpage that displays prior to accessing the Settings page that explains the default passwords used with AVTECH devices.

v3.0.4

August 21, 2008

• Resolved an issue that caused some mail servers to prevent proper email authentication if the username or password contained a null character at the end.
• Resolved an issue that could cause email messages to fail to send if the mail server replies with a long response to the EHLO command. We now check for a 250 response indicating it is ‘OK’ to send and discard the remaining unused message.
• Resolved an issue that could cause email messages to fail to send if the mail server responded with an alternative error code to the EHLO command.
• We now correctly fall back to using HELO if the initial EHLO attempt fails and returns a code other than the 250 ‘OK’ message.
• Added an ‘Uptime’ value to the ‘/getdata.htm’ output for future use as a way to determine how long the device has been powered on.
• Added an ‘Uptime’ value to the trace output for future use as a way to determine how long the device has been powered on.

v3.0.3

May 30, 2008

• Combined the Email Server IP and Domain Name fields into a single field in the SMTP Email Settings Screen. It will now automatically determine whether an IP address or a domain name was entered and use the appropriate method to send the email.
  • This previously caused an issue if a user entered a local IP address for their mail server and also added a domain name. In this situation, TemPageR would attempt to resolve the IP address from the domain name instead of using the configured local IP address.
• Improved the validation of IP address fields in the Settings screens to prevent invalid IP address entry.
• Modified the prompts that appear during password modification on the Security Settings screen.
• Resolved an issue that could cause trace output to stop responding if email messages were too long.

v3.0.2

May 7, 2008

• Resolved an issue that could cause the MTU setting to not be applied correctly, preventing web access over VPN and other secure protocols. MTU settings from 512 to 1400 can now be configured for users experiencing an issue viewing the web interface over a VPN connection.
• Resolved an issue that caused SNMP Trap messages to always be sent with a ‘public’ community string instead of the configured SNMP Community Name.
• Added a ‘View Tracing Output’ option to the Advanced Settings screen. This is especially useful for determining the cause of SMTP email issues as it shows all activity happening ‘behind the scenes’, including communicating with the email server.
• Added an option to disable the web interface for use in highly secure environments.
• Added an option to disable TFTP firmware updates for use in highly secure environments.
• Added an option to disable SNMP for use in highly secure environments.
• Added additional entry validation checks to the settings pages to prevent against invalid settings entry.
• Resolved an issue that could cause some TemPageR units to appear as an unknown device with our new Device ManageR application.
• Modified the Security Settings screen to require the current password when changing to a new password.

v3.0.1

April 10, 2008

• Added additional validation checks to the Settings pages to be sure invalid settings cannot be saved.
• Resolved an issue that could cause the unit to stop responding after a period of time until the power was cycled.

v3.0.0

March 6, 2008

• Completely redesigned the Settings screen to use HTML forms instead of the Java Applet previously used. This provides a much more user friendly configuration interface that does not require any additional browser plugins to operate properly.
• Due to the additional space required for the updated Settings interface, the files used are now stored in a section of flash that was previously used by the TemPageR logging function.
  • With this update, one of the archived logging sections is removed meaning that TemPageR will actively log to one file and keep one (1) archived log file. For long term logging of sensor data, we highly recommend using AVTECH Device Manager.
  • If logging is currently enabled on your TemPageR unit, please DISABLE logging before applying this firmware update to avoid any potential conflicts.
• Modified the way sensor thresholds are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, thresholds could only be configured in Fahrenheit.
  • If thresholds were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor thresholds are configured correctly.
• Modified the way sensor calibration values entered in the ‘Adjust’ field are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, the ‘Adjust’ value could only be entered in Celsius.
  • If ‘Adjust’ values were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor calibrations are configured correctly.
• Modified the Settings authentication to prompt for a password using the standard browser authentication entry display. The username field will *always* be left blank and the password (if configured) should be entered in the password field.
• Added SMTP Authentication capabilities to the email configuration and sending modules. A username and password can now optionally be provided for SMTP Authentication for use on servers that do not allow anonymous SMTP email messages.
• Added the ability to modify the SMTP port used for sending email. This will also benefit users who have mail servers that use alternate ports or do not allow mail submission on port 25.
• Modified the trace output feature to allow the port number to be modified. By default, a port of 143 is used if tracing output is enabled.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages and logging data.
• Added the ability to configure the DNS Server IP address via the telnet configuration menu.
• Added the MAC Address to the Status screen display to make it easier to identify multiple devices on the network.
• Added a new feature that allows users to send a test email by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=SendTestEmail’.
  • A button is also provided on the SMTP Email section of the Settings screen that will trigger a test email to be sent.
  • Both of these new functions will only work if valid email settings are configured on the SMTP Email section of the Settings screen.
• Resolved an issue that could cause DHCP Names less than 8 characters long to save incorrectly.
• Resolved an issue that could cause the SNMP ‘SysObjectID’ variable to return an incorrect value.

v2.7.0

September 21, 2007

• Added a ‘tracing’ function to help diagnose issues such as email alerts not being sent. When enabled through the telnet menu, tracing information will now be output to port 87223. This tracing information can be saved to a file that can be sent to AVTECH Support by executing the command ‘telnet 87223 -f C:\TMPE.tra’, replacing with the IP address of TemPageR and modifying the file path if desired.
• Updated the timezones so now intermediate timezones such as Newfoundland (GMT-3:30) and India (GMT+5:30) are supported. As a result of this change, some users might have to update their timezone setting on the ‘Advanced’ tab after the firmware upgrade. Most should be updated automatically.
• Added a link to our ‘Live Sales Support’ on the About screen. This makes it easy to speak with one of our Product Specialists regarding purchasing additional sensors or devices.
• Added a new webpage display option designed specifically for mobile devices such as mobile phones and PDAs. The new URL ‘http://(IP of Device)/mobile’ will display a text only output of all current sensor data.
• Added a new feature that allows users to reset the high and low values for sensors by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=ResetHighLow’.
• Added the ability to modify the SMTP port used for email via the Telnet configuration menu.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Added an option to return sensor values in a two digit format instead of the default four digit format when queried via SNMP. This option can be configured through the Telnet configuration menu.

v2.6.0

March 5, 2007

• Added support for Email-To-SMS messages. When this option is selected, TemPageR will send email alerts with minimized text content for more efficient display on mobile devices.
• Resolved an issue that caused logging to stop functioning after writing the third logfile instead of overwriting the oldest file.
• Resolved an issue that caused web pages not to load after a firmware update if the web interface was open while a firmware update was in progress.
• Resolved an issue with email notifications that caused email not to be sent if the mail server sent telnet control characters to TemPageR.

v2.5.1

December 22, 2006

• Improved email alert messages so they include additional information regarding what caused the alert to be triggered.
• Resolved an issue with Internet Explorer 6 and 7 that caused the settings password to not be accepted. Other browsers were unaffected.
• Added a progress bar to the settings applet to indicate when the device is saving settings or rebooting.
• Modified the field validation for the email tab to allow email addresses with extra periods (.).

v2.5.0

November 22, 2006

• Major update of the TemPageR 4E operating system. AVTECH Device Discovery Utility v2.5.3 or higher *MUST* be used to install this update.
• Increased the memory available for the web interface which will result in increased responsiveness.
• Increased the size of the ‘Return Address’ field on the Email tab so email addresses up to 42 characters may be entered.
• Modified the ‘Recipients’ field on the Email tab. Multiple email addresses can now be entered in a single field and separated by a comma. If an email address had previously been entered in the ‘Email Recipient 2’ field, it should be re-entered in the new field.
• Added support for Dynamic DNS. The name of the device should now be registered as the hostname on the DHCP and DNS servers if the network is configured to allow this.
• Added a ‘Help’ menu option that provides links to support resources on AVTECH.com and lists the available Technical Support contact methods.
• Added the date and time the alert was generated to the body of email alerts.

v2.1.2

November 1, 2006

• Resolved web interface issues introduced with the release of Internet Explorer 7.
• Added a ‘Help’ screen to the web interface that provides quick access to various support resources.
• Improved the Sensor Loading function on the Status screen to retry if the initial connection fails.
• Removed the ‘X-Priority’ header from email messages and added an extra line break before the body text to resolve an issue with certain mail servers.

v2.1.1

March 2, 2006

• Resolved an issue that prevented negative temperatures from displaying correctly.
• Added negative threshold support. Negative temperature thresholds can now be specified on the ‘Alerts’ tab.
• Resolved an Internet Explorer specific issue that caused the Status screen to ‘flicker’ when the data refreshed.
• Adjusted the thermometer display to improve visual accuracy and match the current temperature more closely.
• Resolved an issue that caused periodic device reboots when accessing the Status screen.
• Updated the firmware update process so logfiles are no longer erased. A future version of the Device Discovery Utility will provide an option to erase the logfiles. Logfiles can also be cleared on the ‘Logging’ tab in Settings.
• Resolved a display issue that occurred when only two external sensors were connected.

v2.0.1

December 22, 2005

• Improved the NTP feature to try to obtain the network time before logging sensor data if the time has not been set yet. It will attempt to obtain the network time up to 5 times. This is in addition to obtaining the network time when TemPageR boots and should eliminate an issue where the time is not obtained if TemPageR boots before the NTP server in the event of a power loss.
• Improved the Alarm engine to reduce repetitive alarms. The temperature will have to return one (1) degree below the defined threshold before the alarm will be cleared. This prevents alarms from being set and cleared repetitively if the current temperature is very close to the threshold defined.
• Resolved some Internet Explorer specific issues that prevented the Status page from refreshing in some cases.
• Resolved a display issue caused by Internet Explorer’s incorrect caching of background images.
• Resolved an issue that caused the incorrect status icon to display for high temperatures (over 100C).
• Resolved an issue that caused the temperature to be calculated incorrectly for high temperatures (over 100C).
• Resolved an ‘Page Could Not Be Displayed’ issue that could occur if the ‘Enter’ key was pressed while modifying the refresh field.

v2.0.0

December 8, 2005

• Added floating point support. Temperatures are now recorded and logged with floating point precision up to one-hundredth of a degree.
  • NOTE: Users monitoring their TemPageR devices via SNMP will have to update the SNMP Queries to support the new floating point feature (i.e. 75 is now 7500).
• Added additional logging capability. Up to three logfiles are now stored. When the file size limit is reached, the current logfile is automatically archived and available for review on the ‘History’ screen.
• Added the ability to reset the logfiles via URL (http://IP of device/cmd.cgi?a=ClearLog). This is valuable for users with scripts that automatically retrieve the logfile at a specific interval and can now clear the file after it is retrieved.
• Added the ability to syncronize the time via URL (http://IP of device/cmd.cgi?a=SyncTime). When the URL is called, TemPageR will use current NTP settings to update the current date and time.
• Major updates were made to the ‘Status’ page.
  • Only the sensor data is updated on refresh to greatly increase refresh speed.
  • Custom refresh rates can be specified to update the sensor data.
  • Users can choose to display all sensors or only connected sensors.
  • Users can choose to display Fahrenheit or Celsius temperature values.
  • The thermometer graphic was enhanced for realism and now displays a different scale for Fahrenheit and Celsius values.
• Updated the ‘History’ page to provide links to the current ‘sensors.csv’ file as well as all available archived logfiles. Archived logfiles are renamed using the date the last entry was recorded.
• Improved the alert cleared functionality to only clear an alert after the temperature is at least one degree above or below the defined threshold. This greatly reduces multiple alerts caused when the current temperature hovers close to a defined threshold.
• Added a link to the ‘About’ page to connect to AVTECH.com and check for firmware updates.

v1.3.3

October 18, 2005

• Resolved an issue that caused the NTP time server to not be saved in certain cases.
• Adjusted the layout of the Settings applet to display all settings tabs consistently.

v1.3.2

October 11, 2005

• Added Daylight Saving Time support.
• Added ‘Logging Interval’ support. Users can now specify a logging interval from the default of every one (1) minute to 65,536 minutes.
• Added the ability to enter a specific Network Time (NTP) server to obtain the current date and time.
• Fixed an issue with the time calculation that caused the hour to be greater than 24 when certain timezones were selected.
• Modified the timestamp in the ‘sensors.csv’ file to put the date before the time to make it easier to sort temperature data.

v1.3.1

September 26, 2005

• Added Date support. The current date is now displayed next to the current time on the status screen and in the ‘sensors.csv’ file.
• Modified the Settings applet layout to make it easier to navigate the Advanced settings.
• Many more updates!

v1.3.0

August 25, 2005

• Added timezone support so the time is displayed in the correct local time both on the Status screen and in ‘sensors.csv’ logging file.
• Improved the Settings applet so settings are saved and loaded almost immediately. In most cases, there is no longer a wait for the settings to load from the device.
• Improved DHCP support so the ‘DHCP Device Name’ on the ‘Network’ tab of the settings will register properly with the DHCP server on the network.
• Added a link to the Status page in alert emails. This makes it easy to click a link and see the current temperature status when an alert email is received from TemPageR.
• Resolved an issue that prevented negative temperature readings from displaying.
• Resolved an issue with the settings password that would prevent users from accessing the settings page after an extended time period.
• Many more updates!

The post TemPageR Firmware Release Notes appeared first on AVTECH.

v4.5.0

April 3, 2012

• Added support for all modern web browsers. The web interface should now be fully functional in all web browsers, including IE8/9, Firefox, Chrome, Safari, Opera and others that conform to modern web standards. With full support for Chrome and Safari, the web interface can now also be viewed in mobile devices running Android and iOS.
• Added support for the JSONP protocol. This makes it much easier for users to incorporate sensor data from TemPageR devices into their own web pages without the challenges previously posed by cross-domain scripting restrictions.
• Updated the sensor output to conform to valid JSON formats.
• Added the ability to configure the date format displayed on the web interface and in email notifications to allow for customization in different international locales.
• Improved the way time is displayed in email notifications to more fully conform to the RFC standard.
• Added timestamps to the trace output to make it easier for our Technical Support team to identify the timing of certain background activities to facilitate quicker resolutions.
• Added a webpage that displays prior to accessing the Settings page that explains the default passwords used with AVTECH devices.

v4.0.1

June 24, 2011

• Resolved an issue that could cause the time included in email alert notifications to be off by one hour depending on the Daylight Saving Time setting.
• Removed the link to a PageR Enterprise FAQ since it is no longer supported in favor of Device ManageR.

v4.0.0

November 16, 2010

• Removed the ‘Logging’ feature so this and all future versions will no longer log sensor data to internal flash memory.
  • Over a period of time, the flash memory becomes un-writable, causing the unit to stop functioning properly. Disabling the Logging feature will prevent this from happening so the device can continue functioning reliably. Advanced Logging of unlimited sensor data is now possible through Device ManageR, which is the recommended method to use to log sensor data from any AVTECH device.
• Optimized the size of the web page files so they fit entirely in flash memory that was not previously used for logging.
• Added the ‘Display URL’ feature to email alert notifications so users can modify the link included at the bottom of email messages.
• Added the ability to define a timeout for SMTP Email communications. This timeout was previously hard-coded and could expire with slower internet connections.
• Added an option to automatically update the date and time via NTP at regular intervals.
• Added an option to disable Gratuitous ARP Packets from being sent periodically.
• Improved the ‘Save Settings’ and ‘Reset Settings’ features to be consistent with newer models.
• Removed the embedded ‘Trace Applet’ due to size restraints. When trace is enabled, it can be viewed by opening a telnet connection to the IP address of the device on the configured port.

v3.1.0

December 29, 2008

• Changed the default MTU to 1024 instead of 1400. This should reduce the occurrence of network connectivity issues with some managed switches and VPN connections.
• Added a MTU option to the Network settings so the MTU can be set to whatever is appropriate for the network it is connected to.
• Added additional error checking to SMTP requests to better diagnose email sending issues.
• Added the ability to define and save the default refresh interval of the Status page via the Advanced section of the Settings.
• Added the Device Name to email messages to make it easier to identify which unit the alert message was sent from when multiple units are installed.
• Resolved an issue that could cause the dates of December 29, 30 and 31 to be calculated incorrectly. These dates should all display properly with this version.
• Resolved an issue with the header response of the /mobile.txt page that could prevent it displaying in the BlackBerry browser.

v3.0.4

August 21, 2008

• Resolved an issue that caused some mail servers to prevent proper email authentication if the username or password contained a null character at the end.
• Resolved an issue that could cause email messages to fail to send if the mail server replies with a long response to the EHLO command. We now check for a 250 response indicating it is ‘OK’ to send and discard the remaining unused message.
• Resolved an issue that could cause email messages to fail to send if the mail server responded with an alternative error code to the EHLO command. We now correctly fall back to using HELO if the initial EHLO attempt fails and returns a code other than the 250 ‘OK’ message.
• Added an ‘Uptime’ value to the ‘/getdata.htm’ output for future use as a way to determine how long the device has been powered on.
• Added an ‘Uptime’ value to the trace output for future use as a way to determine how long the device has been powered on.

v3.0.3

May 30, 2008

• Combined the Email Server IP and Domain Name fields into a single field in the SMTP Email Settings Screen. It will now automatically determine whether an IP address or a domain name was entered and use the appropriate method to send the email. This previously caused an issue if a user entered a local IP address for their mail server and also added a domain name. In this situation, Room Alert 7E would attempt to resolve the IP address from the domain name instead of using the configured local IP address.
• Improved the validation of IP address fields in the Settings screens to prevent invalid IP address entry.
• Modified the prompts that appear during password modification on the Security Settings screen.
• Resolved an issue that could cause trace output to stop responding if email messages were too long.

v3.0.2

May 8, 2008

• Resolved an issue that could cause the MTU setting to not be applied correctly, preventing web access over VPN and other secure protocols.
  • MTU settings from 512 to 1400 can now be configured for users experiencing an issue viewing the web interface over a VPN connection.
• Resolved an issue that caused SNMP Trap messages to always be sent with a ‘public’ community string instead of the configured SNMP Community Name.
• Added a ‘View Tracing Output’ option to the Advanced Settings screen. This is especially useful for determining the cause of SMTP email issues as it shows all activity happening ‘behind the scenes’, including communicating with the email server.
• Added an option to disable the web interface for use in highly secure environments.
• Added an option to disable TFTP firmware updates for use in highly secure environments.
• Added an option to disable SNMP for use in highly secure environments.
• Added additional entry validation checks to the settings pages to prevent against invalid settings entry.
• Resolved an issue that could cause some Room Alert 7E units to appear as an unknown device with our new Device ManageR application.
• Modified the Security Settings screen to require the current password when changing to a new password.

v3.0.0

March 13, 2008

• Completely redesigned the Settings screen to use HTML forms instead of the Java Applet previously used. This provides a much more user friendly configuration interface that does not require any additional browser plugins to operate properly.
• Due to the additional space required for the updated Settings interface, the files used are now stored in a section of flash that was previously used by the Room Alert 7E logging function.
  • With this update, one of the archived logging sections is removed meaning that Room Alert 7E will actively log to one file and keep one (1) archived log file. For long term logging of sensor data, we highly recommend using AVTECH Device Manager.
  • If logging is currently enabled on your Room Alert 7E unit, please DISABLE logging before applying this firmware update to avoid any potential conflicts.
• Modified the way sensor thresholds are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, thresholds could only be configured in Fahrenheit.
  • If thresholds were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor thresholds are configured correctly.
• Modified the way sensor calibration values entered in the ‘Adjust’ field are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius).
  • Previously, the ‘Adjust’ value could only be entered in Celsius.
  • If ‘Adjust’ values were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor calibrations are configured correctly.
• Modified the Settings authentication to prompt for a password using the standard browser authentication entry display. The username field will *always* be left blank and the password (if configured) should be entered in the password field.
• Added SMTP Authentication capabilities to the email configuration and sending modules. A username and password can now optionally be provided for SMTP Authentication for use on servers that do not allow anonymous SMTP email messages.
• Added the ability to modify the SMTP port used for sending email. This will also benefit users who have mail servers that use alternate ports or do not allow mail submission on port 25.
• Modified the trace output feature to allow the port number to be modified. By default, a port of 143 is used if tracing output is enabled.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages and logging data.
• Added the ability to configure the DNS Server IP address via the telnet configuration menu.
• Added the MAC Address to the Status screen display to make it easier to identify multiple devices on the network.
• Added a new feature that allows users to send a test email by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=SendTestEmail’.
  • A button is also provided on the SMTP Email section of the Settings screen that will trigger a test email to be sent. Both of these new functions will only work if valid email settings are configured on the SMTP Email section of the Settings screen.
• Added a function to check the return code from a SMTP server on the initial connection instead of after each command. This resolves an issue that could occur if a SMTP server responds with an error code on the initial connection.
• Added a URL alias so sensor data can be accessed in JSON format at both ‘/getData.htm’ and ‘/getdata.htm’.
• Resolved an issue that could cause DHCP Names less than 8 characters long to save incorrectly.
• Resolved an issue that could cause the SNMP ‘SysObjectID’ variable to return an incorrect value.

v2.7.0

September 19, 2007

• Added a ‘tracing’ function to help diagnose issues such as email alerts not being sent.
  • When enabled through the telnet menu, tracing information will now be output to port 87223.
  • This tracing information can be saved to a file that can be sent to AVTECH Support by executing the command ‘telnet 87223 -f C:\RA7E.tra’, replacing with the IP address of the Room Alert 7E and modifying the file path if desired.
• Updated the timezones so now intermediate timezones such as Newfoundland (GMT-3:30) and India (GMT+5:30) are supported.
  • As a result of this change, some users might have to update their timezone setting on the ‘Advanced’ tab after the firmware upgrade. Most should be updated automatically.
• Added a link to our ‘Live Sales Support’ on the About screen. This makes it easy to speak with one of our Product Specialists regarding purchasing additional sensors or devices.
• Added a new webpage display option designed specifically for mobile devices such as mobile phones and PDAs. The new URL ‘http://(IP of Device)/mobile’ will display a text only output of all current sensor data.
• Added a new feature that allows users to reset the high and low values for sensors by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=ResetHighLow’.
• Added the ability to modify the SMTP port used for email via the Telnet configuration menu.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Added an option to return sensor values in a two digit format instead of the default four digit format when queried via SNMP. This option can be configured through the Telnet configuration menu.

v2.6.0

March 7, 2007

• Added support for Email-To-SMS messages. When this option is selected, Room Alert 7E will send email alerts with minimized text content for more efficient display on mobile devices.
• Resolved an issue that caused logging to stop functioning after writing the third logfile instead of overwriting the oldest file.
• Resolved an issue that caused web pages not to load after a firmware update if the web interface was open while a firmware update was in progress.
• Resolved an issue with email notifications that caused email not to be sent if the mail server sent telnet control characters to Room Alert 7E.

v2.5.1

December 22, 2006

• Resolved an issue with Internet Explorer 6 and 7 that caused the settings password to not be accepted. Other browsers were unaffected.
• Added a progress bar to the settings applet to indicate when the device is saving settings or rebooting.

v2.5.0

December 12, 2006

• Major update of the Room Alert 7E operating system. AVTECH Device Discovery Utility v2.5.3 or higher *MUST* be used to install this update.
• Increased the memory available for the web interface which will result in increased responsiveness.
• Increased the size of the ‘Return Address’ field on the Email tab so email addresses up to 42 characters may be entered.
• Modified the ‘Recipients’ field on the Email tab. Multiple email addresses can now be entered in a single field and separated by a semi-colon. If an email address had previously been entered in the ‘Email Recipient 2’ field, it should be re-entered in the new field.
• Added support for Dynamic DNS. The name of the device should now be registered as the hostname on the DHCP and DNS servers if the network is configured to allow this.
• Improved the Alarm engine to reduce repetitive alarms. The temperature will have to return one (1) degree below the defined threshold before the alarm will be cleared. This prevents alarms from being set and cleared repetitively if the current temperature is very close to the threshold defined.
• Resolved an issue that caused the Settings page not to display after entering a valid password.
• Added a ‘Help’ menu option that provides links to support resources on AVTECH.com and lists the available Technical Support contact methods.
• Added the data and time the alert was generated to the body of email alerts.
• Improved the email alert functionality to provide more detailed email alert messages.
• Added an option to disable the email footer send by default in email alert messages. This is useful if email alerts are sent primarily to mobile devices with character limitations.

v2.0.3

November 1, 2006

• Resolved web interface issues introduced with the release of Internet Explorer 7.
• Added a ‘Help’ screen to the web interface that provides quick access to various support resources.
• Improved the Sensor Loading function on the Status screen to retry if the initial connection fails.
• Removed the ‘X-Priority’ header from email messages and added an extra line break before the body text to resolve an issue with certain mail servers.

v2.0.2

March 22, 2006

• Resolved an issue that prevented negative temperatures from displaying correctly.
• Added negative threshold support. Negative temperature thresholds can now be specified on the ‘Alerts’ tab.
• Resolved an Internet Explorer specific issue that caused the Status screen to ‘flicker’ when the data refreshed.
• Adjusted the thermometer display to improve visual accuracy and match the current temperature more closely.
• Resolved an issue that caused periodic device reboots when accessing the Status screen.
• Updated the firmware update process so logfiles are no longer erased. A future version of the Device Discovery Utility will provide an option to erase the logfiles. Logfiles can also be cleared on the ‘Logging’ tab in Settings.
• Resolved a display issue that occurred when only two external sensors were connected.

v2.0.1

January 5, 2006

• Modified the ‘Network’ tab to only save static IP settings if a valid Gateway and Subnet Mask has been specified.
• Resolved an issue that caused incorrect status icons to be displayed when certain alarm thresholds were defined.
• Edited some text and default field values in the Settings applet.

v2.0.0

December 23, 2005

• Added floating point support. Temperatures are now recorded and logged with floating point precision up to one-hundredth of a degree.
  • NOTE: Users monitoring their Room Alert 7E devices via SNMP will have to update the SNMP Queries to support the new floating point feature (i.e. 75 is now 7500).
• Added additional logging capability. Up to three logfiles are now stored. When the file size limit is reached, the current logfile is automatically archived and available for review on the ‘History’ screen.
• Added the ability to reset the logfiles via URL (http://IP of device/cmd.cgi?a=ClearLog). This is valuable for users with scripts that automatically retrieve the logfile at a specific interval and can now clear the file after it is retrieved.
• Added the ability to syncronize the time via URL (http://IP of device/cmd.cgi?a=SyncTime). When the URL is called, Room Alert 7E will use current NTP settings to update the current date and time.
• Major updates were made to the ‘Status’ page.
  • Only the sensor data is updated on refresh to greatly increase refresh speed.
  • Custom refresh rates can be specified to update the sensor data.
  • Users can choose to display all sensors or only connected sensors.
  • Users can choose to display Fahrenheit or Celsius temperature values.
  • The thermometer graphic was enhanced for realism and now displays a different scale for Fahrenheit and Celsius values.
• Updated the ‘History’ page to provide links to the current ‘sensors.csv’ file as well as all available archived logfiles. Archived logfiles are renamed using the date the last entry was recorded.
• Improved the alert cleared functionality to only clear an alert after the temperature is at least one degree above or below the defined threshold. This greatly reduces multiple alerts caused when the current temperature hovers close to a defined threshold.
• Added a link to the ‘About’ page to connect to AVTECH.com and check for firmware updates.
• Added a status icon to the switch sensor display. The icon will be red is there is an alarm and green otherwise.
• Improved the NTP feature to try to obtain the network time before logging sensor data if the time has not been set yet. It will attempt to obtain the network time up to 5 times. This is in addition to obtaining the network time when TemPageR boots and should eliminate an issue where the time is not obtained if TemPageR boots before the NTP server in the event of a power loss.
• Improved the Alarm engine to reduce repetitive alarms. The temperature will have to return one (1) degree below the defined threshold before the alarm will be cleared. This prevents alarms from being set and cleared repetitively if the current temperature is very close to the threshold defined.

v1.3.6

October 11, 2005

• Resolved an issue that caused the hour to be calculated incorrectly for some timezones.

v1.3.5

October 7, 2005

• Added a ‘Logging Interval’ option and a new ‘Logging’ tab to the Settings applet. Users can now change the logging interval from the default of one (1) minute to any number of minutes up to 65,535. This allows users to store logging data for much longer periods of time before the file wraps back to the beginning again.
• Improved the time display by adding support for Daylight Saving Time (DST). Users can optionally configure DST and the time will be updated accordingly.
• Added the ability for users to specify their own Network Time (NTP) server to obtain the current time and date.

v1.3.2

September 30, 2005

• Added date support. The current date now appears next to the current time on the Status screen and in the ‘sensors.csv’ logging file with NTP enabled.
• Improved the layout of the Settings applet making it easier to navigate and change the settings on the device.

v1.3.1

September 8, 2005

• Added timezone support so the time is displayed in the correct local time both on the Status screen and in ‘sensors.csv’ logging file.
• Improved the Settings applet so settings are saved and loaded almost immediately. In most cases, there is no longer a wait for the settings to load from the device.
• Improved DHCP support so the ‘DHCP Device Name’ on the ‘Network’ tab of the settings will register properly with the DHCP server on the network.
• Added a link to the Status page in alert emails. This makes it easy to click a link and see the current temperature status when an alert email is received from Room Alert 7E.
• Resolved an issue that prevented negative temperature readings from displaying.
• Resolved an issue with the settings password that would prevent users from accessing the settings page after an extended time period.
• Modified the browser refresh to perform reliably in all modern browsers.
• Many more updates!

v1.0.0

• First official release of Room Alert 7E firmware.

The post Room Alert 7E Firmware Release Notes appeared first on AVTECH.

v3.5.1

September 14, 2011

• Added a page that displays when a user clicks the ‘Settings’ link that explains the default password and how to enter the username and password into the web browser prompt.
• Resolved an issue that could cause WiSH Sensor packets to be interpreted incorrectly, causing an unusually high number of invalid packets.
• Resolved an issue that could cause the incorrect sensor label to be used for SNMP Traps sent for WiSH Sensor alerts that have cleared.

v3.5.0

August 2, 2011

• Added a button to the WiSH Sensors tab of the Settings Screen that allows users to reset the settings for an individual WiSH Sensor.
  • This was previously only possible via the Telnet menu.
• Added a button to the WiSH Options tab of the Settings Screen that allows users to reset the settings for all WiSH Sensors.
  • This was previously only possible via the Telnet menu.
• Updated the WiSH Timeout field on the WISH Options tab of the Settings Screen so it is consistent with the Telnet menu. The minimum entry allowed for this field is ten (10).
• Resolved an issue that could cause the time printed in email alerts to be off by one hour depending on the Daylight Saving Time setting.
• Resolved an issue that could cause the incorrect Heat Index threshold to be displayed in email alert notifications.
• Resolved an issue with the WiSH Sensor Missed Packets option in the telnet setting configuration so the current setting is retained if the user presses the ‘Enter’ key.

v3.4.2

August 26, 2010

• Resolved an issue that could cause the Heat Index to be calculated incorrectly when the humidity or temperature was too low.
• Added the ability to disable periodic Gratuitous ARP packets from being sent.
• Resolved an issue with the NTP Auto Update feature that could cause it to report that the time was updated successfully when it was not.

v3.4.1

June 9, 2010

• Resolved an issue that could cause certain WiSH Serial Numbers to not be processed properly by the new whitelist and blacklist feature.
• Improved the blacklist feature so it will remove the configuration for any previously configured WiSH Sensor when it is added to the blacklist. This creates space for additional WiSH Sensors to be discovered and added.

v3.4.0

May 27, 2010

• Added a new ‘WiSH Sensor Filter’ feature that allows users to specifically select which WiSH Sensors should be allowed and which WiSH Sensors should be blocked.
  • This is especially useful in environments with multiple Room Alert 26W units in the same room or within the same wireless vicinity.
  • Users can now configure certain WiSH Sensors to associate with one Room Alert 26W and other WiSH Sensors to associate with the other Room Alert 26W.
• Added a new feature that allows the Room Alert 26W to optionally automatically synchronize the date and time with the configured NTP server at regular intervals. Available intervals include 10 minutes, 60 minutes and 6, 12 and 24 hours.
• Resolved an issue that was preventing the 2-digit SNMP option from working on external sensors connected to WiSH Sensors.
• Resolved an issue that could cause an invalid community name to be sent with SNMP Trap messages.
• Resolved an issue that could cause the Heat Index to be calculated incorrectly when the humidity or temperature was too low.
• Resolved an issue that could prevent a valid 0 Volt reading from being applied as the low reading for the Digital Power Sensor.

v3.3.0

December 10, 2009

• Resolved an issue that could cause Digital Power Sensors to report false 0V alarms that would immediately clear. Most of these false readings are now properly filtered out.
• Added additional false alarm checking to all Digital Power Sensor readings.
• Added the ability to configure the timeout value used for email communication on the ‘SMTP Email’ screen in Settings. The default value is 5 seconds and the setting supports values from 1-99 seconds.
• Resolved an issue that could cause Powered WiSH and WiSPR Sensors to incorrectly report a low battery voltage.
• Resolved an issue that caused the ‘Last Packet Received’ time reported for WiSH Sensors to be incorrect in ‘Lost Communication’ alert emails.
• Increased the size of internal variables used for email messages to prevent possible overruns due to longer email messages.
• Improved the formatting of the date and time sent in the headers of email alerts to prevent some email clients from interpreting the date incorrectly.

v3.2.3

May 26, 2009

• Resolved an issue that caused ‘Adjust’ values applied to the external sensors connected to WiSH and WiSPR Sensor to be scaled incorrectly.
• Resolved an issue that could cause an incorrect checksum value on WiSH Sensor packets, causing otherwise valid packets to be discarded.
  • This could cause WiSH Sensors to periodically lose communication or not appear at all.

v3.2.2

April 28, 2009

• Added the ability to modify the port used for HTTP requests. This was previously hard-coded to use port 80.
• Added the ability to modify the URL that is displayed at the bottom of email alert notifications.
  • This allows users to define a WAN IP or DNS name so the link can be clicked and viewed from outside the local network if external access is configured.
• Resolved an issue that caused the Device Name instead of the Sensor Name to be included with Alarm Cleared SNMP Trap messages.
• Resolved an issue that caused the current date and time to be included with WiSH Lost Communication Alarms instead of the last date and time a packet was received from the WiSH Sensor.

v3.2.1

February 23, 2009

• Added the Device Name to SMS formatted WiSH Lost Communication emails.
• Resolved an Internet Explorer issue on the Sensor Settings page. All other web browsers were unaffected.
• Resolved an issue that could cause an error when saving WiSH Sensors with a second digital sensor connected.
• Modified the SMTP email process to recognize the last response code sent instead of the first.
  • This resolves an issue that could occur with some email servers that sent back more data in the response than expected.
• Corrected an issue with decimal ‘Adjust’ values so they are only applied to Digital Temperature Sensors.
  • Digital Temp/Humidity and Digital Power do not use decimal ‘Adjust’ values.
• Corrected an issue that caused ‘Adjust’ values to be applied incorrectly to WiSH Sensors.

v3.2.0

February 17, 2009

• Major improvements made to the processing of wireless packets received from WiSH and WiSPR Sensors. This should result in much fewer dropped packets and improved reliability.
• Improved false alarm checking for Digital Power Sensors.
  • This will result in increased accuracy and reduced invalid spikes that can interfere with accurate high and low values, logging and graphing.
  • This improved false alarm checking will also reduce the number of alert emails sent for invalid spikes.
• Improved the progress bar used when saving setting via the web interface. It is now smoother and more accurately represents the current status of the setting save and device reboot.
• Added the ability to remove or reset WiSH Sensors that are no longer responding by simply clicking the link from the Status page.
  • This will reset all WiSH Sensor information for this single WiSH Sensor, including all labels and thresholds. The link to do this will appear automatically when a WiSH Sensor stops responding or loses communication with the Room Alert 26W.
• Added support for decimal ‘Adjust’ values to be used to calibrate sensor values.
• Added a progress bar to the initial settings page load to allow the settings to be read properly from the device before displaying the configuration page. This should eliminate the occasional error loading settings from the device.
• Added a new ‘WiSH Options’ settings screen.
  • This will allow users to Enable/Disable WiSH Lost Communication Alarms, configure the number of missed packets before a Lost Communication alert is triggered, the number of WiSH Sensors allowed, and the channel that the Room Alert 26W wireless radio operates on.
  • These are settings that were previously either unavailable or only in the telnet configuration menu.
  • Note that the WiSH Channel should not be modified unless directed by AVTECH Technical Support.
• Added an option to the telnet configuration menu to allow users to configure the level of desired false alarm checking when processing switch sensor alarms.
  • By default, a switch sensor needs to be in an alarm state for 3 consecutive scans before triggering an alarm. This is now configurable from 0 to 5 scans before triggering an alarm.
• Resolved an issue that could cause values in the Lost Communication emails to display out of order.

v3.1.1

December 24, 2008

• Resolved an issue that could cause the dates of December 29, 30 and 31 to be calculated incorrectly. These dates should all display properly with this version.
• Addressed an issue that could cause false alarms from Digital Power Sensors that were not connected at the time.
• Corrected a slight pixel offset issue on the Status page that could appear in some browsers.

v3.1.0

November 20, 2008

• Added the device name to alert email notifications so it is easier to determine which device the alert was sent from.
• Added a signal strength output to the Status page and mobile web interface pages. This will show a green/yellow/red scale with the exact signal strength percentage displayed when the cursor is placed on the scale, making it much easier to determine optimal placement for WiSH and WiSPR Sensors.
• Improved the speed of sensor data processing which will result in slightly faster threshold checking and alarm triggering.
• Added an option to the telnet configuration menu to allow users to configure the level of desired false alarm checking when processing switch sensor alarms. By default, a switch sensor needs to be in an alarm state for 3 consecutive scans before triggering an alarm. This is now configurable from 0 to 5 scans before triggering an alarm.
• Changed the default MTU setting to 1024 instead of 1400. This should reduce the occurance of network connectivity issues when connected to managed switches that drop packets that do not match the stated MSS request.
• Added additional error checking to SMTP requests to better diagnose email sending issues.
• Added the ability to save the default refresh rate of the Status page on the Advanced tab of the Settings.
• Added the ability to define the MTU size of network packets on the Network tab of the Settings.

v3.0.3

September 23, 2008

• Resolved an issue that could cause email messages not to send if authentication was disabled.
• Added an ‘Uptime’ value to the trace output as a way to determine how long the device has been powered on.
• Resolved an issue that could cause the unit to stop responding if trace was left running for extended periods of time.

v3.0.2

September 15, 2008

• Updated fields and labels on the Settings screens to be consistent across all screens and options.
• Resolved an issue that could cause Digital Power Sensors to not send alarms if unplugged from main power.
• Increased the maximum voltage allowed for a Digital Power Sensor to 255VAC from 250VAC.
• Added support for displaying the ‘Heat Index’ value in Celsius in addition to the default of Fahrenheit.
• Added support for limiting the number of WiSH Sensors that can communicate with the Room Alert 26W. This is especially useful when multiple Room Alert 26W units are within range of each other so they only communicate with the desired WiSH Sensors.
• Added switch sensor initialization checks to prevent false alarms from being sent when the unit first boots.
• Added an ‘Uptime’ value to the trace output as a way to determine how long the device has been powered on.

v3.0.1

June 23, 2008

• Resolved an issue that could cause Digital Temperature Sensors to display a 32F reading when first connected.
• Resolved an issue that could cause SNMP Traps to fail to be processed due to an invalid SysObjectID value.
• Resolved an issue that could cause the value entered in the ‘Adjust’ field to change values due to incorrect rounding on sequential Sensor Settings saves.
• Resolved an issue that could cause email messages to fail to send if the mail server replies with a long response to the EHLO command. We now check for a 250 response indicating it is ‘OK’ to send and discard the remaining unused message.
• Resolved an issue that could cause email messages to fail to send if the mail server responded with an alternative error code to the EHLO command. We now correctly fall back to using HELO if the initial EHLO attempt fails and returns a code other than the 250 ‘OK’ message.
• Resolved an issue that could cause the humidity reading from a Digital Temp/Humidity Sensor connected to a WiSH Sensor to not be returned via SNMP.
• Resolved an issue that could cause the internal temperature sensor on a WiSH Sensor to not properly trigger alarms when certain thresholds were set.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages.
• Added a status message when sensor labels are saved so a blank web page does not display before the ‘Saving…’ progress bar.
• Added a new webpage display option designed specifically for mobile devices such as phones and PDAs that required a ‘Content Type’ to be passed with the page data. The new URL ‘http://(IP of Device)/mobile.txt’ will display a text only output of all current sensor data with a Content Type of ‘text/plain’. The URL ‘http://(IP of Device)/mobile’ will still display a text only output of all sensor data without the Content Type header.
• Added an ‘Uptime’ value to the ‘/getdata.htm’ output for future use as a way to determine how long the device has been powered on.
• Updated text displayed in the telnet menu to be more descriptive for some options and to resolve inaccuracies with others.

v3.0.0

May 23, 2008

• Completely redesigned the Settings screen to use HTML forms instead of the Java Applet previously used. This provides a much more user friendly configuration interface that does not require any additional browser plugins to operate properly.
• Modified the way sensor thresholds are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius). Previously, thresholds could only be configured in Fahrenheit.
  • If thresholds were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor thresholds are configured correctly.
• Modified the way sensor calibration values entered in the ‘Adjust’ field are saved so they can be entered in the currently configured temperature scale (Fahrenheit or Celsius). Previously, the ‘Adjust’ value could only be entered in Celsius.
  • If ‘Adjust’ values were previously configured, be sure to review the Sensors section of the Settings screen after applying the update to be sure all sensor calibrations are configured correctly.
• Modified the Settings authentication to prompt for a password using the standard browser authentication entry display. The username field will *always* be left blank and the password (if configured) should be entered in the password field.
• Increased the WiSH Sensor capacity to support up to fifteen (15) WiSH, Powered WiSH and WiSPR Sensors.
• Added SMTP Authentication capabilities to the email configuration and sending modules. A username and password can now optionally be provided for SMTP Authentication for use on servers that do not allow anonymous SMTP email messages.
• Added the ability to modify the SMTP port used for sending email. This will also benefit users who have mail servers that use alternate ports or do not allow mail submission on port 25.
• Modified the trace output feature to allow the port number to be modified. By default, a port of 143 is used if tracing output is enabled.
• Added a new webpage display option designed specifically for mobile devices such as mobile phones and PDAs.
  • The new URL ‘http://(IP of Device)/mobile’ will display a text only output of all current sensor data.
• Added support for Email-To-SMS messages. When this option is selected, Room Alert will send email alerts with minimized text content for more efficient display on mobile devices.
• Added the ability for the Heat Index value to be displayed for Temp/Humidity Sensors connected to WiSH Sensors.
• Added an option to display the time in the default 24 hour format or in 12 hour AM/PM format. This applies for the display on the Status screen as well as in email alert messages and logging data.
• Added the ability to configure the DNS Server IP address via the telnet configuration menu.
• Added the MAC Address to the Status screen display to make it easier to identify multiple devices on the network.
• Added a new feature that allows users to send a test email by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=SendTestEmail’.
  • A button is also provided on the SMTP Email section of the Settings screen that will trigger a test email to be sent.
  • Both of these new functions will only work if valid email settings are configured on the SMTP Email section of the Settings screen.
• Added a function to check the return code from a SMTP server on the initial connection instead of after each command. This resolves an issue that could occur if a SMTP server responds with an error code on the initial connection.
• Added a URL alias so sensor data can be accessed in JSON format at both ‘/getData.htm’ and ‘/getdata.htm’.
• Added an option to disable the web interface for use in highly secure environments.
• Added an option to disable TFTP firmware updates for use in highly secure environments.
• Added an option to disable SNMP for use in highly secure environments.
• Resolved an issue that could cause the MTU setting to not be applied correctly, preventing web access over VPN and other secure protocols.
  • MTU settings from 512 to 1400 can now be configured for users experiencing an issue viewing the web interface over a VPN connection.
• Resolved an issue that caused SNMP Trap messages to always be sent with a ‘public’ community string instead of the configured SNMP Community Name.
• Resolved an issue that could cause DHCP Names less than 8 characters long to save incorrectly.
• Resolved an issue that could cause the SNMP ‘SysObjectID’ variable to return an incorrect value.

v2.0.1

January 2, 2008

• Added support for the new Powered WiSH Sensor.
  • The Powered WiSH Sensor includes all of the functionality of the standard WiSH Sensor and uses AVTECH’s 5V Power Adapter, eliminating the need to replace batteries in the future.
• Removed the ‘Channel #’ reference from the WiSH Sensor display on the ‘Status’ page as there are no physical ‘Channels’ assigned as with the wired digital sensors. WiSH Sensors are displayed on the ‘Status’ page in the order that packets are received when the Room Alert 26W unit boots.
• Improved the code used to receive and process data packets received from WiSH Sensors to dramatically reduce the number of missed or incorrectly parsed WiSH data packets.
• Resolved an issue that could cause Switch Sensor alarms to be tripped and immediately cleared if set to alarm on ‘Open’ when the unit reboots.
• Modified the option to disable WiSH Sensor Lost Communication emails to apply to the ‘Alarm Cleared’ email as well when communication is restored with the WiSH Sensor.

v2.0.0

December 3, 2007

• Improved the efficiency of the sensor reading and parsing component.
  • This allows sensor values to be read from the sensors and saved quicker and should help reduce the chances of WiSH Sensor packets being lost.
• Added Heat Index monitoring. Click here to learn more about the Heat Index.
• Added Digital Power Sensor monitoring.
  • Room Alert 26W can now generate alarms for Voltage (V), Current (A), Power (W) and Apparent Power (VA) detected by AVTECH’s Digital Power Sensor.
• Added a ‘tracing’ function to help diagnose issues such as email alerts not being sent.
  • When enabled through the telnet menu, tracing information will now be output to port 911. This tracing information can be saved to a file that can be sent to AVTECH Support by executing the command ‘telnet *IP* 911 -f C:\RA26W.tra’, replacing *IP* with the IP address of the Room Alert 26W and modifying the file path if desired.
• Added the current date and time to Alert Cleared emails, making it easy to see the exact time when an alarm was cleared.
• Added the ability to disable Lost Communication Alarms for WiSH Sensors via the Telnet configuration menu.
• Added the ability to define how many missed WiSH Sensor packets should indicate an alarm condition via the Telnet configuration menu.
• Resolved an issue that could cause switch sensor alarms to be triggered when the unit reboots.
• Added the ability to modify the SMTP port used to send email notifications via the Telnet configuration menu.
• Added the ability to disable email notifications.
• Added a new feature that allows users to reset the high and low values for sensors by accessing the URL ‘http://(IP of Device)/cmd.cgi?action=ResetHighLow’.
• Updated the timezones so now intermediate timezones such as Newfoundland (GMT-3:30) and India (GMT+5:30) are supported.
  • As a result of this change, some users might have to update their timezone setting on the ‘Advanced’ tab after the firmware upgrade. Most should be updated automatically.
• Added an option in the telnet interface to configure the Ethernet speed and duplex and the MTU size.
• Improved the error checking code so incorrect readings from sensors caused by EMI or other interference will be filtered and ignored.
• Added a link to our ‘Live Sales Support’ on the About screen.
  • This makes it easy to speak with one of our Product Specialists regarding purchasing additional sensors or devices.
• Added an option to return SNMP sensor values in 2 digit format instead of the default 4 digit format via the Telnet configuration menu.
• Modified the SMTP engine to resolve the IP address of the mail server each time an email is sent if a hostname is specified.
  • Previously, the IP address was only resolved during the initial boot process.
• Modified the NTP engine to attempt to obtain the network time every 10-30 seconds if it has not yet been received.
  • Previously, the network time would be updated only during the initial boot process.
• Added a Fahrenheit temperature value to the WiSH Sensor SNMP data.
  • Previously, only Celsius values were provided via SNMP for WiSH Sensors.

v1.2.2

May 22, 2007

• Resolved an issue that could cause Temperature Sensors to not appear initially if the temperature is too high.

v1.2.1

May 21, 2007

• Resolved an issue that could cause Temp/Humidity Sensors to not appear initially if the temperature is too high.
• Resolved an issue that could cause alarms not to clear on external Temp/Humidity Sensors.

v1.1.0

January 25, 2007

• Increased the WiSH Sensor capacity to support up to 12 WiSH Sensors.
• Resolved a SNMP authentication issue that could cause the unit to deny all SNMP Query requests with certain community strings.
• Increased the efficiency of setting and reading WiSH Sensor configuration options by reducing the number of flash read/writes required.
• Resolved an issue with WiSH Sensors that could cause alarms for external sensors not to clear properly.
• Added a feature that disables the web interface while firmware updates are in progress to help prevent incomplete firmware updates.

v1.0.1

January 3, 2007

• Added an option to the Email tab of the Settings screen to disable the footer sent with email alerts. This can help reduce the size of email messages and is especially useful when sending email to mobile devices.
• Resolved an issue with the Email tab that prevented complex email addresses from being entered.
• Resolved an issue that caused the Status screen not to display in some versions of Internet Explorer.

v1.0.0

December 1, 2006

• First official release of the Room Alert 26W firmware.

The post Room Alert 26W Firmware Release Notes appeared first on AVTECH.