(www.rboyapps.com - Making SmartThings Easy!)
Yes the app takes care of all codes within the specified user limit.
Duplicates are caused by codes that have been programmed outside the scope of the app. It could left over from before or programmed directly into the lock etc but because the user has limited the app to only program the first X codes, it only validates those codes. That’s why we suggest starting with a clean slate by resetting the lock when installing the app.
Till now the app used to ignore duplicate codes, now we’ve decided to notify the user so you’re aware that there are codes outside the scope of the app which may conflict with your programming. Duplicate codes are the reason why some folks reported the setCode being sent multiple times, so we now we’re making the user aware of the reason.
We’ll refine the duplicate code messaging and processing in the next update
As for the nameslot message, just deselect that lock from your user, click save and then come back select it and click save, it’s just cosmetic, we’ll patch it in a future update
Thanks for all the updates RBoy… they may be on your radar, but I wanted to suggest a few additional features:
VRBO (mentioned earlier, but would add a lot of value if we could integrate lock codes with the VRBO vacation rental API)
Per User Notifications (based on a label in the app, it appears that this may be in the works)
Door Position update to the Lock Device based on the Contact Device so that we can reference the Lock Device and get complete door status:
right now, we have a separate contact sensor and lock; some locks have the DPS built in, but many do not…
for those that do not, it would be great if this Lock Code app would set the DPS attribute on the associated lock device (since its already associated and subscribed to the separate contact sensors)…
basically, this would allow us to name the door lock something like ‘Front Door’ and we can associate all of our apps & rules with only that 1 device and when notifications (TXT, App or voice) reference the device, it will be simply called ‘Front Door’ (vs “Front Door Lock is Open” or “Front Door Contact is Open”)…
hopefully that use case makes sense, but basically, we all struggle with the fact that a door is 2 different devices… would be nice if the Lock could represent both as just a door (and this App could provide the necessary communication between devices.)
If you have a lock with an integrated Door Position Sensor (like Yale or August) then use our Enhanced Z-Wave Lock device handler and it will show up as a Lock and Door Contact Sensor in SmartThings (since device with 2 capabilities which can then be used any SmartApps)
Per user notifications are already there and you can enable/disable them along with restrictions on when to notify based on modes or user presence.
In the next version 07.04.00 we’ve added 2 more custom options for user notifications:
Limit the number of notifications for that user (first X notifications)
Ability to specify custom notifications options for the eac user (who to notify and how to notify)
Hello RBoy. I’ve been using your smartapps and so far they’re working really good until recently, wife always complaining that evertime I come home from work (11pm) I would wake her up because the speaker notification is too loud, which is just fine during daytime.
Can I suggest to include it in your future updates for us to set the volume on a specific time or a way to turn off the tts notification on a specific time. thank you so much.
Been a while using this app and just did all the updates and it’s been working flawless. One problem were having is when my son leaves the house he’s forgetting to close the back slider, is there a way to prevent the front door from locking if the other door sensors are open? This way if he can’t lock the front door it will remind him to go close the other doors.