Notifications from alarm.com for remote arm/disarm/bypass actions (possibly others where user is known) do not include the user performing the action but the user is included with that action is in the activity log. This contrasts notifications when these type of actions are performed locally at the panel which do include the user, so there is lack of consistency in this behavior.
Is there any logic behind the notification itself not including this info as it’s very useful information to see at a glance with notifications. Needing to open the app and go into the activity log to see this makes it unnecessarily burdensome on the user, especially when the activity log can be littered with a ton of motion sensor notifications to weed through to find this relevant info.
I would like to see all remote notifications include the user performing the action (when known) in the same way local action include this info. Furthermore, to clearly tell you in a notification if this was a local or remote action, they should include that in the notification as well by simply adding the word “remotely” into those notifications:
Location notification: “Panel was <action> by <user> at <time> on <date>”
Remote notification: “Panel was remotely <action> by <user> at <time> on <date>”
When you create a secondary login, the only info linked to that is the Username and an email address, and I believe it is likely data security concerns that keep them from being added as an identifier in notifications. I think that’s probably the main reason you don’t see that option at the moment.
It’s a good call out , and they could assign a new nickname option to logins to identify the app user, but then on the same token many individuals end up giving family members access using a single login, so identification may end up being confusing for some users.
I don’t like how actions done via the app or web are logged using the web login name vs. your panel username, so having an option for a nickname is a good addition to this request and a general good addition. That would address the “shared login” as you could give it a generic name vs. the specific account name.
I was able to create logins using First_Last for my users so that I don’t have to think about random aliases names or email address in activity logs, but at the same time those users can change that at any time. As an admin, I want to see consistent information across the platform and being able to set a nickname as the real name (which is what I have in the panel itself) would be a great benefit even beyond the notification aspect.
I never heard of any traction on this, but I have followed up with Alarm.com and I just sent another request for a nickname/label option for login names. When I get any info back I will follow up here. I think it would be a very useful addition.