Not sure if something is going on at Google, but was just testing a new notification and found that my Gmail wasn’t working either. Gave the “tls error” message. Tried several changes and no joy. Changed to using the Use Default (not Gmail)and it’s working now. Mine was working with Gmail as late as 2-18-2026.

18 hours ago, BCreekDave said:

Not sure if something is going on at Google, but was just testing a new notification and found that my Gmail wasn’t working either. Gave the “tls error” message. Tried several changes and no joy. Changed to using the Use Default (not Gmail)and it’s working now. Mine was working with Gmail as late as 2-18-2026.

I am now getting the same error (using a Gmail account). The last time mine worked was 7:30am PST on Monday, Feb 23.

@BCreekDave and @Ross no issues running a test message or triggering a program notification using Gmail settings that I've had for many, many years. I don't have a regularly scheduled notification setup so just based on testing now things worked as expected. Make sure you are not sending a lot of messages (not sure what would be "a lot") perhaps Gmail is blocking too many attempts to send notifications.

Be sure you've setup in accordance to the wiki information:

https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_for_Use_with_gmail

Be sure that your timeout setting is high.

3 hours ago, Geddy said:

@BCreekDave and @Ross no issues running a test message or triggering a program notification using Gmail settings that I've had for many, many years. I don't have a regularly scheduled notification setup so just based on testing now things worked as expected. Make sure you are not sending a lot of messages (not sure what would be "a lot") perhaps Gmail is blocking too many attempts to send notifications.

Be sure you've setup in accordance to the wiki information:

https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_for_Use_with_gmail

Be sure that your timeout setting is high.

Did the settings just as in the wiki. No good. I send from a gmail box that only had 3 messages sent in the last week, so definitely not overloading that. It still works from the Outlook client sending-receiving, so the account is good.

I went to the Gmail forums and others are reporting issues from other clients, so I don’t think it’s just UDI. I would be checking your setup often as my suspicion is yours will start to fail soon. Google is jacking around with stuff and not admitting to it.

I've got the same thing as well. My (default) does not work either, Any resolution yet?

2 hours ago, aLf said:

My (default) does not work either

What device are you using and what is your IoX firmware version?

2 hours ago, aLf said:

Any resolution yet?

As this is not widely reported as an issue doubtful there's a "resolution". My notifications continue to work as normal. Tests and random program runs trigger email notifications just fine.

Geddy: Thanks, but all that said, I and others are still having issues with Gmail despite the fact that others are not. I have used Gmail for years to send from ISY. Now all of a sudden I (and others) are having issues. What would be causing this and when I ask for a resolution, I'm asking for help from you and others in troubleshooting it. I'm pretty sure that it's related to tls.

ISY 994i, 4.7.3

Any help from you and other members is much appreciated.

For what it's worth, I also have AXIS cameras using Gmail to send mail/notifications using SMTP and TLS from the same Gmail account utilizing the second step authorization code and they are still working fine!

Edited yesterday at 04:08 PM1 day by aLf

I can't offer much help (I no longer have a functioning 994), but I did have a multiday blackout with Gmail last week. It seems fine now.

-Tom

