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.
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.
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:
- I activate my alarm system with RFID chip
- my speaker tells me which window is open
- i close it and activate the system.
I try to do this with this flow:
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.
Hi.
Can you show your Heimdall setting that you use to delay the DISARM action?
Here are the settings from heimdall.
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.
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 
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?
Iāll see if our developers can share some light on how itās handled by the device firmware.
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 āā
How far is the IO Module from your Homey?
Iād assume that timeouts happen due to lack of connection most of the time.
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.
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.
Please feel free to reach out to us on homey@frient.com.
However, Iād start by trying to move the device closer just to see if the problem still occurs.
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
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:
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?
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.
Any update on this?
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.
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
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.
