The new App for notifications seems great and a simple implementation of the RM to this specific need. Well done.
Would be possible to add Co2 to the list of Sensors?
Would be possible to add, as an optional argument, to Co2 and Sound a threshold level? For example if sound detected only above X dB?
Also could the lock code functionality be enhanced? I was going to move the lock code usage notification to this app, but then realized that each lock had to be set up separately so I quit.
What I am looking to do is have any lock report when a lock code is used and ideally be able to use a generic message with %device%, %value% and the lock code: "Front Door Lock was unlocked using lock code Denise"
I don't have more than one lock that supports codes. I could setup a virtual lock to test I suppose, but doesn't Any Lock Code with the variable %device% as shown in the app cover any device with a lock code?
Haven't tested, but knowing how apps typically work, my guess is that when I select a lock then the app subscribes to that lock, so it wouldn't know about the other locks. I wrote my own app to notify me about lock code usage so that works for now, but I'd like to move a lot of my notifications to the new notifications app if possible.
I don't think HE customizes it based upon specific apps, if that makes sense? It's the same across all the built-in apps. So, even though you have a multiple select option for "device" (like Contact Sensors, for instance), the %device% variable always performs the same way.
I think what @corerootedxb is trying to say is that the text notification area doesn't check to see if multiple devices were selected, it supports reporting the device name no matter what. So I could set up one lock and not have to hard code the lock name in the message, the %device% would report it.
Yeah, it's a template that is used in all notifications. Basically, the Notifications app and Rule Manager (and other apps that implement Text/Audio notifications) all use the same text.
This is from RM. It's exactly the same as it is in Notifications.
Probably your first assertion is correct that the event can only attach to one lock at a time. It might just be something that HE overlooked or perhaps a way that the event subscription model was coded originally.
I'm not on the HE team, so I don't know for sure, just applying my developer's logic to what it might be doing on the back end.