And you need those text alerts for compressor faults, temperature excursions, refrigerant leak trips, high discharge pressure, and more. Setting up email alerts is easy and still works.<\/p>\n\n\n\n
But nobody wakes up to an email. You wake up to a text.<\/p>\n\n\n\n
As you know well, the gap between a 20-minute response and a shift-change discovery is the gap between a service call and writing off a warehouse of product<\/strong>.<\/p>\n\n\n\n (According to The Global Cold Chain Alliance, the average cost of a significant temperature excursion is north of $150,000 for product, disposal, regulatory response, and the operational mess that follows. That’s one<\/em> event.)<\/p>\n\n\n\n In this article, I’ll walk you through how to turn your E3’s email alerts into SMS text messages on your phone<\/strong>. If you’ve already got SMTP configured, setup takes about a minute. (If you don’t, we’ll cover that too.)<\/p>\n\n\n\n We’ll also explain why the E3’s built-in SMS feature stopped working for you<\/strong> \u2014 and why the fix isn’t where you’d expect it to be.<\/p>\n\n\n\n Note: If you’re running older Emerson E2 controllers \u2014 the ones without native SMTP \u2014 that’s a different setup entirely. The E2 requires a supervisory layer to send email in the first place. (That’s covered in a separate guide.)<\/em><\/p>\n\n\n\n If you’ve had the E3’s built-in SMS working in the past (using the Mobile Phone field with carrier gateway addresses like @vtext.com), you may have noticed it stopped delivering. We’ll cover why that happened and what changed later in the article.<\/p>\n\n\n\n The short version: the carrier gateways that feature depended on have been shut down. The method below replaces it entirely.<\/p>\n\n\n\n text.email<\/a> is a email-to-SMS service<\/a> \u2013 and the only one that works immediately when you sign up.<\/p>\n\n\n\n You send an email to your special address, and it shows up as a text on your phone<\/strong>.<\/p>\n\n\n\n text.email handles A2P 10DLC carrier compliance<\/a> (the registration requirement that makes creating your own SMS pipeline a disproportionate pain for simple alert use cases).<\/p>\n\n\n\n Sign up, pick a private keyword for your account, and your delivery address becomes: Any email sent to that address arrives as a text. We’ll plug this address into your E3’s notification settings in Step 3.<\/p>\n\n\n\n If you already have email alerts configured for your E3, skip to Step 3.<\/p>\n\n\n\n If not, you need to tell the E3 how to send email. The simplest path is using a Gmail account as your SMTP relay.<\/p>\n\n\n\n Open a browser and enter the controller’s IP address. (Default is 192.168.0.250 for ETH0, 192.168.1.250 for ETH1.) Default credentials are username Navigate to Configure System<\/strong> \u2192 General System Properties<\/strong> \u2192 Network Settings<\/strong> \u2192 Advanced<\/strong>.<\/p>\n\n\n\n First, set up DNS<\/strong> so the controller can resolve smtp.gmail.com.<\/p>\n\n\n\n On the same Network Settings page, enter valid DNS servers in the DNS Server 1<\/strong> and DNS Server 2<\/strong> fields. Google’s public DNS (8.8.8.8 and 8.8.4.4) works fine if your IT team doesn’t have a preference.<\/p>\n\n\n\n Then, generate a Gmail App Password.<\/strong> This is the part that trips people up. Google killed “Less Secure Apps” access in 2024; you can’t just use your regular Gmail password for SMTP anymore.<\/p>\n\n\n\n Instead, you need an App Password, which is a 16-character code that Google generates specifically for devices like controllers and scanners that can’t do OAuth.<\/p>\n\n\n\n To get one:<\/p>\n\n\n\n Now configure the SMTP section on the E3:<\/p>\n\n\n\n Test the connection.<\/strong> Once SMTP is enabled, use the Test Email Address<\/strong> field on the same page to send a test. Make sure it arrives before moving on.<\/p>\n\n\n\n If you’re not using Gmail (maybe your facility runs its own mail server or uses Microsoft 365) the fields are the same, but you’ll need the SMTP server address, port, and authentication details from your IT team. Set the Authentication Type based on what your local server requires.<\/p>\n\n\n\n The one thing to watch: the sender email address must be a valid user on the SMTP server.<\/strong> If it isn’t, the controller will accept the settings but emails won’t actually send.<\/p>\n\n\n\n Here’s where you connect the E3’s email system to SMS delivery.<\/p>\n\n\n\n Now tell the controller which users should receive which alerts.<\/p>\n\n\n\n This filtering matters. You don’t want a text for every advisory \u2014 just the things that cost you product or compromise safety. We’ll give you some suggestions on what’s worth texting vs. what’s fine as email later in this article.<\/p>\n\n\n Send another test email from the SMTP settings page. This time, it should arrive as a text on your phone within seconds.<\/p>\n\n\n\n If it doesn’t:<\/p>\n\n\n\n Once you’ve confirmed a test text arrives on your phone, you’re set. Every alarm that passes your filter settings will now hit your phone as an SMS.<\/p>\n\n\n\n If you configured SMS on your E3 a while back and it quietly stopped delivering texts, you’re not going crazy. It broke, and it broke at the cell phone carrier level \u2014 not on your controller.<\/p>\n\n\n\n The E3’s “Text Messaging (SMS)” feature \u2014 the one in Network Settings with the SMS enabled<\/strong> toggle and From SMS address<\/strong> field \u2014 was built on top of carrier email-to-SMS gateways.<\/p>\n\n\n\n When you set up a user’s mobile phone number, the manual (P\/N 026-4049) told you to enter it in this format: The documentation lists examples like Wellllll\u2026 those gateways are dead.<\/p>\n\n\n\n Verizon killed vtext.com<\/a>. AT&T killed txt.att.net<\/a>. T-Mobile killed tmomail.net<\/a>.<\/p>\n\n\n\n The carriers shut them down because of A2P 10DLC compliance requirements and spam abuse. Plus, the gateways weren’t exactly generating significant (or any?) revenue, so when the regulatory burden increased, every major carrier pulled the plug.<\/p>\n\n\n\n Emerson’s documentation hasn’t been updated to reflect this<\/strong>. If you’re following the manual, you’re configuring a system that points at infrastructure that no longer exists. Seriously, I’m looking at the manual right now<\/em> and it’s filled with advice about using the carrier gateways.<\/p>\n\n\n\n (If ChatGPT recommended you use @vtext.com \u2014 same problem, different source. It’s working off outdated training data.)<\/p>\n\n\n\n The obvious next thought: set up your own email-to-SMS pipeline.<\/p>\n\n\n\n But sending application-to-person (A2P) SMS in the US now requires 10DLC registration with The Campaign Registry. That means registering your business, registering the purpose of your messages, and waiting for carrier approval.<\/p>\n\n\n\n Yes, even for something as straightforward as “my compressor faulted, tell me about it.”<\/p>\n\n\n\n The compliance overhead is completely out of proportion to the use case.<\/strong> It’s the same registration process whether you’re sending 5 alerts a month or 50,000 marketing messages.<\/p>\n\n\n\n Skip the E3’s SMS fields entirely.<\/p>\n\n\n\nEmerson E3 Refrigeration Controller Text Alerts: Table of Contents<\/h2>\n\n\n\n
\n
Setting Up Text Alerts on Your E3 \/ Site Supervisor \/ Lumity<\/h2>\n\n\n\n
Step 1: Sign up with text.email<\/h3>\n\n\n\n
yournumber@yourkeyword.text.email<\/code><\/p>\n\n\n\nStep 2: Configure SMTP on Your E3<\/h3>\n\n\n\n
Log into the E3 web interface<\/h4>\n\n\n\n
user<\/code>, password pass<\/code> \u2014 though if those haven’t been changed, you’ve got a bigger problem than alert configuration, especially post-Frostbyte10.<\/p>\n\n\n\nUsing Gmail as your SMTP relay<\/h4>\n\n\n\n
\n
\n
![\"Emerson](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/emersone3-networksettings-tinified-1024x551.png\")
<\/a><\/figure>\n<\/div>\n\n\nUsing a different SMTP server<\/h4>\n\n\n\n
Step 3: Add your text.email address as a notification recipient<\/h3>\n\n\n\n
\n
yournumber@yourkeyword.text.email<\/code><\/li>\n\n\n\n![\"Manage](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/emersone3-manageusers-tinified-1024x681.png\")
<\/a><\/figure>\n<\/div>\n\n\nStep 4: Set up alarm communications<\/h3>\n\n\n\n
\n
\n
![\"Set](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/emersone3-alarmcomm-tinified-1024x190.png\")
<\/a><\/figure>\n<\/div>\n\n\nStep 5: Test it<\/h3>\n\n\n\n
\n
yournumber@yourkeyword.text.email<\/code><\/li>\n\n\n\nWhy the E3’s Built-In SMS Stopped Working<\/h2>\n\n\n\n
What happened?<\/h3>\n\n\n\n
phonenumber@carrier_txt_domain<\/code>.<\/p>\n\n\n\n5551234567@vtext.com<\/code> and walks you through the carrier domains for each US provider.<\/p>\n\n\n\nWhy building your own fix isn’t worth the effort<\/h3>\n\n\n\n
So what is<\/em> the right fix?<\/h3>\n\n\n\n