Hmm okay normal stream is not possible then ?
That depends on the codec used by the camera and the capabilities of the display device.
thanks for the quick respons as always!
i wil first focus on the Hikvision camera’s becaus that is something we have in commen.
i already set the codec to h264 a few days ago and from that moment on i can see the live video on my phone.
i wil try to change for the hikvision to the substream but where can i find the richt rtsp adres to use?i already did quick look on the camera settings but i could not find it in a few min.
You could try rtsp://192.168.1.208:554/Streaming/Channels/102 to select the substream.
thanks, i think i did it the right way.
it stil only works on my phone. i tried al codec types who are avalible but it is not working.
i don’t want to waste more of youre and my time so i wil leave it for as is for now.
and who now there wil be in the future other users wo wil figure it out and share what the problem is.
@Adrian_Rockall my love streams not working anymore ? Can hear sound but no video ?
Unfortunately, that’s out of my control as the app just passes the RTSP url to the display device. Maybe contact Athom to see if they can shed any light.
You might have some luck if you enter the URL for the sub stream.
But it was working fine …. No problem the ring app live virus is working fine
I haven’t updated the ONVIF app since Nov 19, 2025, so it is probably an updated to the Homey app that has broken it. You could try rebooting everything to see if one of the devices has got in a muddle.
Goodmorning,
I have 3 reolink camera’s and they used to work fine with this great ONVIF app.
I stil can see the live image with the relolink ap on my notebook.
I dubbelchecked the username and password, they are correct.
No video in Homey.
Can you please check this log and tell me where to look to solve this?
The error in the log is: connect ECONNREFUSED
THX!
Log ID: 2026-03-05T09:36:53.824Z
App version 2.0.60
9:36:53.824: Connect to camera error (Terras Camera 192.168.1.201): connect ECONNREFUSED 192.168.1.201:8000
9:36:53.844: Connect to camera error (Tuinhuis camera 192.168.1.202): connect ECONNREFUSED 192.168.1.202:8000
9:39:45.529: --------------------------
9:39:45.530: Connect to Camera 192.168.1.202:8000 - admin
9:39:45.548: Request error (192.168.1.202): connect ECONNREFUSED 192.168.1.202:8000
9:39:45.549: Connect to camera error (Tuinhuis camera 192.168.1.202): connect ECONNREFUSED 192.168.1.202:8000
9:39:55.591: --------------------------
9:39:55.592: Connect to Camera 192.168.1.201:8000 - admin
9:39:55.596:
_request (192.168.1.201): {
“hostname”: “192.168.1.201”,
“port”: 8000,
“path”: “/onvif/device_service”,
“agent”: false,
“timeout”: 15000,
“headers”: {
“Content-Type”: “application/soap+xml; charset: utf-8; action=“http://www.onvif.org/ver10/device/wsdl/GetSystemDateAndTime\””,
“Content-Length”: 261,
“charset”: “utf-8”
},
“method”: “POST”
}
<s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope”><s:Body xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=“http://www.w3.org/2001/XMLSchema”></s:Body></s:Envelope>
9:39:55.609: Request error (192.168.1.201): connect ECONNREFUSED 192.168.1.201:8000
9:39:55.611: Connect to camera error (Terras Camera 192.168.1.201): connect ECONNREFUSED 192.168.1.201:8000
9:39:55.613: --------------------------
9:39:55.614: Connect to Camera 192.168.1.202:8000 - admin
9:39:55.619:
_request (192.168.1.202): {
“hostname”: “192.168.1.202”,
“port”: 8000,
“path”: “/onvif/device_service”,
“agent”: false,
“timeout”: 15000,
“headers”: {
“Content-Type”: “application/soap+xml; charset: utf-8; action=“http://www.onvif.org/ver10/device/wsdl/GetSystemDateAndTime\””,
“Content-Length”: 261,
“charset”: “utf-8”
},
“method”: “POST”
}
<s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope”><s:Body xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=“http://www.w3.org/2001/XMLSchema”></s:Body></s:Envelope>
9:39:55.633: Request error (192.168.1.202): connect ECONNREFUSED 192.168.1.202:8000
9:39:55.635: Connect to camera error (Tuinhuis camera 192.168.1.202): connect ECONNREFUSED 192.168.1.202:8000
ErrorCONNectionREFUSED
meaning: the cam refuses to connect.
Check the used credentials again (i.e. hidden whitespacrs, unallowed characters, lowercase letter(s) changed into capitals caused by autocorrect)
When you’ve different subnets / vLANs, make sure both Homey and cam can connect properly, by checking / adjusting firewall.
.
Make sure port 8000 is still the configured Onvif port.
Hi Peter,
I have checke all, username and pass are ok.
Using port 8000, as you can see in the logging.
They are all in the same network/vlan.
It used to work…
Strange.
The Onvif app is supposed to connect at port 8000; What you should check is, is it still set to port 8000 in the cam settings, just to make sure and to rule things out
If you are certain the credentials are OK, then the only suggestion I have is to reboot everything.
Yesssss, you are the Hero of the day!!!
Onvif was not even enabled in the server settings!
It used to work, might me disabled by a firmware update.
THX!!!
how can i see if i put in the right substreem RTSP?
wil the app give a malfunction if i put in the wrong one?
ore just no image?
ore wil it just keep using the mainstream if i make a typo?
It might show an error or no stream. It won’t automatically fall back to the old one.
is there anyway to get a conformation that the substream work?
i did try a wrong rtsp addres on purpose but the stream wil stil show up.
i realy like to be sure that i use the substream to rule out thinks why the camera’s are not working on my tablet app but do work on my phone app.
if i use a general onvif app from the play store the my tabelt can play the camera. but not at the homey app.
i also did try the homey hikvison app but there i get a error even on my phone.
Good morning. Since this morning, my Reolink TrackFlex, which I configured via ONVIF, has lost its connection. I haven’t changed the IP address or ports for weeks, nor have I modified anything else. Is there a problem with the app?
I haven’t changed the app for a long time, so it’s unlikely to be an issue with the app.
