Knowledge Base  /  Frequently Asked Questions  /  RoomAlert.com

How To Troubleshoot A Room Alert Monitor’s Sensor Data Pushes Not Getting Through To RoomAlert.com

If your Room Alert Monitor is successfully communicating with RoomAlert.com, you’ll see the device listed in your Devices Inventory with a green status icon. In the image to the right:

Example RA32E is communicating with our Room Alert Account.

Example RA12E and Example RA4E are not communicating with our Room Alert Account.

 The push feature on Example RA3E is disabled, so this unit is also not communicating with the account.

If your device does not have a green status icon…

First check if you can access your Room Alert Monitor locally. If you’re on the same subnet as the device, type its IP address directly into your web browser’s address bar.

If the web interface successfully loads, please continue with the steps below to determine why the pushes to RoomAlert.com aren’t getting through.

Step 1: Check your device's firmware version.

In order to push its sensor data to RoomAlert.com, your compatible device must be running at least the minimum firmware version listed below.

Models Compatible with RoomAlert.com

ModelMinimum Firmware VersionRelease Date
Room Alert 32Sv.1.0.1February 11, 2020
Room Alert 12Sv.1.2.0July 16, 2020
Room Alert 32Ev2.4.0July 18, 2014
Room Alert 32W (legacy)v2.4.0July 18, 2014
Room Alert 12Ev2.1.0August 8, 2014
Room Alert 4Ev3.2.0August 20, 2014
Room Alert 3Ev1.3.0August 8, 2014
Room Alert 3 Wi-Fiv1.0.0February 28, 2015
Step 2: Check the information in the Device Details page.

Click on a Room Alert Monitor in the Devices Inventory list to open its Device Details page.

The Push Status is listed in the Device Details at the top of the page.

indicates that the device is successfully pushing sensor data to the account.

indicates that the device hasn’t pushed data to the account in at least 2 hours.

indicates that the device hasn’t pushed data to the account since before the last RoomAlert.com release.

 indicates that the push feature is disabled on the Room Alert Monitor.

For instructions to enable the push feature, please see How To Enable/Disable Push To RoomAlert.com.

If your device was previously communicating with the Room Alert Account and suddenly stopped, take note of the “Last push received” timestamp.

Did you make any changes to the device on this date? Were any network changes introduced on this date?

Step 3: Check your Room Alert's IP address configuration.

If your Room Alert Monitor is configured with a static IP address, check its settings for any invalid addresses or typos.

If you suspect that the issue might be related to your DNS server, try using a public DNS, such as Google’s, which is 8.8.8.8.

Step 4: Check your network's security settings.

The Room Alert Monitor pushes its sensor data out over HTTP port 80 to your account at RoomAlert.com. HTTP port 80 is commonly open, but it’s possible that your firewall may be blocking traffic on this port. If so, please allow traffic from the Room Alert Monitor to pass through.

If you’re using a proxy server, please configure a rule to allow your Room Alert Monitor to push its sensor data directly to push.roomalert.com.

It’s possible that some security applications on the network may block Room Alert pushes, as well. We recommend checking all security settings, such as web filters, etc., to check if they may be interfering with Room Alert.

Step 5: Manually trigger a push while capturing a trace to diagnose the issue.

In order to determine why your pushes to RoomAlert.com are failing, you can capture a trace from your unit while you manually trigger a push.

These instructions require Telnet. The Telnet client is disabled by default in Windows versions Vista and above. Please see this FAQ for instructions on enabling it: How To Enable Telnet In Windows (Versions Vista And Above).

Select your Room Alert model below for the proper instructions.

Room Alert 32S & 12SRoom Alert 32E/W, 12E, 4E and 3ERoom Alert 3 Wi-Fi

To manually trigger a push to RoomAlert.com while running a trace on your Room Alert Monitor, you’ll be:

A. opening a Windows Command Prompt,

* If you cannot use Windows Command Prompt, you may instead use PuTTY or Mac Terminal.

B. starting a trace on your Room Alert Monitor, and then

C. manually triggering a push to RoomAlert.com.

The instructions below show you how.

A. First, open a Windows Command Prompt window.

B. In the Command Prompt window, begin a trace on your Room Alert monitor:

Please follow the instructions in this FAQ to capture a trace directly to a text file: How To Generate A Trace On A Room Alert Monitor.

C. Then trigger a push from your device to RoomAlert.com.

  1. Open your Room Alert Settings pages. This FAQ shows you how: How To Access A Room Alert Monitor’s Settings Pages.
  2. Go to the Advanced Settings page.
  3. Under the RoomAlert.com section of the page, select the Send Push button.

D. Leave the trace open for about a minute to capture all the necessary data. Then you may close the Command Prompt window, and check for common errors in the trace file.

To manually trigger a push to RoomAlert.com while running a trace on your Room Alert Monitor, you’ll be:

A. opening 2 Windows Command Prompts,

* If you cannot use Windows Command Prompt, you may instead use PuTTY or Mac Terminal.

B. starting a trace on your Room Alert in one of them, and then

