I have been running UI4 on the original which did not support notifications. I upgraded to the beta UI5 and the notifications would allow you to enter the offset code index, but the notifications still did not work. I upgraded this morning to UI5 version 1.5.255 and tried the notifications which don’t work.
I have experimented with the index/offsets using 0 and 1 with no luck. I never get an email or SMS when a specific lock code is entered. Has anyone been able to get this working?
As a side note I would like to see a drop down list instead of an index for these notifications. A couple of problems would be if you add an delete codes then this index will change and be invalid which would also invalidate my notifications. Since you can’t edit notifications (only creation and deletion is implemented in the interface) you would have to delete and add all notifications if you add and remove lock codes. In my use case I want to be notified when the cleaners have entered, or any rental guests have arrived. Since the rental codes change quite often the indices will be invalid almost every time.
I am seeing the same thing. With 1.5.236, I was getting email notifications but no text notifications. Now with 1.5.255, I am not getting any notifications. The only place it shows up is in My Alerts. This is concerning because I will not receive any notifications if the alarm goes off while I am away from home.
Not sure why email notifications are not working. I do know that MCV changed the backend that sends out text notifications. They told us that they were working out the kinks still. I do not use the notifications as I use my own notification relay (email relay server running on a pogo plug which relays to my gmail account).
I checked it again and the email is working now. I think there is a secondary issue with notifications/triggers though. Without a reboot or reload stale notifications can get stranded and are unseen. If you continue to use the same name for a notification it will never work. You must do something like test_notification_1, test_notification_2, etc. I verified this after the fix. In the absence of a reboot or reload they don’t appear to work correctly when adding, deleting, and reusing the same names using the information below.
Here is what I have uncovered so far with the notifications.
Automation–>triggers
Delete a notification and the save button does not appear. The notification will get removed from the list in the triggers UI.
Go to Devices–>Locks–>Wrench–>Notifications
Notice now all of them are gone. Close the dialog box then select the reload button. All Notifications are back now. Go back to Automation–>triggers and notice that the one you deleted is also back.
Here is some additional information on the confusion with notifications and the ‘PIN code INDEX number’. Notice how there is only one place where this nomenclature is found. If you are in the triggers or notifications page you have no direct knowledge about the index. Additionally the index is always 0 when you start creating a new one. This leads you to believe that the system uses offset 0 based indices so PIN code #1 listed on the page should be 0. Which can invalidate your notifications. Since there is no editing capability, you would be forced to delete them all and recreate them. I would personally use a UUID for the index on the back-end under the hood and present the user with a drop down box of names. This would reason well since there would be no use for a manually entered index value that has no corresponding entry and would never execute.
The other issue is that using an index is not a preferred method since they can change and get shuffled - especially with door lock PIN codes. By using the drop down named values list this would prevent invalid entries and provide built in validation. Otherwise some sort of string validation looping through the existing codes and doing a string compare would be appreciated.
In earlier versions of the UI when creating scenes the lock pin used to be selected from a drop down list, i agree this was far better we should not be making changes which predispose errors and confusion
[quote=“u20111223, post:10, topic:169897”]I would personally use a UUID for the index on the back-end under the hood and present the user with a drop down box of names. This would reason well since there would be no use for a manually entered index value that has no corresponding entry and would never execute.
The other issue is that using an index is not a preferred method since they can change and get shuffled - especially with door lock PIN codes.[/quote]
I agree with everything above… I too have a new code for each renter, and am reluctant to make any scene that is triggered by a PIN being entered since I have no way of ensuring that new codes I create will (or won’t!) have IDs corresponding to the trigger already in existence.
By using the drop down named values list this would prevent invalid entries and provide built in validation. Otherwise some sort of string validation looping through the existing codes and doing a string compare would be appreciated.
This would be best… Ideally I could do something like this:
Set a scene trigger named “when a named PIN is entered with name containing” with a value “Renter”.)
Then I know that the trigger will fire for all my existing Renter codes previously set up: RenterBob, RenterSue, etc. Any future codes I enter such as RenterJoe, etc. would also trigger the scene. No action would be needed on my part other than creating the code with Renter in the name.
Great, thank you. Please ensure that “all PINs” is one of the drop-down options, to account for the poorly-documented “*” index accepted now.
What about a PIN string match trigger? I’ll be happy to enter this myself… Should I create a separate Mantis account, since my MCV forums credentials don’t appear to work?