RobertA

I see other threads on this. for instance, It's been a while, but I think this is how I did it. Using composer, you can determine the IP address of the Door Station. Click on the door station and view its IP Address using the monitoring/properties tab. Its likely a DHCP auto assigned IP address. You might want to change it to a static IP address, but that isn't necessary. To do that, you would have to log into the doorstation's IP address with a browser, such as firefox (I don't believe chrome or IE lets you due to the outdated security certificate) and change its networking configuration to a static IP. Then log into your HIK NVR, using a browser and its IP address. Under system settings/configuration/camera management, you can click on an unused camera, and modify. Change the camera's setting from Plug-n-Play to Manual, type in the door station's ip address, and select custom 1 as the protocol. if another doorstation is to be added, use custom 2 for the second, etc. type in the doorstation's login user name (root) and password (t0talc0ntr0l4!). management port should be 554 and channel 1. I think that is basically what I did.

Thank you Cyknight for your help! Can the door station support SMTP SSL port 465? or would a software update or a newer driver support SSL? My door station HW version is 220v3 and the software version is 2.25.0.34.7. I don't know how to determine what my driver version is. I have only composer home, not pro. I tried several email services, including ATT ISP's email, and they seem to support only SSL port 465. My driver documentation provides only info to setup using port 587.

Once again, my door station has stopped sending a snapshot email. I am still configured to send via smtp.gmail.com and I generated a new app password (https://myaccount.google.com/apppasswords) and replaced the door station's SMTP Server Password field with the new app password, in case the password from last year had expired. Is the capability to send a snapshot email from the door station still supported? I have experimented with updating all fields but so far I have no success. From the door station's browser page and the Email Sending Diagnostics window, all I get as a clue is this output: Email created. Snapshot attached. Sending started. Test email FAILURE.

My interpretation of Google's statement "If an app or site doesn’t meet our security standards, Google might block anyone who’s trying to sign in to your account from it" implies that as of June 1, an app's access needs to be manageable from Google's security page/tab that manages third party access, where one may determine and manage an app's access to your Google Account data. So, I am under the impression that by using the account username and password (which gives "all in" access), even when using a generated unique app password, isn't going to meet these security standards, since we can not determine or revoke this app's access from Google's "app with access" management page.

Nice sleuthing and discovery, RAV! I followed your link and followed those instructions, generated a unique "control4" app password, and in the door station property's password field, replaced my account password with the generated app password. Tested, and success! so far, so good! Hopefully, come June 1, this will remain supported by gmail, and not be under the umbrella of what they plan to discontinue as third-party apps that sign in to a goggle account using only username and password.

The door stations use gmail's less secure account authorizations when sending outgoing emails. But gmail is discontinuing this on May 30, 2022. Is there a workaround planned to allow door stations to continue sending emails as of June 1? Gmail's Less secure apps & your Google Account notification in help states: To help keep your account secure, starting May 30, 2022, Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password. Please note this deadline does not apply to Google Workspace or Google Cloud Identity customers. The enforcement date for these customers will be announced on the Workspace blog at a later date.