# \[APP\]\[Pro&Cloud\] frient Zigbee App (v2.5.4)

**URL:** <https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161>\
**Category:** Apps\
**Tags:** app, zigbee, flow, homey-pro, homey-bridge\
**Created:** [February 8, 2023, 9:47am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161 "2023-02-08T09:47:45Z")\
**Posts on this page:** 20\
**Page:** 18

<div class="post-metadata">

**Author:** ![tommy\_dog](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tommy_dog/32/79589_2.png) [@tommy\_dog](https://community.homey.app/u/tommy_dog)\
**Post date:** [January 19, 2025, 8:13am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/349 "2025-01-19T08:13:33Z")

</div>

When is the keypad being updated to support multiple pin codes natively? This is something that has been repeatedly promised for well over a year. It appears that multiple pins do work for Heimdall, but this DOES NOT WORK ON THE Bridge.

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 20, 2025, 7:25am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/350 "2025-01-20T07:25:02Z")

</div>

Hi Jakob. That’s a nice idea, but unfortunately it won’t be possible, since the device sends the entered tag’s ID or PIN code only when the button is pressed afterwards - it’s coded in the device itself (not a driver) to work this way.

---

<div class="post-metadata">

**Author:** ![Jakob\_Thinggaard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jakob_thinggaard/32/121229_2.png) [@Jakob\_Thinggaard](https://community.homey.app/u/Jakob_Thinggaard)\
**Post date:** [January 22, 2025, 9:17pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/351 "2025-01-22T21:17:13Z")

</div>

I want to make a flow that allows me to cancel my Arming of the alarm system in the case that a window is open.

The desired workflow is:

1. I activate my alarm system with RFID chip
2. my speaker tells me which window is open
3. i close it and activate the system.

I try to do this with this flow:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a6ab9c8ea4fa3bb9ad228cf0fa3a51ef17735a89.png)

However… When i try to do this, my Frient Keypad starts beeping 30 seconds (the delay set in Heimdall) before it is disarmed. This means, that the system is never Armed in that period. I want to skip the 30 second beeping. How do i do this? I have tried to do this via this card, but the Frient is not in the list of devices.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/a/bab81c0287927d23701d7aafcea6d3872aec77d1.png)

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 24, 2025, 7:12am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/352 "2025-01-24T07:12:31Z")

</div>

Hi.

Can you show your Heimdall setting that you use to delay the DISARM action?

---

<div class="post-metadata">

**Author:** ![Jakob\_Thinggaard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jakob_thinggaard/32/121229_2.png) [@Jakob\_Thinggaard](https://community.homey.app/u/Jakob_Thinggaard)\
**Post date:** [January 24, 2025, 7:32am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/353 "2025-01-24T07:32:20Z")

</div>

Here are the settings from heimdall.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/c/6c7e04276f722cc71cb91ae33e8b784a4f870dc6.png)

Is there a smart way to also exclude a specific door (main door) from being detected as open during countdown? In reality, my main door may be open as I activate the alarm. I don’t want the Heimdall to detect this as open during the countdown and cancel the activation.

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 24, 2025, 11:54am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/354 "2025-01-24T11:54:41Z")

</div>

That seems like something that could be handled by Heimdall app I believe - for example, an action card that could disable or change the delay time.

Perhaps @DaneedeKruyff could share his opinion 🙂

---

<div class="post-metadata">

**Author:** ![Jakob\_Thinggaard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jakob_thinggaard/32/121229_2.png) [@Jakob\_Thinggaard](https://community.homey.app/u/Jakob_Thinggaard)\
**Post date:** [January 26, 2025, 7:38pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/355 "2025-01-26T19:38:34Z")

</div>

Hi Frient,

Pls. read below comments regarding the frient Keypad. Any input on how i remove these 20 sec beeping when there is a window open?

> [@Heimdall - Let Homey watch over your home](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/1619):
>
> This indicates to me that the Keypad doesn’t handle the switch to disarmed in the right way, the disarming isn’t cancelled. I’m afraid that’s not something I can fix from this app. That’s valid, I see many flows where people add redundant cards that may interfere with what they want to achieve, that’s why I asked. There’s no impact on Heimdall whatsoever. It’s just a warning for the user, they will not be excluded.

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 27, 2025, 9:09am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/356 "2025-01-27T09:09:40Z")