I migrated over to EISY r2 yesterday (not fun - that's another story).

My Gmail doesn't work on an EISY either. However, I haven't researched yet whether the settings should be different for an EISY compared to an ISY.

Clicking the default checkbox does work (neither Gmail nor Default worked on my ISY994). But, I'd rather use the Gmail account.

Ross

7 hours ago, aLf said:

ISY 994i, 4.7.3

UD had to change how the "default" operated. I think that broke it for older ISY firmware versions. I know somebody reported recently that 4.9 had a working default server. I can't confirm it will work for everybody though. My ISY994 was 5.3.4 before I moved to Polisy then eisy. Perhaps your version is one that's broken when you try the "default" option.

7 hours ago, aLf said:

I'm pretty sure that it's related to tls.

What is your timeout set to? (when using the gmail server settings) Be sure it's over 5,000. Try 10,000 and see if you still have an issue. Have you actively used the google account you're trying to send from in the last 24 months? Other than just auto sending emails from it. Google does require that you log in (I think once a year) to keep the account active. It's possible some accounts are "throw away" accounts and you're not actually logging into them and Google might flag them as inactive and suddenly blocking the ability to send.

4 hours ago, Ross said:

My Gmail doesn't work on an EISY either. However, I haven't researched yet whether the settings should be different for an EISY compared to an ISY.

If the settings worked on the ISY994 or Polisy (whatever you migrated from) they should work on eisy. The wki settings still work (as of last attempt) if you need a refresher.

Same here with TLS error. Thought it was me until I saw this post. Started about 2026 Feb 24 or so. I was having many problems with my ISY 994izw with v.4.9.0 rebooting every 5 minutes or so. Replaced the micro sdcard and restored (original transcend card 10 years old). Somewhat fixed it. Noticed all would work as long as I didn't open the admin console's programs tab. Then, magically for the past few days it's all back to normal except for the tls error. Not getting any notifications. Really sux.

Using smtp.gmail.com doesn't work at all! If I "Use Default", sometimes it works and sometimes it doesn't.

So frustrated with the ISY and notifications that I purchased the Eisy r2 and I'm waiting to do the full install. Hope this tls error doesn't get migrated to my new setup.

PhanTomiZ

11 minutes ago, PhanTomiZ said:

Same here with TLS error.

I didn't read thru the comments but did you follow Google's procedure to create a new app password?

Google changed the rules for logging in with TLS.

What You Need To Do

If an application stops working, you have two options:

1. Switch to Modern Auth: Update your app or switch to an app that supports "Sign in with Google" (OAuth 2.0).

2. Use App Passwords: If the app is older and doesn't support modern sign-in, you must:

   • Enable 2-Step Verification on your Google account.

   • Go to your Google Account settings > Security > App Passwords.

   • Generate a new 16-digit password for that specific app and use it instead of your regular password.

Edited 19 hours ago19 hr by mmb

2 hours ago, mmb said:

Google changed the rules for logging in with TLS.

1. Switch to Modern Auth: Update your app or switch to an app that supports "Sign in with Google" (OAuth 2.0).

2 hours ago, mmb said:

I didn't read thru the comments but did you follow Google's procedure to create a new app password?

Google changed the rules for logging in with TLS.

What You Need To Do

If an application stops working, you have two options:

1. Switch to Modern Auth: Update your app or switch to an app that supports "Sign in with Google" (OAuth 2.0).

2. Use App Passwords: If the app is older and doesn't support modern sign-in, you must:

   • Enable 2-Step Verification on your Google account.

   • Go to your Google Account settings > Security > App Passwords.

   • Generate a new 16-digit password for that specific app and use it instead of your regular password.

Not sure how Google changed the rules for logging in with TLS??? What is 1.Switch to Modern Auth: Update your app or .....

What I do know is my Blue Iris, which has the same email servers setting as my ISY, keeps chugging along. I get notifications with snapshots and all.

Out of the blue, my ISY stopped sending notifications and when I test the same settings as Blue Iris, I get the TLS negotiation failed.

10 minutes ago, PhanTomiZ said:

when I test the same settings as Blue Iris, I get the TLS negotiation failed.

My up to date BI version supports only oauth (over tls) for gmail smtp.

Basically Google is phasing out a simple password over TLS and now requires the app to be updated to use stronger authentication (eg oauth over tls (not IOX)) or a procedure to setup a new app password on your google account for apps not updated to a newer authentication methods.

Not sure why the ISY Default doesn't work.

Edited 18 hours ago18 hr by mmb

Hello all, some comments:

1. Make sure neither subject nor body are blank

2. If you have 994, especially such old versions as 4.7.3, you are pretty much on your own because it does not support the new security suites required by google

3. I know this is regarding gmail, but just in case you are using "Default", please note that over the years, we had to add many security/throttling/blacklisting mechanism to prevent hackers (and some customers) ruining our online mail reputation by sending mass emails. So, you might have been black listed. It's always best to use gmail

4. If on polisy/eisy, and using gmail, please submit a ticket (https://www.universal-devices.com/my-tickets )

With kind regards,

Michel

@Geddy Thank you for your responses, Geddy. My Gmail stopped sending notices around Feb 24 - about the same time as others seem to have stopped. I was on the ISY994 then (I migrated this past weekend). My default on the ISY994 also didn't work.

On the EISY, the settings don't work, but the Default does.

Based on your advice, I went and logged into the account - you are right - something I don't hardly ever do. I also noticed I had 10,000 Sent emails in there dating back years. I deleted and trashed them. I sent an email from the account and it worked. However, still no joy sending emails from EISY.

Here are my settings. Based on @Michel Kohanim previous post, I'll open a ticket.

Thanks,

Ross

47 minutes ago, Ross said:

Based on your advice, I went and logged into the account - you are right - something I don't hardly ever do.

@Ross another thing I might suggest is if you don't log in there often then you should probably reset/change the app password and make it new.

What I don't understand is how can several be having this issue, but at the same time others (myself included) haven't had issues. I have even setup a daily email now just to be sure it triggers daily. Since Feb 27th it hasn't missed a beat.

One thing to check is at the sending side do (did) you see recent messages in the sent? I wonder if they are being sent, but where you are sending them is blocking them (for some reason). I send from @gmail.com to @outlook.com. I know this doesn't mean anything if there's an error on send, but wondering if some messages are indeed being sent.

Perhaps @Michel Kohanim is right that something in Gmail has changed again and old ISY994 firmware isn't able to meet the change. Not sure if UD changed how it's handled in the settings for Polisy/eisy since it seems to work just fine there with the same settings I've had since the ISY994 days. I'm guessing there is some underlying safety/security "handshake" stuff going on.

Perhaps this is another indication that the Notification Plugin might be the best option for alerts/notifications going forward. Certainly for eisy users.

@Geddy I will consider changing the app password; however, I might wait until I exhaust other possibilities (including opening a ticket) as I've forgotten the process and will need to do some research.

To answer your other question: I send to both a text email (Verizon - I know, archaic) and a once/day email to another Gmail account. My last Sent email was Feb 24.

I'm good with UD Mobile notifications, but my wife just wants a text. I prefer the texts myself.

Thanks,

Ross

18 hours ago, mmb said:

I didn't read thru the comments but did you follow Google's procedure to create a new app password?

Google changed the rules for logging in with TLS.

What You Need To Do

If an application stops working, you have two options:

1. Switch to Modern Auth: Update your app or switch to an app that supports "Sign in with Google" (OAuth 2.0).

2. Use App Passwords: If the app is older and doesn't support modern sign-in, you must:

   • Enable 2-Step Verification on your Google account.

   • Go to your Google Account settings > Security > App Passwords.

   • Generate a new 16-digit password for that specific app and use it instead of your regular password.

This is what solved all gmail issues for me, combined with a 10000 timeout period.

2 hours ago, Geddy said:

What I don't understand is how can several be having this issue, but at the same time others (myself included) haven't had issues. I have even setup a daily email now just to be sure it triggers daily. Since Feb 27th it hasn't missed a beat.

That is a good question @Geddy . Something must trigger it.

Google began phasing out Basic Authentication which is a simple password over TLS in 2022 with a final cutoff date of March 2025. I changed my ISY to their approved password for less secure Apps in 2022. Since then it hasn't missed a beat.

My Blue Iris now requires Oauth authentication, that happened with an app version update last year I think.

2 minutes ago, dbwarner5 said:

This is what solved all gmail issues for me, combined with a 10000 timeout period.

I think I had to do both an increase in timeout to 3000 and the Google less secure App password procedure.

17 hours ago, mmb said:

Are you using oauth in BI?

If so then that could be why. I use oauth and it works fine.

Not using oauth in BI. My Cyberpower UPS also works fine and I receive notifications from it.

Sorry for the stupid question, but where does Oauth get configured? Gmail?

I've been using the app passwords for many years now. I'm sure those settings work and I'm very familiar with getting that setup.

I've done everything in the wiki for setting up gmail years ago. I've even gone in and created new app passwords.

Configuring gmail Account

(NOTE: As of May 2022 Google has removed the ability for logging in with simply a Username/Pass (used to be considered "Less Secure Apps" process of logging in). Google accounts are now required to have Advanced Security enabled (Two-Factor Authorization type of access). Please refer to Google Account Help for specific directions on how to generate an App Specific password that will then be used in configuring ISY Email Setup.

1. Login to your gmail account

2. Go to Settings | Forwarding and POP/IMAP. Under POP Download, make sure POP is enabled.

3. Go to Settings | Filters and Blocked Addresses and make you are not blocking yourself

Configuring (unique) App Password

(Required as of May 2022)

See App Passwordfor more info.

Steps (as of April 2024)

1. Go to Accountfrom the Google list of apps

2. Click on Security & sign-in in the list on the left

3. Click on 2-Step Verification found under "How you sign in to Google" (You might need to enter your password to proceed)

4. App Passwords is at the bottom of the page. (See below if you do not have the section for App Passwords)

5. Click on >

6. Type the name for the "App" (i.e. "ISY Notification")

7. Click on Create

8. Copy (or make note of) the generated password to be used later

9. Click DONE to store the newly created app specific password to your account

This created a unique 16 character password, save it (copy to clipboard) and use it when setting up Gmail below instead of the primary account password.

If you do not see App Passwords this means you have never setup an app password. Use the "Search Google Account" box at the top of the page (when you are on the "Security & sign-in" page). Or you can try using this direct link - https://myaccount.google.com/apppasswords (you might need to sign into Google or re-enter your password before continuing)

• NOTE: 2-Step Verification MUST be active on your account before you can setup "App Passwords"

Configuring for Use with gmail

1. Make sure you have configured your gmail Account (see above)

2. Go to Admin Console | Configuration tab | Emails/Notifications

3. Under SMTP Settings ensure Use Default is Not checked

4. For SMTP Server enter smtp.gmail.com

5. For SMTP Port enter 587

6. For User ID enter the username associated with your gmail account (e.g. abc@gmail.com)

7. For Password enter the password associated with your Account

8. For From you can leave it blank. If your service allows it, you can add a display name ensuring the format follows First-Name Last-Name:Email-Address"

9. Make sure TLS is checked

10. For timeout, 5000 (or more)

11. Click on the Save button

12. Test (Often times the "TEST" email is considered SPAM by many free email servers. So if it does not show up right away please check your SPAM folder. Normal alerts should receive to in-box normally, but you may need to add the address to trusted senders or setup a filter to never filter ISY notifications.)

Attention: The "FROM" field contains an important ":" (colon) between the "First-Name Last-Name" and "Email-Address" portion. That is VERY important to include if you want a display name to appear in the sent message. If you do not include the colon and have something other than just the email address it WILL FAIL.