# \[APP\] Shelly Loqed - Your personal doorman

**URL:** https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816
**Category:** Apps
**Tags:** app, homey-pro
**Created:** [September 20, 2023, 2:02pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816 "2023-09-20T14:02:58Z")
**Posts on this page:** 20
**Page:** 5

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 21, 2024, 9:04pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/82 "2024-02-21T21:04:50Z")

</div>

> [@JvdMeulen](#):
>
> The "Als’-card isn’t triggered anymore, and it was before when the status changed …

Okay, ill have a look tomorrow.  
Could you make a printscreen of you When cards, so i can match my setup to yours? Thanks!

---

<div class="post-metadata">

### Author: ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)
#### Post date: [February 21, 2024, 9:15pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/83 "2024-02-21T21:15:31Z")

</div>

This is a “When”-card

> [@JvdMeulen](#):
>
> ![Capture 2024-02-21 at 21.46.36@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/6/26c804fc36b5ac25e8fe320804864ead86fe1fe1.png)

---

<div class="post-metadata">

### Author: ![Glenn\_Seegers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/glenn_seegers/32/8353_2.png) [@Glenn\_Seegers](https://community.homey.app/u/Glenn_Seegers)
#### Post date: [February 21, 2024, 9:19pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/84 "2024-02-21T21:19:33Z")

</div>

It’s just a tip I didn’t ment it as an insult but ok, i had a lot of f ups with apps that had auto updates on and decided that i want to read the changelogs first before updating.

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 7:28am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/85 "2024-02-22T07:28:18Z")

</div>

> [@JvdMeulen](#):
>
> This is a “When”-card

Yes i know. But i need a printscreen of all available When cards so i know what options your lock has.

---

<div class="post-metadata">

### Author: ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)
#### Post date: [February 22, 2024, 7:39am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/86 "2024-02-22T07:39:12Z")

</div>

Ah sorry, this should be it

 ![Capture 2024-02-22 at 08.38.03@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/e/7e4c126b38fe6822d5d4c5cd3a779d834143cf0d.png)

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 12:28pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/87 "2024-02-22T12:28:42Z")

</div>

@JvdMeulen

> [@JvdMeulen](#):
>
> Ah sorry, this should be it

Well, its clear to me that you were never on the (old) testversion (3.3.0, when i toke over the app development). I just found out that one already had the bug in it making legacy devices not function properly.  
Appareantly, the Homey Webhook used for the “old” devices has just been “stolen” to be used for the new OAuth devices, thus making the legacy devices not work anymore.  
The sourcecode is still in the master branch tho, and i am busy solving it right now.

However, to not let you install 10 times to solve it, there is one thing i would need to know.  
Could you run this HomeyScript (replace the Testdeur with your lock name):  
`return _.find(await Homey.devices.getDevices(), x=>x.name=='Testdeur');`

In the response, you will find

```auto
"data": {
    "id": *****
  },

```

I need to know if the id is only a few numbers, or also contains leters.  
Could you let me know? Then i have a fixed version within the hour i think.

---

<div class="post-metadata">

### Author: ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)
#### Post date: [February 22, 2024, 12:48pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/88 "2024-02-22T12:48:38Z")

</div>

> [@Arie\_J\_Godschalk](#):
>
> Well, its clear to me that you were never on the (old) testversion (3.3.0, when i toke over the app development)

I never said i was, did i?

> [@Arie\_J\_Godschalk](#):
>
> However, to not let you install 10 times to solve it,

Thanks, i appreciate that.

> [@Arie\_J\_Godschalk](#):
>
> the Homey Webhook used for the “old” devices has just been “stolen” to be used for the new OAuth devices

Who did that?

> [@Arie\_J\_Godschalk](#):
>
> I need to know if the id is only a few numbers, or also contains leters.

It’s exactly 5 numbers

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 12:55pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/89 "2024-02-22T12:55:29Z")

</div>

> [@JvdMeulen](#):
>
> It’s exactly 5 numbers

Thanks.

I have just solve the issue for “legacy” devices, and its already pushed to live:

> **[LOQED](https://homey.app/en-us/app/com.loqed.touch-smart-lock/LOQED/)**
>
> Your personal doorman

Update your app, and it should work as it did before.

If you still run into issues, please let me know.

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 1:06pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/90 "2024-02-22T13:06:08Z")

</div>

> [@JvdMeulen](#):
>
> I never said i was, did i?

No you didn’t 😉  
If you did, you would then have already had this issue.  
For me, this insight gave me a way of tracking the issue, through comparing the 2.2 sourcecode to the 3.3.0 (and later) sourcecode.

> [@JvdMeulen](#):
>
> Who did that?

Well, i am assuming the previous developer.  
It seems that version 3.3.0 was not ment to keep supporting legacy devices, but would have required users to switch to the new devices.

Personally i think everyone would do good to remove the locks from homey and re-pair them with the new driver. **When connected through the new driver, you get a lott more options, beter insights, beter tags, etc.**  
However, imho, the legacy driver should stay active to give users the possibility to re-pair the locks when the have the time.

Now, personally, i wasn’t aware that version 3.3.0 (which i took over) already broke the legacy driver.  
I didn’t have LOQED before i took over.  
And to be fair, while i did test the legacy driver, to see of you could open/close the lock, i appareantly didn’t test well enough, because i didn’t notice the status of Homey not being updated when the locked changed through the LOQED app (or psychically).  
My bad.

But, afaik, it should no be fixed in version 3.4.3.

---

<div class="post-metadata">

### Author: ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)
#### Post date: [February 22, 2024, 1:06pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/91 "2024-02-22T13:06:58Z")

</div>

> [@JvdMeulen](#):
>
> ![Capture 2024-02-21 at 21.46.36@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/6/26c804fc36b5ac25e8fe320804864ead86fe1fe1.png)

It looks like this event is triggered twice

---

<div class="post-metadata">

### Author: ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)
#### Post date: [February 22, 2024, 1:16pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/92 "2024-02-22T13:16:25Z")

</div>

> [@Arie\_J\_Godschalk](#):
>
> It seems that version 3.3.0 was not ment to keep supporting legacy devices, but would have required users to switch to the new devices.

That’s all fine, but “you” ( developers in general ( and maybe athom can/should add some setting to prevent breaking changes )) shouldn’t push updates that “breaks” apps/flow that are in test.

Maybe i’ll upgrade, but i really want to keep the status change trigger. And no, i dont want to define/hook up-- all the if-cards.

Thank you for quickly take actions and solving the problem(s).

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 1:18pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/93 "2024-02-22T13:18:46Z")

</div>

> [@JvdMeulen](#):
>
> shouldn’t push updates that “breaks” apps/flow that are in test.

I’ll try my best.

BTW, version 3.4.3 will not activate the Lock Status Changed trigger if it has been changed through Homey.  
Update 3.4.4 solves this issue and is in review by Athom right now.

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 22, 2024, 2:11pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/94 "2024-02-22T14:11:34Z")

</div>

> [@JvdMeulen](#):
>
> Maybe i’ll upgrade, but i really want to keep the status change trigger.

I have just added this flowcard in version 3.4.5 for the new OAuth Devices.  
It’s in review now and will be published shortly.

---

<div class="post-metadata">

### Author: ![Wout\_van\_den\_Dool](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_van_den_dool/32/391_2.png) [@Wout\_van\_den\_Dool](https://community.homey.app/u/Wout_van_den_Dool)
#### Post date: [February 23, 2024, 9:56pm UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/95 "2024-02-23T21:56:17Z")

</div>

I experience since a day a lock which I cannot access. The device is offline. “Apparaat onbeschikbaar” I have version 3.4.5.

I did execute two weeks ago the API Reset and that worked fine. Now I cannot repair, deleted the device and re-installed it.

b3ff3c53-6918-46d4-8717-bbff67effbe7 is the report ID I shared with you.  
And just to be sure, this is part of the script output:

“uiIndicator”: null,  
“available”: false,  
“unavailableMessage”: “The device is offline”,  
“warningMessage”: “De status van dit slot is onbekend.”,  
“ready”: true,  
“repair”: true,  
“unpair”: false,  
“images”: ,  
“color”: “#002746”

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 24, 2024, 8:30am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/96 "2024-02-24T08:30:47Z")

</div>

> [@Wout\_van\_den\_Dool](#):
>
> Now I cannot repair

What happends if you do repair?  
Do you get the loginscreen? Does login goes as usual?

---

<div class="post-metadata">

### Author: ![Wout\_van\_den\_Dool](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_van_den_dool/32/391_2.png) [@Wout\_van\_den\_Dool](https://community.homey.app/u/Wout_van_den_Dool)
#### Post date: [February 24, 2024, 8:53am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/97 "2024-02-24T08:53:31Z")

</div>

Yes all goes as expected after repairing

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 24, 2024, 9:23am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/98 "2024-02-24T09:23:27Z")

</div>

@Wout_van_den_Dool As in, its working again?

---

<div class="post-metadata">

### Author: ![Wout\_van\_den\_Dool](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_van_den_dool/32/391_2.png) [@Wout\_van\_den\_Dool](https://community.homey.app/u/Wout_van_den_Dool)
#### Post date: [February 24, 2024, 9:38am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/99 "2024-02-24T09:38:05Z")

</div>

nope unfortunately not…

---

<div class="post-metadata">

### Author: ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)
#### Post date: [February 24, 2024, 10:13am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/100 "2024-02-24T10:13:16Z")

</div>

@Wout_van_den_Dool do you have other locks that do work? Or just the one?

---

<div class="post-metadata">

### Author: ![Wout\_van\_den\_Dool](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_van_den_dool/32/391_2.png) [@Wout\_van\_den\_Dool](https://community.homey.app/u/Wout_van_den_Dool)
#### Post date: [February 24, 2024, 11:16am UTC](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816/101 "2024-02-24T11:16:44Z")

</div>

Just that one…, think I found a root cause, bridge is disconnected from the WiFi (dead)

[Previous page](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816.md?page=4)

[Next page](https://community.homey.app/t/app-shelly-loqed-your-personal-doorman/89816.md?page=6)
