Tried both triggers and the ‘person detected’ was ass you said also triggered when not pressing.
The 1 second option didn’t work before but it now does, though it still feels like a workaround. I am just amazed why there is not a ‘doorbell pressed’ trigger.
@Koktail
“What is the reason that the ‘visitor’ flow card has disappeared?”
A flow trigger card of “Doorbell Pressed” that triggers the instant the doorbell is pressed (or even just being able to validly enter 0 in the current card) for immediate action without having to wait for X seconds and then see the tail lights of the Amaz…ing delivery driver disappear in to the distance by the time you get to the door would be extremely helpful. Most other trigger cards in flows with a delay allow you to enter 0 for immediate action, why not this one? Is there some technical reason for this we are just not aware of? @Koktail
Are you sitting down? 
I agree!
Hello everyone,
Unfortunately, I am encountering the following problem again (one that I have experienced previously).
The flow is as follows:
IF → Camera 1 detects a person, THEN → The Reolink app should open on an external display.
This worked well for a while.
Now, however, I am experiencing false triggers again. The app launches—and I simultaneously receive a push notification containing a still image—but there is no person present to trigger the flow.
I have now discovered that it is Camera 2 triggering the flow, rather than Camera 1.
It is the exact same problem as before.
Could this be due to the fact that the cameras are still using dynamic IP addresses? In my router (a Fritzbox), I have the option to assign static IPs to all devices, ensuring that their IP addresses never change. Would doing this help? Could this potentially be the root of the problem?
You should definitely assign static IP addresses to the cameras.
Hi Heinz,
I’ll implement that this afternoon. Then I’ll test again. I had already suspected as much.
Hi everyone,
Assigning static IPs to the cameras and other devices did indeed help.
However, I’ve noticed something else.
Camera 1 (TrackMixWlan) isn’t using the Home Hub’s Wi-Fi network, but rather the Fritz!Box’s, and it’s triggering the detected person correctly.
Camera 2 (E1 Pro Outdoor) is using the Home Hub’s Wi-Fi network, but it’s not reliably triggering the camera.
Do you have any insights on this? Do you need more information?
Is there any issue with the F850W Camera? I can’t add it to Homey using the Reolink app, but it works fine with the ONVIF app. However, I’d like to control the light as well.
The “doorbell is pressed for X seconds” card is the default trigger that Homey generates for the default doorbell capability that we are using. It fires based on the ONVIF event the moment the button is pressed. (And it different then the “Person detected”, which triggers on the camera’s AI spotting function)
The minimum of 1 second is a Homey platform limitation, not something we can change on the app side.
This is most likely a network issue, not a camera or app problem.
The app receives detection events (person, motion, etc.) from your cameras via ONVIF push notifications over TCP port 8000. This requires a stable, direct connection between Homey and the camera on the same subnet.
Your Camera 1 works fine on the Fritz!Box Wi-Fi, but Camera 2 on the Home Hub’s Wi-Fi is unreliable
this suggests the two Wi-Fi networks are on different subnets preventing the ONVIF events from reaching Homey.
to capture the 'deurbel gedrukt event"
happy ringing 
Hi, I’m looking to integrate 2-way audio on Zendo. I can establish a WebRTC connection. The mic from the phone does stream to the doorbell but the doorbell microphone doesn’t stream back. On the Homey web app there’s no audio at all (nor there’s any in the iOS app). Both primary and secondary doorbell tracks over RTSP are streaming AAC (which is not WebRTC standard). could that be the issue?
I’ve tried Unifi over WebRTC and I do get the camera audio streaming so the player is negotiating audio correctly.
Diagnostics: b6d0c04c-77aa-4675-b96b-2e6aaa60711a
Happy to provide the full WebRTC negotiation.
Hello,
I am using the Reolink app on my Homey Pro 2023.
The livestream is working properly, but for more than 5 days Reolink has no longer been sending or showing person or vehicle detections.
My Homey Pro 2023 is connected by cable and via WiFi.
My Reolink Recorder is connected using a UTP cable.
Could you please check what is causing this issue and how it can be resolved?
Thank you in advance.
Have you tried connecting your Homey Pro to your network via only one single connection method, either Ethernet cable, or WiFi. Multiple connections can cause communication errors/drop-outs. If you have an Ethernet LAN cable connection, there is no need to connect WiFi also.
When was your Homey Pro last restarted? And have you tried restarting the ReoLink app on your Homey?
I just released v1.1.19 to production with a lot of improvements : https://homey.app/en-nl/app/com.reolink/Reolink
New features
Improvements
Bug fixes
Thank you sooooooo much for this, excellent work!
Can I ask if there is a reason there is a “Connection Lost” trigger card, but not a Connection Restored trigger card (and no “Invert” option on the Connection Lost card)?
Hi Koktail,
Thank you so much for your hard work and all these amazing updates!
Do you happen to know when scene management will be available for the Reolink Home Hub? Thanks again for keeping this app so well-maintained!
i just bougt a reolink argus series b320 camera to connect with homey but i can’t get a connection. i do have the camera connected troug the reolink phone app but i can nog get it in to homey also i can’t find the onvif settings.
did u buy the wrong camera?
The Argus battery/solar cameras don’t support the necessary protocols to work with Homey. Powered cameras only.
