# Unauthorized access!

**URL:** <https://community.ultraloq.com/t/unauthorized-access/4252>\
**Category:** ULTRALOQ Smart Lock\
**Created:** [August 24, 2022, 6:55pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252 "2022-08-24T18:55:18Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![RoyN](https://avatars.discourse-cdn.com/v4/letter/r/f05b48/32.png) [@RoyN](https://community.ultraloq.com/u/RoyN)\
**Post date:** [August 24, 2022, 6:55pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/1 "2022-08-24T18:55:18Z")

</div>

This lock is a complete disaster!

I have a user who has scheduled access which expired on 8/20. This person came to my house yesterday (8/23) and was able to unlock and enter my home twice. I just tested their code today (8/24) and was able to unlock the deadbolt.

Someone explain to me how this device can be considered a safe lock to protect person and property when it grants people unauthorized access? This is the polar opposite of why anyone puts a lock on their door - to keep people out not let them in.

I’m livid!

---

<div class="post-metadata">

**Author:** ![RoyN](https://avatars.discourse-cdn.com/v4/letter/r/f05b48/32.png) [@RoyN](https://community.ultraloq.com/u/RoyN)\
**Post date:** [August 24, 2022, 7:05pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/2 "2022-08-24T19:05:17Z")

</div>

Just for kicks, I just changed the access dates so that they expire on 8/19. I thought this might reset the permissions for this access code. Nope! I was still able to unlock the door with this code!

The English language doesn’t have words that can express the anger and frustration I have right now.

---

<div class="post-metadata">

**Author:** ![Gilbert](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/gilbert/32/1913_2.png) [@Gilbert](https://community.ultraloq.com/u/Gilbert)\
**Post date:** [August 25, 2022, 9:22am UTC](https://community.ultraloq.com/t/unauthorized-access/4252/3 "2022-08-25T09:22:33Z")

</div>

@RoyN Our agent has replied you via Trouble-Ticket, please check the email.

---

<div class="post-metadata">

**Author:** ![Berube2](https://avatars.discourse-cdn.com/v4/letter/b/d2c977/32.png) [@Berube2](https://community.ultraloq.com/u/Berube2)\
**Post date:** [August 26, 2022, 6:06pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/4 "2022-08-26T18:06:09Z")

</div>

When entering the end date for a code, by default it out in the next year by default… Did you make sure the year was 2022 ? That is one thing that I don’t like… But otherwise don’t have any problems

---

<div class="post-metadata">

**Author:** ![Evans1](https://avatars.discourse-cdn.com/v4/letter/e/a9a28c/32.png) [@Evans1](https://community.ultraloq.com/u/Evans1)\
**Post date:** [August 28, 2022, 1:59pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/5 "2022-08-28T13:59:14Z")

</div>

I had the opposite issue my parents came and their access didn’t work at all. I ended up deleting there code and adding it back in then it started to work again.

---

<div class="post-metadata">

**Author:** ![Gilbert](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/gilbert/32/1913_2.png) [@Gilbert](https://community.ultraloq.com/u/Gilbert)\
**Post date:** [August 29, 2022, 9:06am UTC](https://community.ultraloq.com/t/unauthorized-access/4252/6 "2022-08-29T09:06:12Z")

</div>

@Berube2 We will consider adding more options in the future, but now the default is the next year.

---

<div class="post-metadata">

**Author:** ![Gilbert](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/gilbert/32/1913_2.png) [@Gilbert](https://community.ultraloq.com/u/Gilbert)\
**Post date:** [August 29, 2022, 9:08am UTC](https://community.ultraloq.com/t/unauthorized-access/4252/7 "2022-08-29T09:08:50Z")

</div>

@Evans1 Please double-check the schedule, especially the Weekdays and the time. For the Weekdays, the Blue color means it’s available, Gray means unavailable. Also, some users set up the visit time from 00:00 to 00:00, which will also cause visitors cannot open the door.

---

<div class="post-metadata">

**Author:** ![Evans1](https://avatars.discourse-cdn.com/v4/letter/e/a9a28c/32.png) [@Evans1](https://community.ultraloq.com/u/Evans1)\
**Post date:** [August 29, 2022, 12:17pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/8 "2022-08-29T12:17:50Z")

</div>

@Gilbert, they are setup as standard users to the schedule would not apply.

---

<div class="post-metadata">

**Author:** ![RoyN](https://avatars.discourse-cdn.com/v4/letter/r/f05b48/32.png) [@RoyN](https://community.ultraloq.com/u/RoyN)\
**Post date:** [August 29, 2022, 4:17pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/9 "2022-08-29T16:17:14Z")

</div>

Yep. That was the problem and that is pure insanity. Nobody schedules a “temporary” user for over a year at a time. Hey, let me give you temporary access from July 4, 2022 to July 6, 2023.

This is definitely not a feature, this is a bug that they know about and won’t fix.

Funny thing is that I contacted their tech support and they told me either my batteries are weak (not so) or if my batteries aren’t weak them someone has reset my lock (not remotely possible) so I need to factory reset it. I mean, talk about lazy tech support… Lazy tech support always goes to the nuclear option for factory reset.

Glad I didn’t listen to that and discovered that I had inadvertently given someone access to my house for 366 days instead of one day. Thanks for pointing that out!

---

<div class="post-metadata">

**Author:** ![Murphy1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/murphy1/32/1100_2.png) [@Murphy1](https://community.ultraloq.com/u/Murphy1)\
**Post date:** [January 22, 2023, 3:24am UTC](https://community.ultraloq.com/t/unauthorized-access/4252/10 "2023-01-22T03:24:19Z")

</div>

I don’t get why they allow us to post the situation publicly but don’t resolve it where all can see what we should do as if we aren’t experiencing the same problem

---

<div class="post-metadata">

**Author:** ![Michael11](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@Michael11](https://community.ultraloq.com/u/Michael11)\
**Post date:** [January 22, 2023, 6:09pm UTC](https://community.ultraloq.com/t/unauthorized-access/4252/11 "2023-01-22T18:09:37Z")

</div>

THis Lock is very buggy and the fact that you cannot get Weekend Support is starting to really annoy the crap out of me.
