# \[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:** 20\
**Page:** 7

<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:** [April 25, 2026, 8:22pm UTC](https://community.homey.app/t/app-reolink/151761/124 "2026-04-25T20:22:39Z")

</div>

That’s quite possibly your problem… running a release candidate of Homey OS. A possibly unstable test version. And once you’ve enabled that option, I think the only way to disable it and have stable release updates only is to do a factory reset of your Homey (which if memory serves me it has a warning message about possible unpredictable results and the factory reset needed to undo the enabling of that option).

Also, the Reolink app version 1.1.1 is labelled a Test version, with a large amber warning box just below the version number in the Homey app store, that it is not a tested release, and some issues may arise. So a test version app running on release candidate OS.

---

<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:** [April 25, 2026, 8:51pm UTC](https://community.homey.app/t/app-reolink/151761/125 "2026-04-25T20:51:06Z")

</div>

The only failing part is ONVIF: Network timeout

That means the camera is not responding on ONVIF port 8000. This usually means ONVIF is disabled, blocked, or not properly supported by this device/firmware.

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 25, 2026, 8:55pm UTC](https://community.homey.app/t/app-reolink/151761/126 "2026-04-25T20:55:50Z")

</div>

Are they employed by Homey or are they involved in the development of the Reolink software?

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 25, 2026, 8:57pm UTC](https://community.homey.app/t/app-reolink/151761/127 "2026-04-25T20:57:00Z")

</div>

Thanks, as I said, ONVIF worked perfectly until two weeks ago.

---

<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:** [April 25, 2026, 8:59pm UTC](https://community.homey.app/t/app-reolink/151761/128 "2026-04-25T20:59:35Z")

</div>

Excuse me, I am not following that. Is who employed by Homey or involved with ReoLink? Did I miss something?

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 26, 2026, 9:22am UTC](https://community.homey.app/t/app-reolink/151761/129 "2026-04-26T09:22:58Z")

</div>

The problem wasn’t with the Homey firmware 13.2.0-rc.2, but with the Reolink TEST version. I installed the official version and the flows are working again. I won’t be installing any more Reolink test versions.

---

<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:** [April 26, 2026, 10:37am UTC](https://community.homey.app/t/app-reolink/151761/130 "2026-04-26T10:37:21Z")

</div>

> [@Heinz\_Himmel](#):
>
> The problem wasn’t with the Homey firmware 13.2.0-rc.2, but with the Reolink TEST version. I installed the official version and the flows are working again

It’s more likely to be a problem with the interaction between the Reolink test version and the Homey release candidate version. As I’m running the Reolink app test version without any problems on advanced flows and person detection.

But yes, installing test/release candidate versions of any software are quite likely to produce bugs or unpredictable behaviour. That’s not the developers fault though, as that’s the whole reason for testing, to find bugs and issues.

Be kind, always.

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 26, 2026, 4:41pm UTC](https://community.homey.app/t/app-reolink/151761/131 "2026-04-26T16:41:35Z")

</div>

Hello all. I’m trying to connect my Reolink Video Doorbell PoE to Homey Pro (Early 2023), using the Reolink app. I (think) I have enabled the needed server settings but still I get “no device found”.

It works when I capture the stream in e.g VLC Player.

I would really appreciate some pointers if you have them.

 ![IMG_4579](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/0/f02cd69f4db3df2b6580cfc0af80d7f7e8e5d16b.png)

 ![search](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/8/18cda563d2c166aec54a3ca032c8afc3438f3229.jpeg)

 ![noDevFound](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3fc322447e8bfcdc69637d2ca6bb2fb7303d23e9.jpeg)

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 26, 2026, 5:14pm UTC](https://community.homey.app/t/app-reolink/151761/132 "2026-04-26T17:14:44Z")

</div>

> [@Drako74](#):
>
> It’s more likely to be a problem with the interaction between the Reolink test version and the Homey release candidate version

That’s exactly what I wrote 😄

Please be nice to everyone!

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 26, 2026, 5:15pm UTC](https://community.homey.app/t/app-reolink/151761/133 "2026-04-26T17:15:47Z")

</div>

Try manually entering the IP address on the switch.

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 26, 2026, 6:00pm UTC](https://community.homey.app/t/app-reolink/151761/135 "2026-04-26T18:00:21Z")

</div>

Yes, tried that, but with the same result.

---

<div class="post-metadata">

**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\
**Post date:** [April 26, 2026, 6:10pm UTC](https://community.homey.app/t/app-reolink/151761/136 "2026-04-26T18:10:00Z")

</div>

Is the base port 9000 configured?  
Are the ports open in the firewall?

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 26, 2026, 6:16pm UTC](https://community.homey.app/t/app-reolink/151761/137 "2026-04-26T18:16:35Z")

</div>

I have no limitations/rules defined on the routers firewall.

I might try now to temporarily disable the firewall and see what happens when trying to connect again.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [April 26, 2026, 6:18pm UTC](https://community.homey.app/t/app-reolink/151761/138 "2026-04-26T18:18:22Z")

</div>

> [@K-G\_Ohman](#):
>
> I might try now to temporarily disable the firewall

Don’t do that, it’s very risky to disable the firewall (especially on WAN side) since anyone can remotely access your devices with firewall disabled. It also won’t fix your LAN/local network issues, since firewall is usually for WAN only.

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 26, 2026, 6:20pm UTC](https://community.homey.app/t/app-reolink/151761/139 "2026-04-26T18:20:59Z")

</div>

I understand. I only did it for like 30s while trying with no firewall. Unfortunately it did not fix the problem. Still “No new devices found”. (firewall back on 🙂 )

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 27, 2026, 3:30pm UTC](https://community.homey.app/t/app-reolink/151761/140 "2026-04-27T15:30:31Z")

</div>

Anyone else that has experienced a similar problem? (And solved it…)

---

<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:** [April 27, 2026, 5:17pm UTC](https://community.homey.app/t/app-reolink/151761/141 "2026-04-27T17:17:24Z")

</div>

Can you connect directly to the camera from the ReoLink mobile app (iOS or Android, not the Homey app) and not through an NVR or Home Hub?

That uses similar connection method / ports as the Homey app.

Do you have VLANS on your network and/or different WiFi SSIDs for IoT devices, security cameras etc?

---

<div class="post-metadata">

**Author:** ![K-G\_Ohman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k-g_ohman/32/162633_2.png) [@K-G\_Ohman](https://community.homey.app/u/K-G_Ohman)\
**Post date:** [April 27, 2026, 5:30pm UTC](https://community.homey.app/t/app-reolink/151761/142 "2026-04-27T17:30:39Z")

</div>

Yes, the Reolink mobile app works perfectly.

No VLANS and it is PoE, hence Ethernet connection.

---

<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:** [April 27, 2026, 5:41pm UTC](https://community.homey.app/t/app-reolink/151761/143 "2026-04-27T17:41:25Z")

</div>

Is your Homey network cabled or WiFi?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [April 27, 2026, 6:12pm UTC](https://community.homey.app/t/app-reolink/151761/144 "2026-04-27T18:12:37Z")

</div>

> [@Drako74](#):
>
> That uses similar connection method / ports as the Homey app

I don’t think it does. The mobile app likely uses a P2P connection (like almost every other camera manufacturer). This allows you to view the camera remotely. Homey uses the direct IP/ONVIF/RTSP connection, which works differently. While I have no experience with Reolink products myself, I’m almost 100% certain that the mobile app uses a P2P connection instead of ONVIF (since P2P has been the default for remote video streams for years now, and every camera manufacturer that I know of uses it).

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

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