‎Scheduled Access Codes for Smart Locks and Alarm PINs | SimpliSafe Support Home
 
bobthebuilder's profile

4 Messages

0

Scheduled Access Codes for Smart Locks and Alarm PINs

Subject: Scheduled Access Codes for Smart Locks and Alarm PINs

I am a new SimpliSafe customer and recently installed SimpliSafe Smart Locks. Overall, I like the integration with the security system, but I was surprised to discover that user PINs cannot be restricted to specific days or times.

This creates a common real-world problem.

Like many homeowners, I occasionally need to grant access to a housekeeper. My cleaner comes on a specific day of the week during a specific time window. I do not want to provide a code that works 24 hours a day, 7 days a week. I want to provide a code that only works when the cleaner is expected to be at my home.

Currently, my choices are:

1. Give the cleaner a permanent code that works all the time.
2. Manually create and remove codes every week.
3. Leave my alarm disarmed during a scheduled window.

None of these are ideal.

The feature I would like to see is simple:

Create a user and assign:
- A lock code
- An alarm PIN
- A schedule

Example:
Housekeeper
Every Thursday
8:00 AM – 4:00 PM

Outside of that schedule, both the lock code and alarm PIN would be inactive.

This would improve both security and convenience. It would also eliminate many situations where homeowners accidentally re-arm the system before a service provider arrives.

Many competing smart lock systems already offer scheduled access codes. Since SimpliSafe already supports multiple users, PINs, schedules, and smart locks, this seems like a natural enhancement to the platform.

I believe this would be valuable for housekeepers, dog walkers, babysitters, contractors, property managers, and anyone who needs recurring but limited access to their home.

Thank you for considering this request.

No Responses!

New to the Community? Get started by reading our Welcome Article and please be sure to review our Community Guidelines before posting.

Related Conversations

  • 0

    0