Thanks for the detailed report. The issue was caused by introducing detection updates through Baichuan (besides the ONVIF). When those updates arrived very close together, a “cleared” event could be missed while the previous “detected” update was still being processed. v1.5.5 contains the fix and is on test right now.
Could you test it and let us know whether the detection now clears correctly?
You are most welcome (I only wish everyone could do a bit of their own testing and provide details when reporting issues)
I have installed and running the test version 1.5.5. And I will monitor camera detection events, and advise of any further issues. But as the problem was intermittent in nature, I don’t have any specific way to test for it.
The other issue I reported, would it be at all possible to have a setting to specify the default stream to auto play on opening the camera device card?
Thank you.
The suggestion is in the backlog to investigate.
Changes in 1.5.6 (test):
Fixed cameras that could switch themselves into privacy mode and then drop off the network. The app was asking the camera whether privacy mode was on, and on some models that question was enough to turn it on. The app now only listens to what the camera reports on its own, and cameras that never report a privacy state no longer show the switch
Fixed motion and AI detection that could stay stuck on until the app was restarted
Hi Koktail @Koktail
Sorry to be the bearer of bad news, but this latest version has FUBAR’d a number of my Advanced Flows for my PoE video doorbell & RLC-1212A. Both of which previously supported/worked with Privacy, but both seem to have lost that function now which has rendered a number of my Flows non-functional.
Diagnostic Report: 9554b4a4-4b7f-4715-9589-f8564120d32a
Reolink 1.5.7 is on test.
1.5.6 checked whether a camera supports privacy mode in the wrong place. The answer it looked for does not exist there, so the app decided that no camera supported it and took the switch away. If you had flows using privacy mode, Homey dropped those cards the moment the capability disappeared.
Sorry for that, a working flow should never break over a detection change. Privacy mode is a stubborn thing to detect, it lives in one bit of a separate binary command and plenty of models never mention it at all.
1.5.7 asks the camera itself. The switch is never removed again, only added when a camera confirms it. It comes back by itself after the update, usually right away, and for battery cameras as soon as they are awake.
1.5.8 fix: Improve discovery to prevent timing out
One thing does not fix itself. A flow card that fell out of a flow stays out. If a privacy mode step went missing from one of your flows, add it again after the update.
Hi Koktail @Koktail
Having a problem with a camera sticking on motion detection again. It’s a RLC-1212A PoE 12MP camera, that records to a RLN36, and is also connected to directly from Homey Pro (2026).
I have tried several times to do a Repair, re-entering the cameras password, but it disconnects the camera. And then running the Repair again and pasting the exact same password from my password manager reconnects the camera, but the same motion detection is still stuck on, and there is no one in the room with the camera.
App Version: 1.5.9
Diagnostic Report ID: 27a4217b-2a18-400a-89d8-67fe502a8a9c
Reolink 1.5.10 is on test.
Fix: improved stability for hubs and NVRs without ONVIF profiles. Motion events from cameras behind such a hub are now handled more efficiently, which reduces load on the app and lets battery cameras sleep as intended.
If you use a hub or NVR, please give 1.5.10 a try and let me know how it runs. If anything looks off, enable debug logging in the app settings and open a ticket so I can look into it.
Reolink 1.5.10 is live.
1.5.2 Updated the Reolink network settings path in the pairing instructions.
1.5.3 Argus Solar cameras behind a hub are now recognised.
1.5.4 Doorbell chime volume now works when the doorbell is connected through a Home Hub or NVR.
1.5.5 Detection states no longer get stuck when ONVIF and hub events overlap.
1.5.6 Privacy mode detection no longer probes cameras that do not support it, state and switches stay intact.
1.5.7 The privacy mode switch is back on cameras that support it.
1.5.8 Discovery no longer times out when adding cameras.
1.5.9 Connection handling improved so motion events are no longer missed after a reconnect.
1.5.10 Hubs and NVRs without ONVIF profiles no longer send the app into a restart loop.
Just got an email from shelly at reolink support that the new firmware for the 2nd gen video doorbell with RTSP/ONVIF support has gone live! Looking forward to testing homey compatibility
Reolink v1.6.1 is available in test
Install: Reolink | Homey
v1.6.0
v1.6.1
Hello,
Is there a solution yet for the issue where the camera’s motion status gets stuck in the ‘active’ state? I have connected 8 Reolink RLC-824 cameras, but the motion status remains stuck; this prevents the creation of reliable flows, as the zones containing the cameras effectively remain active. Does anyone have a solution? Regards,
Alex
Reolink v1.6.2 is available in test
Install: Reolink | Homey
v1.6.2
A fix for detection states that got stuck was released in v1.5.5. The 1.6.x versions also improve how the app recovers its connection to cameras.
Could you tell me which app version you are running? Please also turn on the switch Enable debug logging in the app settings. When a camera gets stuck again, use the Open support ticket button below that switch and mention the camera name. Your logs are linked to the ticket automatically, so I can see which events came in from that camera and which ones went missing.
Hello,
The issues I described previously occurred in version 1.5.10; I am now using version 1.6.2, and the problems with the motion status getting stuck seem to be resolved. However, I have encountered another issue: the app does not recognize person or vehicle detection, reporting only that the motion alarm has triggered or cleared. If I link a flow to this—specifying that the flow should run when the motion alarm triggers and a person or vehicle is detected—nothing happens; the same applies if I start the flow based specifically on a person or vehicle being detected. Yet, in the Android Reolink app, the recording clearly shows it was triggered by a vehicle or person. I hope there is a solution for this; please let me know if any testing or further information is needed so we can resolve the issue. Tested with version 1.6.2 and Reolink RLC-824A.
Regards, Alex
Hi Koktail,
Since the last release, my PoE video doorbell has stopped reporting when it goes off-line. All other PoE and solar camera models that I have still report off-line okay, it is just the video doorbell (the one that has the privacy function).
I have my RLN36 NVR configured to do a weekly reboot at a set time, and I have Flows on my Homey Pro (2026) for all the cameras and NVR, which send me a Push notification when any of them goes off-line. It’s a good sanity check, to make sure the notification is working, and clear everything out once a week to keep them all running their best. I stopped getting the Push notification the the doorbell after the last update.
If you need any additional details from me just holla. Thank you kindly.
EDIT 1: It would also be extremely helpful if the video doorbell had a WHEN trigger card for when the Privacy mode is changed (similar to the AND card that allows you to select On or Off would be nice, but just that it changed is really needed as you could then test which way it was switched On or Off with the AND card).
EDIT 2: I have also just discovered that the Homey Reolink app is thinking the video doorbell is in Privacy mode, despite the doorbell not being so, and when I open the device card with my hand in front of the lens (manually imposing privacy) you get a lovely live video feed of the palm of my hand along with the notification to the contrary of privacy mode… it’s busted ha ha 
And if I go to the selector page and select Privacy mode on, then check the video, no charge. Same if I select Privacy mode off. But if I repeat this several times with a short pause between each to allow the command to be sent and acted upon, after several iterations it does eventually change to Privacy Mode. But I have to repeat this process 2 or 3 times again to disable Privacy Mode.
Hello,
I’m experiencing a problem with the Reolink app on Homey.
All of my Reolink cameras have suddenly stopped displaying the live video in Homey. They all show the same error:
“WebRTC offer failed: Not Found: 404 page not found”
This affects all my Reolink cameras, not just one specific device.
My cameras are working perfectly in the official Reolink app, so the cameras and network connection appear to be working correctly.
My setup:
I have already tried changing the Homey camera connection from HTTPS/443 to HTTP/80, but this did not solve the problem. The cameras disconnect from Homey when using HTTP, so I restored HTTPS/443.
The important point is that all cameras are affected at the same time and they all return the same WebRTC 404 error.
This was working correctly before, without changing the configuration of the cameras.
Has anyone experienced the same problem recently? Could this be related to a Homey/WebRTC issue or a recent update of the Reolink app/Homey?
I would appreciate any advice or suggestions on how to troubleshoot this.
Thank you
Goodmorning. Compliments for the builder! What a great app. Thanks.
I hope I have a simple question (Claude could not find it): for my outside camera I want to be able to put it to sleep (eg when I am home or at certain times a day) and awake it using a THEN trigger in flows. Is this easy to add? Apparently using Home Assistant it is possible.
Thanks a lot in advance.
Hello - My reolink RLC-410-5MP IPC_515B16M5M used to work but is not working anymore.
Note that my reolink RLC-410-5MP IPC_51516M5M (not B) is working perfectly.
They have the same network configuration and same firmware v3.0.0.2356_23062000
Note a new homey app release that contains a fix: Fixed picker initial scroll positioning. Older app versions might have caused irradic behaviour for pickers. For me, it also seems to change the picker value once I opened a picker, also for my Reolink camera settings.
