# \[APP\]\[Pro\] Support for ONVIF compatible cameras (Release 2.0.70, Test 2.0.70)

**URL:** <https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377>\
**Category:** Apps\
**Created:** [April 14, 2020, 4:57pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377 "2020-04-14T16:57:37Z")\
**Posts on this page:** 20\
**Page:** 93

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [September 30, 2025, 8:25am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1866 "2025-09-30T08:25:38Z")

</div>

I will add an option to override the RTSP url in the next update.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [September 30, 2025, 8:32am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1867 "2025-09-30T08:32:32Z")

</div>

As @robertklep mentioned, the stream might be using a codec that’s not supported by the Homey app.

One of my cameras was set to use H265 (I think from memory), so I had to change that to H264 and then it works (hope I got those numbers correct).

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 30, 2025, 8:55am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1868 "2025-09-30T08:55:32Z")

</div>

Sounds right, I was expecting as well that the camera using H.265 might cause this issue.

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 30, 2025, 10:15am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1869 "2025-09-30T10:15:52Z")

</div>

Hi Robert,

First attempt failed with this error:

 ![Scherm­afbeelding 2025-09-30 om 12.12.42](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/2/c24f939be78a75b5b38999105171abb8853aed2c.png)

Than I tried exactly the same again (opening the url with Chrome browser, than being suggested opening the stream with VLC) and this time I was asked to enter credentials and… the stream showed up!

This is the screenshot:

 ![Scherm­afbeelding 2025-09-30 om 12.12.04](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a68388629fe534bce767f8625c7ed3f719f0ac91.jpeg)

Unfortunately, trying the same again after a few minutes gives:

 ![Scherm­afbeelding 2025-09-30 om 12.28.50](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/1/1150c94c65a3e6d7108eba9d95bcd2216155949b.png)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 30, 2025, 10:30am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1870 "2025-09-30T10:30:06Z")

</div>

The Homey app is able to play my Reolink doorbell stream if I return the RTSP URL in a test app like this: `rtsp://username:password@AA.BB.CC.DD:554`

@Eternity you don’t use separate VLAN’s or guest/IoT networks that may cause this issue?

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 30, 2025, 11:30am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1871 "2025-09-30T11:30:50Z")

</div>

> [@robertklep](#):
>
> rtsp://username:password@AA.BB.CC.DD:554

That works fine! If I enter my details and copy the URL in Chrome, it suggests starting VLC and the stream shows instantly!

All wifi devices are on the same LAN. I do run Pi-Hole, but switch that off during testing.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [September 30, 2025, 2:31pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1872 "2025-09-30T14:31:03Z")

</div>

@robertklep Could you try adding `/Preview_01_main` to the end of the url in you test app?

That is being returned by ONVIF so the URL that Eternity is using will be:

rtsp://user:password@192.168.50.8:554/Preview\_01\_main

According to Reolinks information that should be OK, but maybe it’s the issue.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 30, 2025, 2:38pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1873 "2025-09-30T14:38:19Z")

</div>

Works fine like that as well.

This is the code that I’m using:

```auto
const video = await this.homey.videos.createVideoRTSP({});
const videoWithURL = video.registerVideoUrlListener(() => {
  return { url : 'rtsp://username:password@AA.BB.CC.DD:554/Preview_01_main' };
});
await this.setCameraVideo(VIDEO_ID, 'Camera Voordeur', videoWithURL);

```

Are you URL-encoding username/password?

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 30, 2025, 2:53pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1874 "2025-09-30T14:53:42Z")

</div>

> [@Adrian\_Rockall](#):
>
> rtsp://user:password@192.168.50.8:554/Preview\_01\_main

I tried that with my credentials

in Chrome, and VLC opened the stream

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [September 30, 2025, 3:13pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1875 "2025-09-30T15:13:00Z")

</div>

I don’t think I am encoding them, I just inject them into the URL returned by ONVIF, so maybe that’s it. It works OK for me but maybe my credentials are URL friendly.

I will investigate that when I get home.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [September 30, 2025, 9:30pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1876 "2025-09-30T21:30:20Z")

</div>

I have published a new test version.

This version URL encodes the username and password before adding to the RTSP URL to allow for special characters.

Added an Advanced option to specify a custom RTSP URL.

@Eternity and @Youri_Pasternak could you check if these changes fix your issues?

---

<div class="post-metadata">

**Author:** ![Youri\_Pasternak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/youri_pasternak/32/55754_2.png) [@Youri\_Pasternak](https://community.homey.app/u/Youri_Pasternak)\
**Post date:** [October 1, 2025, 5:27am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1877 "2025-10-01T05:27:15Z")

</div>

thank you Adrian for adding the custom RTSP URL option, it works great now!

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [October 1, 2025, 8:24am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1878 "2025-10-01T08:24:40Z")

</div>

> [@Adrian\_Rockall](#):
>
> @Eternity and @Youri_Pasternak could you check if these changes fix your issues?

Working now @Adrian_Rockall. It must have been my quirky password!

Thanks!

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [October 1, 2025, 10:12am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1879 "2025-10-01T10:12:25Z")

</div>

Great, and thanks to @robertklep for the suggestion.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 1, 2025, 11:04am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1880 "2025-10-01T11:04:52Z")

</div>

Hi Adrian,

What crossed my mind: To prevent Homey users, using pre-2023 models, from posting “streamdoesntwork,why” , I’d suggest to add something like “Streaming is unavailable for pre-2023 models” to these Live Stream tooltips or descriptions:

 ![Screenshot_20251001_124811_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/9/e9e11b6e3a39565b1af2704153e11e1f89e46796.jpeg)

I’m not a fan of filtering these fields for the ‘older’ Homey models, it’s nice to have the RTSP URL available for use in other applications.

---

<div class="post-metadata">

**Author:** ![Xa4](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xa4/32/11450_2.png) [@Xa4](https://community.homey.app/u/Xa4)\
**Post date:** [October 1, 2025, 7:28pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1881 "2025-10-01T19:28:21Z")

</div>

Also in the new version I’ll get the same result. Socket hang up. VLC is working fine.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [October 1, 2025, 8:25pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1882 "2025-10-01T20:25:26Z")

</div>

If you enter the camera IP address into Chrome, does it show anything?

The errors in the log you sent are specific to RTSP, they look more like general ONVIF issues. Have you enabled ONVIF on the cameras?

---

<div class="post-metadata">

**Author:** ![Astrapowerrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/astrapowerrr/32/78916_2.png) [@Astrapowerrr](https://community.homey.app/u/Astrapowerrr)\
**Post date:** [October 2, 2025, 9:07am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1883 "2025-10-02T09:07:38Z")

</div>

cant find it on the forum but is it possible to send the stream as a notification.  
I would like that when doorbell is pressed i can see that live stream who is in front of my door.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [October 2, 2025, 9:25am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1884 "2025-10-02T09:25:36Z")

</div>

I very much doubt this will be available, but I am sometimes wrong.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 2, 2025, 9:31am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1885 "2025-10-02T09:31:13Z")

</div>

That would require an MJPEG stream to be available (at least on iOS), which means using some sort of transcoder.

[Previous page](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377.md?page=92)

[Next page](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377.md?page=94)