C. manually triggering a push to RoomAlert.com in the other.

The instructions below show you how.

A. First, open two Windows Command Prompt windows.

B. In the first Command Prompt window, begin a trace on your Room Alert Monitor:

Please follow the instructions in this FAQ to capture a trace directly to a text file: How To Generate A Trace On A Room Alert Monitor.

C. Then, in the second Command Prompt window, trigger a push using the Room Alert Monitor’s Telnet menu:

  1. At the prompt enter the following command:

    telnet [IP address of the unit] 9999
    Example: telnet 192.168.2.100 9999
  2. If you are prompted for your Room Alert Monitor’s password, enter it and then press the Enter key on your keyboard. Otherwise, simply press Enter.

    You must press Enter within a few seconds or you’ll get a “Connection to host lost” message. If you see that message, press Enter to get the prompt back and re-enter the telnet command from Step 1.
  3. The Telnet menu will appear. At the “Your choice?” prompt, enter 81, which will trigger a push to RoomAlert.com.

D. Leave the trace in the first Command Prompt window open for about a minute to capture all the necessary data. Then you may close the Command Prompt window, and check for common errors in the trace file.

To manually trigger a push to RoomAlert.com while running a trace on your Room Alert 3 Wi-Fi, you’ll be:

A. opening a Windows Command Prompt,

* If you cannot use Windows Command Prompt, you may instead use PuTTY or Mac Terminal.

B. starting a trace on your Room Alert 3 Wi-Fi, and then

C. manually triggering a push to RoomAlert.com.

The instructions below show you how.

A. First, open a Windows Command Prompt window.

B. In the Command Prompt window, begin a trace on your Room Alert 3 Wi-Fi:

Please follow Step 2 of the instructions in this FAQ to capture a trace directly to a text file: How To Generate A Trace On A Room Alert Monitor: Step 2.

C. Then trigger a push from your Room Alert 3 Wi-Fi to RoomAlert.com by using one of the following methods:

  • Insert a bent paper clip into the unit’s switch sensor port so that it bridges the 2 contacts. This will change the state of the switch sensor from open to closed and therefore trigger a push.
    • The switch sensor port is the one with the little grey buttons on the back of the unit next to the vent. You may view it here in the image labeled “Back”: Room Alert 3 Wi-Fi Product Tour.
  • Disconnect your external digital sensor from the RJ-11 port on the back of the unit. (You may then reconnect it.) Disconnecting or reconnecting a digital sensor will trigger a push.
  • Hold the Room Alert 3 Wi-Fi in your hands to warm it. An increase of 2 degrees Celsius on the internal temperature sensor will trigger a push.

D. Leave the trace open for about a minute to capture all the necessary data. Then you may close the Command Prompt window, and check for common errors in the trace file.

Step 6: Check for common errors in the trace file.

This example trace shows a successful push to RoomAlert.com:

In the first line shown, you can see the request to send a manual push to RoomAlert.com. Within the next few lines, the IP address for push.roomalert.com gets resolved and the connection is established. You can see the response from RoomAlert.com in the red box.

Below are some example errors that you may see with an unsuccessful push to RoomAlert.com.

0.0.0.0 Push IPConnection timed outBlank 'httpresp' lineHTTP Errors

If you see “IP resolved to 0.0.0.0,” your Room Alert Monitor could not properly resolve the IP address for push.roomalert.com; in most cases, this means that there’s an issue with the configured DNS server.

For troubleshooting recommendations, see Step 3.

If you see “RAC Push connection timed out,” it usually means that a security setting on the network is blocking the push.

For troubleshooting recommendations, see Step 4.

If there’s no response printed after the “httpresp:” line, this typically means that something on the network stripped the data out of the push.

For troubleshooting recommendations, see Step 4.

If you see “400 Bad Request,” “403 Forbidden” or another error in the HTTP response, a proxy server is most likely interfering with the push data.

Please set up a rule to allow the Room Alert device to push its data directly to push.roomalert.com.

If you require additional assistance, please send your trace file to us at Support@AVTECH.com.

Want to know if your device goes offline again? Set up an alert by following the instructions in our FAQ, How To Configure A ‘Not Pushing’ Alert In Your RoomAlert.com Account.

Facebooktwitterredditpinterestlinkedinmail

Room Alert Manager - Compatible Devices

The latest version of Room Alert Manager supports only the devices below.

It does not support any legacy Room Alert or TemPageR models.

~~~

Note about support for the Room Alert 3W:

1. You must have this model at default credentials for compatibility with Room Alert Manager. Username: admin | Password: PASSWORD.

2. Room Alert Manager does not currently support firmware updates for this model.

Custom credentials and firmware updates for the Room Alert 3W will be included in a future release of Room Alert Manager.

~~~

Current S modelsCurrent E models
Room Alert 32SRoom Alert 32E
Room Alert 12SRoom Alert 12E
Room Alert 4E
Room Alert 3E
Room Alert 3W at default credentials (Username: admin | Password: PASSWORD)