mmb

Curious @Michel Kohanim what is causing the ISY Default smtp failures on the ISY? Even when firmware is updated. It seems so straight forward.

My experience as well, EISY and Polisy work fine with Gmail but the ISY doesn't work at all. The ISY Default smtp setting does work fine for me, first try actually.

Very smooth for me, surprisingly given everything that was touched.

My ISY has been on Gmail since 2012/2013, likewise never a problem,. Back in the days of LeeG etc.

Nothing changes for your Gmail account. The change affects use of their smtp servers that you use to move email. It's well known that certain people abuse smtp to send spam and other garbage. Stronger authentication tries to ensure that the right people are using their smtp servers. ISY supports Basic authentication for their smtp servers, Google no longer supports Basic authentication for reason describe above. They say you have to use their procedure to generate an approved strong password (16 character) if you want to continue to use Basic authentication.. BI now supports Oauth which allows you to use your usual Google username and password for authentication to their smtp servers.

Under Settings / Email Servers / Authenticate

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. I think I had to do both an increase in timeout to 3000 and the Google less secure App password procedure.

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.

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: Switch to Modern Auth: Update your app or switch to an app that supports "Sign in with Google" (OAuth 2.0). 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.

Thanks Getty, I can't find the email and nothing on the site that I can find - this prompted the post as I was looking for the webinar date in February. I've suggested to Michel previously that UD undersells itself for such a great automation product.

Less technical like my brother 🤦‍♂️ He would love it!

It would be nice it UD published the webinar dates in their Announcements on the Forum.. And if there is a YouTube link so those who miss their webinars can follow up after.

You assume correct, in BI select Settings / Alerts /On Alerts / + (lower left) then create new alert. Then create the EISY Program. Something like this: Motion Cam Lts If $Motion_Cam_Detect is 1 And From 9:05:00PM To 5:00:00AM (next day) Then Set 'Outside Front and Side Lts' On $Motion_Cnt += 1 Wait 10 minutes Set 'Outside Front and Side Lts' Off $Motion_Cam_Detect = 0 Else $Motion_Cam_Detect = 0

Regarding Triggers, I took a different approach. I use BI Alerts to set a variable thru Rest on the EISY which triggers an Outdoor Lights Program. The program turns on the outdoor lights then Waits 5 minute then turns them off. Improved lighting helps BI recordings as I don't use IR, just ambient light. For example: user:password@192.168.0.106:8080/rest/vars/set/2/38/1 I been using this combo for about 15 yrs and it works flawlessly, especially since BI's recent incorporation of AI. Of course, this was all done well before PG3 and the BI node plugin, so this is new to me. BTW if you use the UNIFI Protect ecosystem, the Unifi Protect doorbell and cams can trigger the eisy/insteon lighting nicely using their webhooks.

Same experience roughly the same time. A hard reboot got it going again and I believe I did a fw update after. I put it off as a fw glitch.