Knowledge Base
/
Release Notes
/
Room Alert Firmware
/
Legacy Models
TemPageR 3E Firmware Release Notes TemPageR 3E Firmware v3.0.1 Released 10 April 2013
Firmware for your TemPageR products is available at RoomAlert.com.
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.