schlage BE469 deadbolt "Failed to add restriction"

Schlage BE469 deadbolt installed with VeraLite. Installation and everything else seems to work great. I cannot add any restrictions to the pin codes. I tried daily and weekly, and it saids “Failed to add daily restriction.” Anyone else have this problem or anyone have any suggestions/solutions?

I’m having the same issue. It looks like it let me add a restriction to only 1 pin code and the rest are now failing.

Thinking of getting the Schlage Deadbolt, however PIN management is going to be key for my buying decision. Has anyone else had issues adding restrictions to the PINs they’ve setup (as I need this functionality for granting access to my cleaning lady. Anyone w/ this deadbolt get it to work properly?

Hopefully this will help you

Changing an existing PIN
Navigate to Vera’s ‘Control’ (or ‘Dashboard’ or ‘Devices’) page
Remove an existing user’s slot (see below)
Add the user again with a different PIN (see above)
Click ‘Set’.
The user’s PIN will remain active until you remove it.
Removing a PIN
Navigate to Vera’s ‘Control’ (or ‘Dashboard’ or ‘Devices’) page
From the list, find the user whose PIN you wish to de-activate
Click the ‘Remove’ button next to that user
Click ‘Set’.
The user’s PIN will be removed from Vera’s list.
NOTE: If Vera does not confirm the removal after 60 seconds, simply try again.
SPECIAL NOTE: If you add, change or remove many users/PINs in rapid succession, Vera will display a ‘job icon’ for each addition/change/deletion. You do not need to wait for each one to complete. For example, you can add 10 users in rapid succession, and you will see 10 gray ‘job icons’. Gray indicates Vera hasn’t started yet, as explained here. Since it takes several seconds for Vera to program a new PIN into the lock, as each job is being processed (in order), the corresponding icon turns blue, then becomes green when it is successful. In this way, you can quickly queue up several new users, and then just let Vera process them one at a time. When Vera is finished, you will see the list of all users, along with a ‘Remove’ button next to each. Similarly, you can click several ‘Remove’ buttons in rapid succession without waiting for each removal to complete.
Reversing the Lock/Unlock Status

If the lock/unlock status of your door lock is backwards, meaning Vera’s ‘Dashboard’ shows it is locked when it’s really unlocked and vice-versa, it’s possible the lock was oriented upside-down when mounted. To solve this issue, go to Vera’s ‘Setup’ page, click the ‘Devices’ tab and click the ‘+’ button next to the door lock, and then the ‘Advanced’ button. If you see a parameter “#305 Reverse”, enter a value of 1. Save this change. Vera will now reverse the lock/unlock status.
If parameter #305 is not in the list, then at the bottom of the page, type 305 in the “New Device Data ID” field, and type 1 in the “New Device Data Value” field. Click ‘Add’. Then save your changes. Vera will now reverse the lock/unlock status.

Hey Burkevalocks,
Thanks for the tips. I am from Woodbridge :slight_smile: (but don’t live there anymore). I couldn’t find the param setting anywhere under advanced … and also didn’t see the New Device Data ID field either :/.

I am new at this, but comfortable in this environment, just having a ton of trouble. I finally got the two locks to pair with Vera Edge, but both locks are displaying this warning in red: Please wait! Getting secure classes…forever. I think I need to address that first as that could be the root of all evil. Do you have experience with this warning and how to fix it?

It is much appreciated, because otherwise I want to throw this controller out the window and into my pool.

[quote=“ctonnesen, post:5, topic:187265”]Hey Burkevalocks,
Thanks for the tips. I am from Woodbridge :slight_smile: (but don’t live there anymore). I couldn’t find the param setting anywhere under advanced … and also didn’t see the New Device Data ID field either :/.

I am new at this, but comfortable in this environment, just having a ton of trouble. I finally got the two locks to pair with Vera Edge, but both locks are displaying this warning in red: Please wait! Getting secure classes…forever. I think I need to address that first as that could be the root of all evil. Do you have experience with this warning and how to fix it?

It is much appreciated, because otherwise I want to throw this controller out the window and into my pool.[/quote]

You need to move the controller within a few feet and leave it there until its done pairing. Getting secure classes means it hasn’t finished pairing. Door lock with the security involved means that they need to be in direct contact vera at a closer range to get properly setup. And Altho I have paired mine from some distance when you run into an issue like this you should unplug your vera and plug it in next to the door and use the buttons to include or if you want the UI to include then you need to setup the wifi or run a long cat5 cable.

[quote=“ctonnesen, post:5, topic:187265”]Hey Burkevalocks,
Thanks for the tips. I am from Woodbridge :slight_smile: (but don’t live there anymore). I couldn’t find the param setting anywhere under advanced … and also didn’t see the New Device Data ID field either :/.

I am new at this, but comfortable in this environment, just having a ton of trouble. I finally got the two locks to pair with Vera Edge, but both locks are displaying this warning in red: Please wait! Getting secure classes…forever. I think I need to address that first as that could be the root of all evil. Do you have experience with this warning and how to fix it?

It is much appreciated, because otherwise I want to throw this controller out the window and into my pool.[/quote]

Yes I would do what integlikewhoa said. I would have the same answer. But if you have any other problem please do let me know I will see if there is anything else I can help you with.

[quote=“burkevalocks, post:7, topic:187265”][quote=“ctonnesen, post:5, topic:187265”]Hey Burkevalocks,
Thanks for the tips. I am from Woodbridge :slight_smile: (but don’t live there anymore). I couldn’t find the param setting anywhere under advanced … and also didn’t see the New Device Data ID field either :/.

I am new at this, but comfortable in this environment, just having a ton of trouble. I finally got the two locks to pair with Vera Edge, but both locks are displaying this warning in red: Please wait! Getting secure classes…forever. I think I need to address that first as that could be the root of all evil. Do you have experience with this warning and how to fix it?

It is much appreciated, because otherwise I want to throw this controller out the window and into my pool.[/quote]

Yes I would do what integlikewhoa said. I would have the same answer. But if you have any other problem please do let me know I will see if there is anything else I can help you with.[/quote]

Thanks so much. I put it on wifi and moved to the doors in question. It worked on one of the doors, but when I moved it to the second door (Vera was within 18 inches of the doorlock), I got the same behavior where it couldn’t finished pairing and got the secure classes warning. In the blue box above, I get passed the exchanging secure network keys part, and then it hangs out there … forever. I waited an hour or more, and it just never gets passed it.

The lock works perfectly - just can’t pair it with the Vera.

I think you have your blinders on. If it doesn’t pair that doesn’t mean it VERA’s fault or that the lock works perfectly. You very well could have an issue with either the lock or VERA and or the firmware version on either one.

Hi jfl007

Did you manage to get your lock working?

I can program in multiple pins but get the same “Failed to add restriction” message when I try to add weekly or daily restrictions to those pins.

Appreciate a reply if anyone has fixed this.

I’m using a Vera Edge with the most recent firmware, and I receive the same “Failed to add restriction” or “Failed to add weekly restriction” trying to manage settings for either a Scalage BE469 or a Yale YRD220-ZW. This appears to be a problem with UI7, and not the locks.

Has anyone been able to manage restrictions for either of these locks under UI7? If so, could you share what you had to do? If not, how do we report this issue to MiCasaVerde to get the ball rolling? Would this fall under the 30 day clock, or since functions such as lock, unlock, and rudimentary pin management (adding and removing pins with zero restrictions) work does MiCasaVerde consider these devices to be ‘working’?

This function appears from the MiCasaVerde support site to have worked under UI5. Is this one of those charming instances I keep hearing about where UI7 still hasn’t caught up? (Mostly, I’ve been happy with my Edge so far, but things like this make me wonder why UI7 shipped without feature parity…)

[quote=“edge.trauma, post:11, topic:187265”]I’m using a Vera Edge with the most recent firmware, and I receive the same “Failed to add restriction” or “Failed to add weekly restriction” trying to manage settings for either a Scalage BE469 or a Yale YRD220-ZW. This appears to be a problem with UI7, and not the locks.

Has anyone been able to manage restrictions for either of these locks under UI7? If so, could you share what you had to do? If not, how do we report this issue to MiCasaVerde to get the ball rolling? Would this fall under the 30 day clock, or since functions such as lock, unlock, and rudimentary pin management (adding and removing pins with zero restrictions) work does MiCasaVerde consider these devices to be ‘working’?

This function appears from the MiCasaVerde support site to have worked under UI5. Is this one of those charming instances I keep hearing about where UI7 still hasn’t caught up? (Mostly, I’ve been happy with my Edge so far, but things like this make me wonder why UI7 shipped without feature parity…)[/quote]

Welcome,

you should call vera or email them if you have time to request assistance with your problem.

I’m not sure what 30 day clock your thinking of, but I never heard of anything happening in 30 days.

Ui5 is old outdated and has no extra features then ui7. if you blast back to when ui5 was in style the complaints were the same. Ignore the ui5 posts.