# \[APP\] Reolink

**URL:** <https://community.homey.app/t/app-reolink/151761>\
**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:** 6\
**Page:** 19

<div class="post-metadata">

**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:** [October 13, 2026, 6:58am UTC](https://community.homey.app/t/app-reolink/151761/373 "2026-10-13T06:58:47Z")

</div>

Reolink v1.6.2 is live

Install: [Reolink | Homey](https://homey.app/a/com.reolink)

v1.6.2

- Cameras behind a hub or NVR get their own motion detections, even when a channel on the hub is empty.

---

<div class="post-metadata">

**Author:** ![Fant4](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fant4/32/120854_2.png) [@Fant4](https://community.homey.app/u/Fant4)\
**Post date:** [October 14, 2026, 5:57pm UTC](https://community.homey.app/t/app-reolink/151761/374 "2026-10-14T17:57:34Z")

</div>

Anyone can help me?

---

<div class="post-metadata">

**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:** [October 14, 2026, 6:06pm UTC](https://community.homey.app/t/app-reolink/151761/375 "2026-10-14T18:06:40Z")

</div>

@Fant4 Have you tried changing the stream to the sub-stream?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/4/8449df263de2bfcc9d62eaa228d6724aee41078a.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/8/485c80a70e0806e179c8758b71f214760d0d4b15.png)

H.265 CODEC isn’t supported by the WebRTC implementation that Athom uses for Homey.

---

<div class="post-metadata">

**Author:** ![Fant4](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fant4/32/120854_2.png) [@Fant4](https://community.homey.app/u/Fant4)\
**Post date:** [October 14, 2026, 6:54pm UTC](https://community.homey.app/t/app-reolink/151761/376 "2026-10-14T18:54:37Z")

</div>

Yes, I’ve tried, but I still get a black screen and it doesn’t work. I haven’t changed anything, yet it suddenly stopped working more than 10 days ago.

Only snapshot works now in Homey… But in Reolink App all cameras working fine.

 ![1000104523](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/9/59b1160ffe887230b40c43bd42f25705c40f4b29.jpeg)

---

<div class="post-metadata">

**Author:** ![Fant4](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fant4/32/120854_2.png) [@Fant4](https://community.homey.app/u/Fant4)\
**Post date:** [October 14, 2026, 7:55pm UTC](https://community.homey.app/t/app-reolink/151761/377 "2026-10-14T19:55:13Z")

</div>

**SOLVED: WebRTC offer failed – 404 page not found (Homey SHS)**

I finally managed to solve this issue, and I wanted to share the solution in case it helps other Homey SHS users.

All my Reolink cameras suddenly stopped working in Homey, showing a black screen with the following error:

`WebRTC offer failed: Not Found: 404 page not found`

The cameras were still reachable and working correctly through the Reolink app. The problem affected all cameras, and restarting or updating Homey and the Reolink app did not resolve it.

**Root cause:** The bundled `go2rtc` version was **1.9.13**.

**Solution:** I replaced the bundled `go2rtc` binary with the official **1.9.14** release, then restarted the Homey SHS Docker container.

After the restart, all my cameras started working again!

For reference, the binary was located at:

`/app/packages/homey-local/assets/bin/amd64/go2rtc`

I downloaded the official Linux AMD64 release from the go2rtc GitHub repository, verified its SHA-256 checksum, backed up the original binary, replaced it, and restarted the container.

**Important:** This was a manual workaround in my installation. The replacement may be overwritten by a future Homey SHS update, and I recommend backing up the original binary and verifying the correct architecture before attempting the same procedure.

Hopefully, this helps anyone experiencing the same WebRTC 404 error!

---

<div class="post-metadata">

**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:** [October 16, 2026, 12:04pm UTC](https://community.homey.app/t/app-reolink/151761/378 "2026-10-16T12:04:56Z")

</div>

Reolink v1.7.0 is available on test

Install: [Reolink | Homey](https://homey.app/a/com.reolink/test/)

v1.7.0

- A new setting opens the H.264 stream first, so H.265 cameras show video in the Homey web app.
- Actions are blocked while privacy mode is on.
- A command the camera refuses or does not answer shows a clear error.
- Hubs clean up properly when removed during startup or reconnect.
- The RLN4E NVR is recognised.

[Previous page](https://community.homey.app/t/app-reolink/151761.md?page=18)
