Best posts made by Matt English_257716806459606

Evening guys,

Well I have received my new POE doorbell and if works perfectly save for two things which I hope will have been sorted with HomeAssistant. Due to going for the POE for stability in my network setup I have had to forgo the option of receiving "Rich" Notifications. I hoped to solve this with HomeAssistant and the automation that it allows for me to fill that gap. This lead me to search for the specific Integration that would allow this and I came across a fork of the main one available in the HACS addon by JimStar

Whilst this had to functionality sorted with the ONVIF notifications, the current firmware publicly available for POE did not have the notification for "Visitor" added to the notification XML. Thankfully myself and another user (shout out to skynet01 on Github) messaged support about this and they thankfully have sent us an up to date firmware for both Wi-Fi and POE which resolves this functionality. This means that notifications can be set up off the button press of the doorbell now.

Until this is released to the general public (or if someone from Reolink support can add it here or officially) skynet01 has it hosted on Google Drive which will be linked below.

POE version: 1459_22102808: (https://drive.google.com/file/d/1WH6tef5x4RfH9WcHQrxWWOadN049UjFH/view?usp=sharing)
Wifi version: 1459_22102806: (https://drive.google.com/file/d/1WKDSj5dQX8ApbAMwzCwVI7g05dGGiusj/view?usp=sharing)
(if this isn't allowed please let me know)

After upgrading the firmware it has been advised by support to go to "Settings>Network settings>Advanced>Port settings" to check and enable the ports first.


After that install the HACS integration by JimStar and you will be able to add the respective automations for snapshots etc to allow your own version of "Rich" notifications. I won't go into how to here as there are multiple ways to do this and each personal to your own circumstance but this gives you complete local control of your Doorbell.

Again big thanks to JimStar for the integration fork, to skynet01 for hosting the firmware until Reolink gets it pushed publicly and to Support for getting this sorted very quick for us.

This link to the resolved issue and further details as to why this was needed is as follows: https://[censored]/JimStar/reolink_cctv/issues/49

*Edit* Links Updated and a link to the original GitHub issue