10 ft. Genesis 22-Gauge 4-Conductor (22/4) Wire Posts

Posted By

We would like to inform you about a temporary delay affecting some recent orders. Due to a major system upgrade on our vendor’s end, certain shipments are taking a little longer to process than usual. This may affect orders placed between Thursday, the 24th at noon, and today. Orders placed in the next couple of days may also be impacted.

Please rest assured—if you selected fast or expedited shipping, your order will still ship using that method and will arrive as quickly as possible once processed.

We are actively working with our vendor to move orders through the system and get them out the door as quickly as possible. We’re confident this situation will be short-lived and we’re here to support you every step of the way.

If your order is past the expected timeframe outlined in our shipping policy, feel free to reach out by emailing us here. This will open a support ticket and our team will get back to you as soon as possible.

Thank you for your patience and continued support of Alarm Grid. We will continue to provide any further updates as we receive them.

Tags: , , , ,

Comments


Posted By

Update 6:46 PM 05/12/25: Per AlarmNet and Resideo, both Total Connect 2.0 and alarm communications are fully restored. This update isn't time stamped, so it's unclear exactly when services were restored. Alarm dealers may continue to see some issues in programming legacy devices and video-only accounts. PRO Series and VISTAH3 device programming is completely restored.

Original Post:

AlarmNet has alerted all dealers to an issue with their communicators that began at 8:15 AM today. They are investigating the issue and working diligently toward a solution. Preliminary investigation shows that this interruption is not the result of malicious activity or a security breach.

What You May See:

As a result of this issue, you may have seen a communicator failure message on your system. This could show up as a "Check 103" message, "Reporter Failure", and possibly others. You may also have noticed issues logging into Total Connect 2.0, or delays or failures in completing commands using TC2.

According to AlarmNet, they are seeing some system recovery with improvements in latency, etc. However, the AlarmNet network is still not at 100%, so if you notice an issue logging into Total Connect 2.0, or an issue with sluggish or failed command execution, this is why.

In the past, we've seen queued signals and notifications being delivered once communication is restored. This can present as a notification coming through that seems out of place. For example, you may receive a notification that your system was disarmed when you know that you armed it. This is just a disarm notification from a previous instance that was delayed in being delivered. The best thing to do is log into Total Connect 2.0 and verify your system status. You can check the panel's event log to confirm exactly what has taken place on your system.

What You Can Do:

If you receive a trouble message on your system you silence it by acknowledging it. This process can vary depending on what system you're using. On a VISTA system, press any key on the keypad to silence the trouble beeping. Enter a disarm sequence by pressing your four-digit code plus one (1) or OFF. Do this twice.

If the communication issue has been resolved, the second disarm command will clear the trouble message from your keypad. If not, the message will remain until the condition has been resolved and you enter a disarm command again.

On the various touchscreen panels or keypads, you should be able to follow prompts on the display to silence and clear the trouble message. On the PRO Series panels, tap the red alert indicator at the bottom right of the display. This will silence the trouble beep and bring up the alert screen. Any active trouble conditions will be displayed. Press "Clear" at the upper right and enter a valid user code.

As with a VISTA system, if the trouble condition has been resolved, this will clear the display. If not, the message will remain under "Active Issues" until the trouble condition is resolved. In this case, until whatever is causing the communication problems has been taken care of. Once the condition has been resolved, press "Clear" again and enter your user code to clear the message.

Stay tuned, as we receive updates we'll update this blog post with any available information.

Tags: , , , , , , , , , , , ,

Comments