MQTT and or Webhook Support for Home Automation
-
Hi Reolink,
I love using your cameras and NVR but the one thing it's really missing when using with a Home Automation platforms is MQTT and or Webhook support. I plan to stick with your system especially given AI is now on it's way but I'd really like to setup automations with this I am currently doing with this workarounds. Anyways please pass this to your team I am sure many others would appreciate this feature. -
Neolink has a pull request that adds MQTT support for Reolink cameras.
https://[censored]/thirtythreeforty/neolink/pull/78 -
Looks like that only supports Reolink camera that doesn't support RTSP natively so no good to me. Id also like MQTT or webhooks from the Reolink NVR without needing to run anything further.
-
Thank you for your suggestions. We will forward your feedback to the R&D team and help them make improvements in the future.
-
hello,
i am here because i was looking exact same thing, mqqt or webhooks for my new nvr 16ch. so it will be easy to interact with domotics systèm.
right now i am trying to real time parse ftpserver log to know when motion sensor has been triggered... it is not very user friendly.
thanks to add my vote !5View 3 replies-
Hi Reolink - I also came here for MQTT support.
MQTT is such a centralpiece for home automation, its support is hugely important to me.
Do you have this planned with your development team ?
Thank you Reolink -
@user_619401890463775_619401890463775
Hi there, now we don't have the plan for MQTT. If there is any news, I will let you know. -
@reolink-fiona this sucks. It's much easier to implement MQTT than an entirely new API that uses webhooks. Then other people still have to update their apps to support your new API. With MQTT your camera becomes compatible with a ton of home automation stuff already out there (HA, Blueiris etc). Most of your cameras are targeted toward advanced users (The average person doesn't even know what POE is, they just buy a Nest or Wyze).
It would be nice if we could use our cameras how we want and MQTT allows that. I guess we can all go and request it here: https://community.reolink.com/topic/4308/get-to-know-your-customers-day-tell-us-what-you-want and maybe someone will listen to us
-
@aleleu62_232174521270407 Interesting, I came here to share my similar solution. Though I'm using inotify-tools rather than FTP logs to get an instant trigger. I'll share below:
I came up with a solution on my own - setting Reolink up to FTP images to a Linux server on my local network, which uses inotifywait (from inotify-tools) watching for close_write (FTP user finished writing new file) to instantly trigger a curl command to send the image to the service of my choice (locally running NTFY.sh server, but this could also be to a webhook receiver anywhere on the web). This lets me have a feed of event snapshots to my computers, using the NTFY.sh website subscribed to my local server. It works great - it reacts just as fast as the Reolink android app which uses Google's notification network. Hopefully this gives enough hints to folks wanting to build their own thing.
As you can see from my solution, all I really wanted was rich notifications (images included) on my desktop computers. NTFY.sh can also run on Android, so this approach would also work for that, too. The only thing I'm missing is knowing WHY the event was triggered - the Reolink FTP filenames just include the camera number, not whether it was a person, motion, vehicle, or pet being detected, so that cannot be exposed via this flow. If you need that for your use case, this won't work for you.
I would most like having the ability to run any CURL command desired, and surface as many fields as possible as Linux bash variables, so they could be included - ie, camera name, reason for the triggger (motion, vehicle, person, visitor (someone rung doorbell), pet, etc), image, etc. -
@user_804514214613241_804514214613241 Yes, this is another method to have rich notification. However, this requires Linux knowledge. Most people opted for pushover which is quicker to implement.
-
