# \[APP\] Reolink **URL:** \ **Category:** Apps\ **Created:** [February 27, 2026, 9:05am UTC](https://community.homey.app/t/app-reolink/151761 "2026-02-27T09:05:26Z")\ **Posts on this page:** 20\ **Page:** 17
**Author:** ![march](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/march/32/121098_2.png) [@march](https://community.homey.app/u/march)\ **Post date:** [August 28, 2026, 6:25pm UTC](https://community.homey.app/t/app-reolink/151761/333 "2026-08-28T18:25:10Z")
@Koktail Hi. very nice app. All my 7 Reolink cameras are working and connecting fine with it. Is it possible to make use of the line crossing alert trigger in a flow? ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [August 28, 2026, 7:20pm UTC](https://community.homey.app/t/app-reolink/151761/334 "2026-08-28T19:20:46Z")
My Homey doesn’t really have the capacity for any more apps, or I might have considered SNMP (have used it plenty in the enterprise environment, and aware there are SNMP apps for Homey thanks). ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [August 29, 2026, 2:54am UTC](https://community.homey.app/t/app-reolink/151761/335 "2026-08-29T02:54:23Z")
Changes in 1.4.17 (test): - Added separate face detection with its own flow cards (previously grouped under person detection) - Fixed hub-connected cameras that could stop reporting motion and detection events; unroutable - Events now fall back to reading the camera state directly - Refreshed the capability icons and the zoom in/out icons ---
**Author:** ![Seb\_Seb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seb_seb/32/120718_2.png) [@Seb\_Seb](https://community.homey.app/u/Seb_Seb)\ **Post date:** [September 3, 2026, 1:25pm UTC](https://community.homey.app/t/app-reolink/151761/336 "2026-09-03T13:25:28Z")
I have problems with 3 out of 5 of my cameras, get an error message saying: player unable to open the MRL rtsp://admin blablalba/preview\_01\_main. But when I switch to sub - h264 the camera works but the quality is really bad. These 3 cameras used to work with the main stream before. The to other cameras that are working have 264 as main stream. Any suggestions what might have happened? Homey version is v1.5.0 experimental. ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [September 3, 2026, 3:08pm UTC](https://community.homey.app/t/app-reolink/151761/337 "2026-09-03T15:08:17Z")
@Seb_Seb Hi, the H.265 codec isn’t officially supported by Homey and its WebRTC feed. Depending on the resolution of the stream, and available bandwidth it sometimes manages to show in burst, but not reliably. For any cameras that support changing their main stream to H.264 in their Stream settings this fixes the problem. For cameras that are fixed to H.265 for their main stream you have to use the sub stream for reliable video feed. **Further information:** WebRTC support for H.265 (HEVC) is growing natively in modern browsers like Google Chrome (version 136+) and Safari, but it still faces fragmentation and interoperability gaps across platforms like Microsoft Edge. **Browser Support Status** Google Chrome: Native H.265 support is available starting in version 136, letting you send and receive streams without flags. Safari: Supports H.265 natively across Apple devices leveraging hardware acceleration. Microsoft Edge: Supports receiving in some capacities, but publishing or sending H.265 via WebRTC is often excluded or blocked depending on updates and device capabilities. Mozilla Firefox: Does not support H.265 natively in WebRTC. **Key Benefits** Bandwidth Savings: Offers roughly 50% better compression efficiency compared to older H.264 at equivalent visual quality. Higher Resolutions: Efficiently handles 4K and 8K video feeds with 10-bit HDR color support. Hardware Acceleration: Relies heavily on GPU decoding and encoding on modern hardware, reducing overall CPU usage and preserving battery life. **Current Challenges** Licensing Complexities: H.265 is royalty-bearing and governed by patent pools like MPEG-LA, complicating open-source rollouts. Interoperability: Differing implementations between browsers (such as Chrome supporting send/receive while other engines lag behind) can cause negotiation failures in real-time streaming applications. ---
**Author:** ![Seb\_Seb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seb_seb/32/120718_2.png) [@Seb\_Seb](https://community.homey.app/u/Seb_Seb)\ **Post date:** [September 3, 2026, 4:28pm UTC](https://community.homey.app/t/app-reolink/151761/338 "2026-09-03T16:28:13Z")
Hello, thanks for the explanation. Not really the answear I was hoping for tho… 🙂 I can only make 1 out of the 3 cameras to stream main stream 264 but the 2 newer once are locked to 265 on main stream. I removed the experimental app the installed the 1.4.14 version and Im able to stream 265 now but only for like 30 seconds. Hopefully the 265 will work in the future. ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [September 3, 2026, 4:34pm UTC](https://community.homey.app/t/app-reolink/151761/339 "2026-09-03T16:34:05Z")
> [@Seb\_Seb](#): > > Hopefully the 265 will work in the future. As support for H.265 improves across all browsers, it will improve… but a lot of it is down to the licensing and the different browsers agreeing on how best to implement it 🤣🙈🤣 ---
**Author:** ![Seb\_Seb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seb_seb/32/120718_2.png) [@Seb\_Seb](https://community.homey.app/u/Seb_Seb)\ **Post date:** [September 3, 2026, 4:53pm UTC](https://community.homey.app/t/app-reolink/151761/340 "2026-09-03T16:53:19Z")
Well I was playing around some more with the bitrate and I have streamed with h.265 now for 15 minutes on 2 of the cameras without any problems from the homey app. There is only one camera there is a problem with and that one I can change in the reolink app to main h264 so this might not really be a problem after all 😃 ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [September 3, 2026, 5:32pm UTC](https://community.homey.app/t/app-reolink/151761/341 "2026-09-03T17:32:01Z")
It isn’t officially supported… doesn’t mean without tweaking you can’t get it to mostly work 😉 Out of my 8 cameras, there’s only one I struggle with… and that’s locked to H.265 for both streams being a Duo 3V with dual lenses stitched together for 180° field of view… the bit rate is just too high to work consistently. But it still manages to notify if person detection with a still snapshot. ---
**Author:** ![march](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/march/32/121098_2.png) [@march](https://community.homey.app/u/march)\ **Post date:** [September 5, 2026, 9:50am UTC](https://community.homey.app/t/app-reolink/151761/342 "2026-09-05T09:50:04Z")
\*bump > _@Koktail Hi. very nice app. All my 7 Reolink cameras are working and connecting fine with it. Is it possible to make use of the line crossing alert trigger in a flow?_ ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [September 9, 2026, 12:26pm UTC](https://community.homey.app/t/app-reolink/151761/343 "2026-09-09T12:26:58Z")
Changes in 1.5.1 (test): - Fixed hub and NVR connected cameras that could stop reporting motion and AI detection after the connection to the recorder dropped. The app now reconnects on its own without needing a restart - Fixed detection flow triggers that could fail to fire before the first camera snapshot was ready ---
**Author:** ![Joe75](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joe75/32/19891_2.png) [@Joe75](https://community.homey.app/u/Joe75)\ **Post date:** [September 11, 2026, 5:54am UTC](https://community.homey.app/t/app-reolink/151761/344 "2026-09-11T05:54:04Z")
Hello, I’m having trouble with privacy mode on the E1 Outdoor Pro. As soon as I open the Reolink app and select the options, the camera switches to privacy mode. The default setting is always enabled on my device. I can’t turn the mode off because the camera goes offline; it is connected via Wi-Fi. I can’t get it back online afterwards—the only solution is a full reset. ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [September 11, 2026, 9:29am UTC](https://community.homey.app/t/app-reolink/151761/345 "2026-09-11T09:29:34Z")
This is a known bug. The app can switch privacy mode on by itself, and on some models the camera then goes offline until it is reset. There is no fix yet, and I need debug logs from an affected camera to find the cause. Could you enable debug logging (Homey \> Apps \> Reolink \> gear icon \> “Enable debug logging”) and then try again what went wrong before, so open the camera’s settings in Homey once? After that, press “Open support ticket” on the same settings page, so the logs reach me. If the camera drops offline again, a reset brings it back. ---
**Author:** ![Joe75](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joe75/32/19891_2.png) [@Joe75](https://community.homey.app/u/Joe75)\ **Post date:** [September 12, 2026, 5:46am UTC](https://community.homey.app/t/app-reolink/151761/346 "2026-09-12T05:46:08Z")
Hello, perhaps it makes sense to remove the feature from the app for the time being; the way it is now, it doesn’t make sense. The problem is easily explained: not every Reolink camera has a privacy mode. If a camera is connected via Wi-Fi and does not support privacy mode, it immediately goes offline. With cameras that do support it, there is at least the option to disable it via the manufacturer’s app. Therefore, the simplest solution would be for the Homey Reolink app to query the camera and only offer the privacy mode if the camera actually supports it. ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [September 12, 2026, 6:29am UTC](https://community.homey.app/t/app-reolink/151761/347 "2026-09-12T06:29:26Z")
That is exactly what the app does, but some models respond as supported when actually it isn’t. I cannot reproduce this on my devices so I need someone to reproduce what is happening. ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [September 12, 2026, 1:28pm UTC](https://community.homey.app/t/app-reolink/151761/348 "2026-09-12T13:28:07Z")
Would you be able to enable Debug Logging and reproduce the problem, then generate a Diagnostic Report before turning Debug Logging back off. Then send the developer the Diagnostic Report ID or just post it here for them. That may help with the resolving of this problem. They are in the Reolink app settings on your Homey. ![IMG_7793](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/6/96d598ba3815d6b8e4a526ad8693189bbdab889f.png) ![IMG_7792](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/b/eb6473d4bafbf43e4dc05a11a9fa90168a28a0a9.jpeg) ---
**Author:** ![march](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/march/32/121098_2.png) [@march](https://community.homey.app/u/march)\ **Post date:** [September 13, 2026, 9:03am UTC](https://community.homey.app/t/app-reolink/151761/349 "2026-09-13T09:03:10Z")
why is there no reaction on my simple question for more then 2 weeks? ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [September 13, 2026, 9:30am UTC](https://community.homey.app/t/app-reolink/151761/350 "2026-09-13T09:30:45Z")
Maybe the developer is busy and has other priorities 🤷‍♂️. There is also the option to contact the developer directly via his contact details on the [Homey App Store](https://homey.app/a/com.reolink/). ---
**Author:** ![Koktail](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koktail/32/51498_2.png) [@Koktail](https://community.homey.app/u/Koktail)\ **Post date:** [September 13, 2026, 9:55am UTC](https://community.homey.app/t/app-reolink/151761/351 "2026-09-13T09:55:20Z")
To give some context: I don’t work on the Reolink app full time and I maintain other projects next to it. I also don’t own every Reolink device, so some questions take longer to look into properly. Right now stability and fixing existing issues come first. I keep a backlog of everything that gets reported here, so if I don’t reply to a post it doesn’t mean it got lost. This topic collects questions and reports from a lot of users, so I can’t answer everything individually, but I do read along and work through the list. ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [September 15, 2026, 6:05pm UTC](https://community.homey.app/t/app-reolink/151761/352 "2026-09-15T18:05:08Z")
Hi @Koktail Having a slight glitch with some of my TrackMix PoE cameras (connected directly to my Homey Pro 2026 over my LAN, but recording over LAN to NVR RLN36) getting stuck in a detection state for hours. Executing a Repair and re-authenticating with the camera seems to clear it most times, but shouldn’t need to keep doing that, and it is growing tiresome. Example: a Badger entered my garden under the back gate, and was detected by my back gate camera, and then by my patio camera. The patio camera animal detection cleared when it should on its own. But the gate camera was stuck on animal detection all day until I manually repaired it. ![IMG_7810](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/f/cf173127c8058633e382e7eebee530dfa14e6016.jpeg) ![IMG_7811](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a20ca63ff2fd4fc409407a271e9d47e6f0343bb7.jpeg) Diagnostic Report: 97acf0bc-17f8-4226-bf28-4302140f5e26 Also, would it be possible to add a setting to the camera device card’s Advanced Settings screen to be able to specify a default stream to start when viewing the device. As the default is usually a high resolution H.265 stream that isn’t supported by Homey’s WebRTC feed, every time you open a camera you have to first drop down the menu and select the sub stream. This is most frustrating, and quite a daft way of accessing a camera feed, as by the time you have selected the correct feed the thing you wanted to view has gone. [Previous page](https://community.homey.app/t/app-reolink/151761.md?page=16) [Next page](https://community.homey.app/t/app-reolink/151761.md?page=18)