Hello - I have added Reolink RLC-520 camera using the latest Reolink package (1.0.20)
It says Device Unavailable / Connection lost while the device is perfectly working and has the latest firmware installed.
How can I check what’s wrong ?
note it is RLC-520 and not RLC-520A
A second issue: I have E1 Pro and it cannot be added.
Is it supported in stand alone or not ? (I have seen the E1 is not supported in stand alone)
How did you add it to the Reolink app? It doesn’t detect my E1 Pro (standalone), even with manually entered IP.
Same here. The E1 Pro lacks an http/https server. I guessume the app searches for http(s) servers at this moment.
I hope it can be recognised and added as Onvif cam in the future.
Hello Peter,
How did you add it to the Reolink app? It doesn’t detect my E1 Pro (standalone), even with manually entered IP.
just like the other cameras.
No, my E1 Pro has an HTTP server. I can enable it through the iPhone app and also through the desktop app.
Maybe I have a newer firmware or hardware version?
Awesome, so E1 Pro cams are sold with different options 
. I now see we own cams with different hardware versions:
Yours:
IPC_NT1NA45MP, build @ 20241212
Mine:
IPC_566SD54MP, build @ 20250708
only the IPC_ part is equal…
I was ‘not amused’ when I noticed my cam lacks a web server, but I found out too late to return it. However, it works with the Onvif cam app, albeit it can’t provide for motion-/snapshots 
Overview:
That’s what I was afraid of… I guess I got lucky. I didn’t pay special attention to that when I bought it. I just assumed it was standard.
Why was this app made official.
It’s been clear for weeks there are underlying bugs with multiple devices that still haven’t been addressed.
You’d really bug Athom here imho, not the kind developer making all of this happen.
Re RLC-520, the behaviour is very strange: I delete it and re add it. It works fine for 1 or 2 minutes and then become unavailable for ever.
Most Reolink cameras are supported in Homey, particularly the E Series (indoor cameras like E1, E1 Pro, E1 Zoom) and the RLC Series (outdoor PoE cameras). These models provide local access via RTSP and ONVIF, which enables reliable features such as snapshots, motion detection, and automations.
Some newer or battery-powered models, including parts of the Argus Series, Duo Series, and TrackMix Series, may require a Reolink Home Hub or NVR. These devices often do not expose full standalone APIs, so integration works through the hub rather than directly.
A smaller group of cameras, mainly 4G/LTE models and certain battery devices, are not supported. These rely on cloud-only communication and do not offer the local access required for Homey.
Can you retry and then send a diagnostic report?
Hello,
I have three RLC cameras on my network. All settings (RTSP, ONVIH, HTTPS) are activated. But the app does not find any camera.
They are all working on 192.168.1.10 to . 12. Should they use specific ports per protocol?
For instance, ports are:
Base service: 9001 - 9002 - 9003
RTMP: 1936 - 1937 - 1938
HTTP: 81 - 82 - 83
HTTPS: 444 - 445 - 446
RSTP: 555 - 556 - 557
ONVIF: 8001 - 8002 - 8003
Can you help me?
You might want to start by changing all those port numbers you have changed back to their original defaults of 9000, 1935, 80, 443, 554 and 8000.
The port numbers on each camera can be the same. It is only the IP address of each camera that needs to be different. Although personally I would suggest different username/password combinations for each camera too, for extra security.
@Aeroben I’ve discovered this Reolink app solely looks for the default Onvif port number 8000 atm.
And most probably the app also looks for HTTP(S) and RTSP @ their default ports.
Not sure if the RSTP protocol is camera related (at all).
.
I agree on the solid advice by @Drako74
The E1 Pro should be supported when updated with firmware 21.06
A new version is available here: Reolink | Homey
v1.0.22
Improvement: Improve codec logging
Bugfix: PTZ feature detection for battery devices
Bugfix: Doorbell abilities mismatch that results in missing cards and motion detection
Bugfix: Steam codec and rely on H.254 on substream for all devices
The siren on the Reolink CX820 behaves differently from models like the Reolink E1 Pro. On the E1 Pro the API exposes a usable siren trigger, but on the CX820 thats not available.
Thanks for the explanation! Maybe there will be a firmware update for the camera someday.
Hi @Koktail ,
The latest update appears to have fixed my issue with viewing my streams in Homey, thanks!
Now I can see them , they are appear to be the sub stream rather than the main, high quality, feed. Is there a reason why I can’t view the stream in full quality or is this by design? If so, can we look to add a feature to switch between stream qualities?
Thanks.
Edit: Actually, it didn’t fix the issue - getting myself confused with what is working on what device! Is there anything I can do to assist in diagnosing the issue?
Everything worked perfectly up to version 1.0.20. From version 1.0.21 onwards, no notifications are being sent to Homey.
The Reolink app on my phone detects movement. But this detection isn’t reaching Homey. Therefore, no flows can be triggered. If I manually start the flow in Homey, it works. I haven’t changed anything in the last few weeks. No port, no flow, no IP address. Nothing. Are others experiencing this problem?
No, everything is working as usual for me. However, I have version 1.0.23. Have you tried restarting it yet?