</div>

I’ll see if our developers can share some light on how it’s handled by the device firmware.

---

<div class="post-metadata">

**Author:** ![sbjarnas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sbjarnas/32/80078_2.png) [@sbjarnas](https://community.homey.app/u/sbjarnas)\
**Post date:** [January 28, 2025, 2:56pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/357 "2025-01-28T14:56:48Z")

</div>

Hi, I’m having an issue with using the IO module on my Homey. When I enable one of the outputs, it works fine but Homey will after around 10 seconds, show the message:  
“Something went wrong while controlling \<my\_device\_name\>” Timeout after 10000ms

Any thoughts?

Homey Pro early 2023  
Homey version: 12.3.0  
Zigbee firmware version: 7.4.2-0

IO-module product ID: IOMZB-110  
zb\_sw\_build\_id “”

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 29, 2025, 7:10am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/358 "2025-01-29T07:10:38Z")

</div>

How far is the IO Module from your Homey?

I’d assume that timeouts happen due to lack of connection most of the time.

---

<div class="post-metadata">

**Author:** ![sbjarnas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sbjarnas/32/80078_2.png) [@sbjarnas](https://community.homey.app/u/sbjarnas)\
**Post date:** [January 29, 2025, 8:39am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/359 "2025-01-29T08:39:29Z")

</div>

Its around 10m away but on a different floor of the house. There are a bunch of other Zigbee devices around the house even further away which are interacting without any issues with the Homey. I didn’t have this issue with my older Homey 2019, just started noticing them after the recent upgrade to Homey 2023.

---

<div class="post-metadata">

**Author:** ![sbjarnas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sbjarnas/32/80078_2.png) [@sbjarnas](https://community.homey.app/u/sbjarnas)\
**Post date:** [January 29, 2025, 9:15am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/360 "2025-01-29T09:15:04Z")

</div>

Any more info I can provide as just saying “it doesn’t work properly” is not very useful for you guys. And should this chat be moved to some other platform instead of using this forum? Don’t want to clutter it up with too much of problem solving discussions.

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [January 29, 2025, 10:12am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/361 "2025-01-29T10:12:03Z")

</div>

Please feel free to reach out to us on [homey@frient.com](mailto:homey@frient.com).

However, I’d start by trying to move the device closer just to see if the problem still occurs.

---

<div class="post-metadata">

**Author:** ![Knut\_Danielsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/knut_danielsen/32/71219_2.png) [@Knut\_Danielsen](https://community.homey.app/u/Knut_Danielsen)\
**Post date:** [February 3, 2025, 12:25pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/362 "2025-02-03T12:25:14Z")

</div>

Is it possible to get Develco devices to use the Frient app. Currently it seems that Develco app is not uppdated in last 3 years. Drivers for HAN device will not be according to new standard for Energy

---

<div class="post-metadata">

**Author:** ![tommy\_dog](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tommy_dog/32/79589_2.png) [@tommy\_dog](https://community.homey.app/u/tommy_dog)\
**Post date:** [February 7, 2025, 12:05am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/363 "2025-02-07T00:05:50Z")

</div>

> [@frient](#):
>
> I tried again on Homey Bridge - you can see the video:
> 
> [IMG\_8359.MOV - Google Drive](https://drive.google.com/file/d/1_6nKdcvmwsOB3VdvCDxmR5fIRq3XV148/view?usp=sharing)
> 
> It works exactly the same, just a bit slower - Homey Bridge in opposite to Pro is completely dependent on your internet connection, therefore perhaps there is a problem?
> 
> It’s hard to debug with this little information - perhaps you can share a video as well if you still believe the problem is with frient app.

I am sorry but it just does not work. Today I took a video as proof. It has never worked for tags with my Homey bridge. I tried it in the video with google pixel 7a phone, but its not working. I also tried it with a Sony phone and an unbranded Chinese phone. I also tried it with multiple tags. I purchased over 20 different types of RFID tags (according to your spec ISO14443A and MIFARE classic) but nothing works. I have tried doing it slower, quicker and spent hours on this.

Here is my video:

[![](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/c/9c5edf44be2a3ba7717813da7266ba9068f4fce9.jpeg "not working") ](https://www.youtube.com/watch?v=_mRAuFqachw)

Please look into this urgently as I have been trying to get it working for months. Its bad enough not having multiple pin support on the bridge, but not even having a working RFID solution is just rubbish. You call it a smart keypad, but it only supports one pin and no RFID cards are working on the Bridge. Its a pretty poor experience.

You should have a reliable interface, where you can simply add and remove RFID cards, and the facility to add and remove multiple pins. To rely on a 3rd party app such as heimdall for basic functionality is a huge mistake. Why did you not develop a proper native solution supported by your company? In any case, heimdall is not a solution for people who have the bridge. Go and test it for real with a Homey bridge. It simply does not work. Why are RFID cards not even working?

What is going on?

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [February 7, 2025, 1:11pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/364 "2025-02-07T13:11:00Z")

</div>

Hej Knut. At the moment, we don’t maintain the devices branded as Develco Products on Homey, and therefore, Develco Products app on Homey.

The reason for it is that these devices were never really meant to be used with a third-party gateways such as Homey, and the number of customers actually using it this way is really low.

However, I’ll see if that would be possible to make them use frient app - I’ll come back to you on this.

---

<div class="post-metadata">

**Author:** ![Jakob\_Thinggaard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jakob_thinggaard/32/121229_2.png) [@Jakob\_Thinggaard](https://community.homey.app/u/Jakob_Thinggaard)\
**Post date:** [February 9, 2025, 6:57pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/365 "2025-02-09T18:57:24Z")

</div>

> [@frient](#):
>
> I’ll see if our developers can share some light on how it’s handled by the device firmware.

Any update on this?

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [February 10, 2025, 8:22am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/366 "2025-02-10T08:22:46Z")

</div>

Hej tommy\_dog.

I tried to re-produce your issue once again.

For this, I used a brand new Homey Bridge, and brand new Intelligent Keypad.

I set-up a Homey Bridge, installed the frient app, and connected the keypad. Then, I went to the device’s settings and added RFID tag.

Everything worked flawlessly, so I don’t know why it does not work for you, but clearly, this isn’t anyhow related to frient app on Homey.

Edit:

Once again, consider the distances between the keypad and your Bridge, and if your Bridge has sufficient internet connection.

Also, your RFID tags are successfully read by the device (you can hear the beep) when you apply them, so it’s not the case here.

---

<div class="post-metadata">

**Author:** ![Knut\_Danielsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/knut_danielsen/32/71219_2.png) [@Knut\_Danielsen](https://community.homey.app/u/Knut_Danielsen)\
**Post date:** [February 10, 2025, 11:27am UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/367 "2025-02-10T11:27:48Z")

</div>

Thanks appreciate this. But Develco as a product worked on numerous of 3de-party gateways and the devices named Frient is Develco as stated on Develco Product page 🙂

---

<div class="post-metadata">

**Author:** ![frient](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frient/32/68875_2.png) [@frient](https://community.homey.app/u/frient)\
**Post date:** [February 10, 2025, 1:31pm UTC](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161/368 "2025-02-10T13:31:02Z")

</div>

Well, yes, but Homey was the only integration for DP products that was created on our own initiative, and for other platforms it was their communities including support for it. I’ll see what we can do about it.

[Previous page](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161.md?page=17)

[Next page](https://community.homey.app/t/app-pro-cloud-frient-zigbee-app-v2-5-4/76161.md?page=19)
