07-24-2022 05:39 PM
Hi. We have 5 Nest x Yale locks all on one account, on one hub. How do we separate the codes for only their specific unit but not for all the units? Meaning everyone shouldn't have their codes working for all 5 locks.
Answered! Go to the Recommended Answer.
07-28-2022 10:59 AM
Hi there,
I apologize for my late response and thank you for all of your patience while waiting for a reply. I understand how frustrating your situation must be, and I would love to help however I can. You can create Guest Codes for your tenants within your Home/structure in the app. Here is an article that goes over the process.
Best Regards,
Brad
07-28-2022 01:15 PM
It may be better to have each lock on a different Home/Structure for each one then you can separate your locks and their guest codes more easily. But this would require you to create and manage multiple accounts.
Best regards,
Brad
07-28-2022 01:43 PM - edited 07-28-2022 03:01 PM
@cambridgemanor
I don't know of any tutorials for this process, but you can create a gmail so you can add each lock to that new Home with each email/account you create. You can check out this article which will go over some of that information. Should still be very helpful. Sorry that these steps require a lot, but these locks are not really meant to be used in multiple homes, or really for more than a few users. But this is a workaround that I have seen work for others.
Best regards,
Brad
08-02-2022 08:49 AM
The workaround worked. Thanks for your help 👍
07-25-2022 04:03 AM
Hi
07-25-2022 05:54 AM
Hi. Are you trying to respond to my question?
07-25-2022 12:50 PM
Would creating a new Home on Nest solve this issue?
07-28-2022 10:59 AM
Hi there,
I apologize for my late response and thank you for all of your patience while waiting for a reply. I understand how frustrating your situation must be, and I would love to help however I can. You can create Guest Codes for your tenants within your Home/structure in the app. Here is an article that goes over the process.
Best Regards,
Brad
07-28-2022 11:49 AM
Even when creating separate passwords for guests/tenants with Home Entry Only they are still able to access each other's locks. Is it because they are all on one hub or on one Nest Account?
07-28-2022 01:15 PM
It may be better to have each lock on a different Home/Structure for each one then you can separate your locks and their guest codes more easily. But this would require you to create and manage multiple accounts.
Best regards,
Brad
07-28-2022 01:18 PM - edited 07-28-2022 01:18 PM
Is there a tutorial video that you can refer me to do that?
07-28-2022 01:43 PM - edited 07-28-2022 03:01 PM
@cambridgemanor
I don't know of any tutorials for this process, but you can create a gmail so you can add each lock to that new Home with each email/account you create. You can check out this article which will go over some of that information. Should still be very helpful. Sorry that these steps require a lot, but these locks are not really meant to be used in multiple homes, or really for more than a few users. But this is a workaround that I have seen work for others.
Best regards,
Brad
07-28-2022 01:56 PM - edited 07-28-2022 02:12 PM
Ok if that's the workaround for this then it will have to do. Can it be done all on one Hub? Is there a tech support number I can talk with your department in regards to this issue?
07-28-2022 02:20 PM
Yeah the workaround works, but it can be time consuming. You are welcome to contact Support if you would prefer them to work with you through this process. You go through the questionnaire, and then pick your category, Next > Next and choose if you want to call or chat.
Best regards,
Brad
08-02-2022 08:37 AM
Hi there,
Just checking in to see how the conversation is going as there's been a lapse in activity on this thread.
Best regard,
Brad
08-02-2022 08:49 AM
The workaround worked. Thanks for your help 👍
08-02-2022 08:53 AM
I am glad to hear that the workaround worked for you! That must be a relief! As this is resolved, we'll keep an eye on this thread if you need more help, but we'll mark this issue as resolved.
Best regards,
Brad