Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A Learn More
Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Hi,Currently, our camera only supports Google Home and Alexa. We have not been tested for compatibility with Homekit. But we will collect customers' needs and forward them to R&D team and let them arrange the plan in time!
Hi Cynthia,From the outside it appears that Reolink has some really talented hardware engineers but their software team is significantly under resourced.HomeKit was released 6 years ago and support isn't even on your development roadmap yet, I don't think it is realistic for your customers to expect it will ever be supported within the lifetime of the products they own.Given that your software still requires Flash which was deprecated in favour of HTML5 in 2014 and went EOL in 2017, I think you have other priorities that will consume your organisations software team bandwidth for the foreseeable future.I understand that HomeKit support does have some significant software/security requirements. Maybe rather than putting it off indefinitely you could investigate HomeBridge support which is much easier (should take <10min to setup in a lab) and will solve the problem for your customers who are motivated to integrate Reolink products into the apple ecosystem.While we are on the integration topic. Is there any way to reach the raw streams of cameras that are sitting behind a NVR?This needs to be possible in order to avoid having to purchase a second PoE switch to run the cameras. Maybe it would be possible to setup a simple port forward arrangement in the NVR NAT table.Eg if the NVR is on 10.0.0.2 each camera could be available on an incremental port;camera xx - rtsp://10.0.0.2:554xx/h264Preview_01_main
camera 01 - rtsp://10.0.0.2:55401/h264Preview_01_maincamera 02 - rtsp://10.0.0.2:55402/h264Preview_01_main """camera 16 - rtsp://10.0.0.2:55416/h264Preview_01_main
Hi all,Trying to bring my Reolink cameras into HomeKit via HomeBridge using the Homebridge Camera FFmpeg plugin. Unfortunately I can't seem to get the live video feed to work (stills work fine).According to the logs, HomeBridge is performing the video transcode but the HomeKit end devices just will not display the stream.I've tried both the RLC-410 and RLC-420 cameras without success.Has anyone got this working?If I disable libx264 transcoding and just pass the raw h.264 stream from the camera to HomeKit then it does work.My config is pretty default.
"name": "Camera FFmpeg", "interfaceName": "en0", "cameras": [ { "name": "Retreat", "model": "RLC-410", "serialNumber": "ec:71:db:e5:44:8b", "videoConfig": { "source": "-i rtsp://xxx:xxx@192.168.178.142:554/h264Preview_01_main", "stillImageSource": "-i http://192.168.178.142:80/cgi-bin/api.cgi?cmd=Snap&channel=0&user=xxx&password=xxx", "audio": true, "debug": true } } ], "platform": "Camera-ffmpeg"
Great work Daniel. I suppose it was somewhat intuitive when you think about it. The same process to pull a feed directly off a camera works to pull it off the NVR, just increment the number in the RTSP/HTTP URL to see each of the 16 cameras.In my case due to password authentication it's;rtsp://username:password@ip_addr_nvr:554/h264Preview_01_main... through to ...rtsp://username:password@ip_addr_nvr:554/h264Preview_16_mainAnd for static images;http://ip_addr_nvr:80/cgi-bin/api.cgi?cmd=Snap&channel=1&user=username&password=password... through to ...http://ip_addr_nvr:80/cgi-bin/api.cgi?cmd=Snap&channel=16&user=username&password=passwordJust remember to use the IP address, username and password of the NVR and not of the cameras.It would be great if the Reolink team would update their documentation to include instructions for access cameras directly and via the NVR so others don't have to go through this.
Hello, since it is a complicated task, our enginners need some time to to evaluate and implement it.Thank you in advance for your patience.
Don't worry, the feature already exists, it was just undocumented. Daniel managed to work it out.See https://reolink.com/topic/third-party-camera-feed-access-though-nvr/
Hi Cynthia,This solution will not work if the cameras are connected to the NVR.Would you like to try again.
Hi Cynthia,I think you missed the point of Daniel's post.He was interested in connecting to the camera feed via 3rd party software when it is connected into the NVR directly.That saves the need for a second PoE switch.As I mentioned above, it would require the NVR to map the ports through its NAT firewall.You mentioned in August that you were talking to your R&D team about this. Any progress?
Why not just pass the raw stream then? Any particular reason to transcode it?[/quote]If I don't transcode (add to the config "vcodec": "copy") then everything works but the camera dumps a 7Mbps steam that overloads the 3G/4G link to my mobile if I check the camera feed remotely. And yes I can configure the camera to output a lower res, compressed stream but I am also pulling this into an NVR to record and review later so I want that at full quality. I don't believe that there is anyway to ask the camera for a specific res stream.[quote quote=1060999]Also, have you tried capturing the live transcoded video and analyzing it? Chances are there may be something about the 264 stream that is either unusual that prevents a successful transcode using default settings, or the transcoding process itself is causing a malformation of the data in some way that is preventing Homekit devices from understanding it.[/quote]Yep, I haven't found a good way to do it and the issue is that any player (eg VLC) that I push the steam into is most likely to be more tolerant and will play what HomeKit can't so I doubt I will learn anything useful.The plugin seems to be working well for everyone else so begs the question, is there something broken about Reolink's h264 implementation.If you are interested, I'm also trying to debug this fault with the HomeBridge Camera FFmpeg plugin author over on GitHub.[quote quote=1060999]Also, if I'm not mistaken, the Reolink hardware utilizes some kind of ”watchdog” which monitors the live stream and ensures that frames are delivered within a certain tight time constraint. If the stream breaks this time constraint, I believe the stream is dropped and then re-established. It's possible that the transcoding process is taking up just enough time to exceed this time constraint, causing the stream to drop. [/quote]I can't speak to this as it's outside my understanding. I can confirm via tcpdump that the stream is pouring in, being transcoded and sent out again. It's just as though HomeKit isn't either receiving the stream or doesn't understand it.[quote quote=1060999]I'm all for finding a way to make it work with HomeKit. I know quite a few people that Reolink could pick up as customers if HomeKit compatibility could be established. As a side note, adorable cat.
Agreed and agreed.
You can always get the cameras into HomeKit with the HomeBridge plugin homebridge-camera-ffmpeg. Then you have all the controls and integration options that HomeKit offers.
Firmware files can be found off their main support page.https://support.reolink.com/hc/en-us/Specifically;https://support.reolink.com/hc/en-us/sections/360002374874-FirmwareYou will need to know what hardware version of each camera you have in order to know which firmware is appropriate.Log into the camera and look under Device Settings, System, System Information, Hardware Ver.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!