Reolink Video Doorbell PoE
MattEng0 opened this issue · 41 comments
Morning,
Just received my preordered Doorbell today and I am looking to see, with my limited knowledge, how I can help out making it fully functional with this integration.
The integration itself gets successfully added and the following entities work/have issues:
The camera entity loads a still but does not playback
The FTP switch works
IR switch works
Last Event sensor works
Motion/Person/Pet/Vehicle come up as unavailable
Push notifications switch doesn’t work
Audio switch works
Recording switch works
Siren switch works
Spotlight switch is made - don’t think this is a feature
The main thing that isn’t created is the “Visitor” notification event when the doorbell button is pressed. This would be a main source of automation and I would be keen to help with for both myself and everyone else.
Let me know how or if I can help.
This problem was mentioned in latest reviews of doorbell cameras, here's the 20s clip from the full video: https://youtube.com/clip/Ugkxo6NJURvJD53gU21ER4ao96HiUb96Yi7D
I wanted to buy the reolink doorbell, but I first wanted to make sure it will actually be fully supported by @fwestenberg.
Doorbell button press will be a must have in this integration, IMHO. It will certainly be hugely useful toward the very reason this Reolink integration exists in the first place… Home Automation! 👍🏻👍🏻
I’ll live with no button press integration for a while, but am hoping it’s a simple and fast update!!!
I've come across a ready made solution to the problem as a fork of this development.
The above link has already solved the issue of the Visitor function and a few other tweaks. Worth a look and I have switched to it.
Might help with this development with the solutions used.
The above link has already solved the issue of the Visitor function and a few other tweaks. Worth a look and I have switched to it.
Thank you so much for this info.
Unfortunately not a complete fix and we will be needing to wait for a response from Reolink.
The ONVIF for the button press (Visitor notification) doesn’t seem to have been included in the POE doorbell firmware (which it is on the Wi-Fi version).
I have messaged support about providing a firmware update to include this which hopefully they can, as it already is with the Wi-Fi version.
Thank you, MattEng0… does the referenced cctv integration only apply to Reolink branded NVRs though?
If you mean that it only works with NVRs, no. It is a fork of this integration with additional features/tweaks.
In addition to that we have had a response from Reolink and they have provided the required firmware to allow for the required ONVIF changes which means we can now detect the button being pressed on both the Wi-Fi and POE version.
The thread with the resolved issue is here Doorbell Dings are not detected - POE Doorbell Only
And the new firmware is being hosted across these two links thanks to @skynet01
POE version: 1459_22102808
Wi-Fi version: 1459_22102806
I will create a thread on Reolink and HomeAssistant community forums as a notification for everyone to hopefully make it easier.
Posts completed on both HomeAssistant Community and Reolink Community.
Posts completed on both HomeAssistant Community and Reolink Community.
Great job Matt. Thanks.
The other plugin did not work for me, could never connect to the doorbell, yes i removed this one, waited an hour, rebooted the doorbell and HomeAssistant.
Returning to this one and hoping its updated and keeping an eye on the other one.
Start an issue on the other integration, but I came across that issue too. Make sure you have the options enabled in my posts on Home Assistant and Reolink community forums.
Otherwise the way I fixed it was once I inputted the information at setup I restarted home assistant and it connected correctly.
Well I deleted everything reolink related and went to watch a movie, installed the other addon again and bingo everything worked now :) tomorrow will try to make one of those rich notifications when the button is pressed.
There are a few blueprints in HA forum that do it for you. Just search for camera notifications
I understand correct, with this (fwestenberg) there is actual no funktion of the ring button?
Remove the old reolink integration
Install this new one
https://github.com/JimStar/reolink_cctv
If if doesn't connect to the cameras/doorbell wait 1-2 hours and try again.
OK… so I went through everything, and all things work for the doorbell! But I’m having a Home Assistant issue with video, and I wonder if others are having it or not. In the former Reolink integration, I had always and forever just used the picture entity card to display camera pictures, and then just tapping through that “cover” picture that refreshes every ten seconds, in order to see actual video.
Now, switching to the JimStar integration so I can use the doorbell button, everything looks and feels the same, but when I tap through the picture for any camera I have, video never starts.
Everything else on the doorbell works, and I know video itself is fine, because I can access through the Reolink app. But HA is no longer showing as it used to. One think from the former integration, was that I could have sworn there was a buffer/no buffer check box in the config of the picture entity card. I don’t see anything like that in this now. Maybe that’s new in Lovelace though, having nothing to do with the new Reolink integration.
Anyone else having same/similar issue, or have any ideas on where I may have not done something quite right?
I dont have any issues. Try switching to RTSP stream instead of RTMP, also use 264 and not 265. Make sure all ports are enabled in the network settings of your camera. You can make playback smoother by using WebRTC integration in HA
Please direct me if this post is in the wrong place as I am new to posting on this site. Just received my Reolink wifi doorbell. No install problems. Integration install had no issues, camera was added first time. I am able to view the video in HA, but it appears the visitor function is not working. My DB firmware version is the latest and matches the wifi version listed above. The HA DB device shows visitor function "OFF" and does not show any other "ON" activities despite multiple button pushes. Naturally my automation does not show that it has run. I feel I must have missed something in my setup/config to get the button push to trigger visitor on. I would appreciate any suggestions and thank you for developing this integration.
Please direct me if this post is in the wrong place as I am new to posting on this site. Just received my Reolink wifi doorbell. No install problems. Integration install had no issues, camera was added first time. I am able to view the video in HA, but it appears the visitor function is not working. My DB firmware version is the latest and matches the wifi version listed above. The HA DB device shows visitor function "OFF" and does not show any other "ON" activities despite multiple button pushes. Naturally my automation does not show that it has run. I feel I must have missed something in my setup/config to get the button push to trigger visitor on. I would appreciate any suggestions and thank you for developing this integration.
This one works with the visitor sensor. You have to delete the other reolink integration and add the new one. It can take more than a hour for you to able to add the doorbell/cameras. So be patient :)
https://github.com/JimStar/reolink_cctv
Thanks for the reply. I am using the Jim Star integration. The visitor sensor shows up in entities, it just won't change to on when the DB doorbell is pressed. The _dev integration is not on my HA. I removed it from HA and HACS and restarted before installing the _cctv. UPDATE: just installed the new Reolink PC client. Under network settings I found the ports. ONVIF is there with port 8000, but I cannot change the toggle switch for it to the ON position.
If you have a Poe doorbell you have to update to the latest firmware for visitor sensor to work. There is a link to it in Jimstars repo in a bug report if you search for “Poe doorbell” under closed issues
I'm sorry to repeat what other ppl already said, but i just got my POE doorbell and i'm noticing that the visitors sensors ain't doing jack in HA, and it was delivered WITH the "fixed" firmware, i even tried to re-update it with the firmware found in this thread just to be really really be sure that's not the problem and got this so pretty sure i'm covered there: "Upgrade Failed
Failed to upgrade as the selected package is identical with the current version. Please try again."
there are actually 3 things that do not seem to work in HA that DO work via the reolink app(android) and that's:
- person detection (never changes state from clear)
- motion (never changes state from clear)
- visitors (it's always off)
Just trying to get some help here, i saw someone that started a new thread over at jim's and got it closed ans was told to take a look at all the other threads about it, i've been doing that for hours and i'm still nowhere closer to a solution -.-
I'll attach a debug with redacted domain name, i feel the debug gives out too much private information regarding stuff like that.
My scenario exactly, except I have the Wifi version. I am 99% certain onvif is not active on my DB. Using synology surveillance station, I can manually add the cam as onvif by inputting the IP but not see anything. All other onvif cams are auto discovered. Followed this Reolink process (https://support.reolink.com/hc/en-us/articles/900000655446-How-to-Add-Reolink-Cameras-to-Onvif-Device-Manager). The onvif device manager did not see the DB. I could add the camera manually but do nothing with it. I believe port 8000 is open and answering, but that is the extent.
This is a screenshot from the new Reolink PC client. As you can see, ONVIF port is 8000, not "on" and I cannot set it to "on".
I can see some kind of event log via onvif device manager and it would seem that visitor attribete checks out fine, but what do i know really... :)
If you have a Poe doorbell you have to update to the latest firmware for visitor sensor to work. There is a link to it in Jimstars repo in a bug report if you search for “Poe doorbell” under closed issues
My doorbell already came with the latest firmware (at least the one they are referring to - the one that had the google drive link which has now been taken down). The visitor button is still not working in HA. Some have suggested to NOT plug in the doorbell directly to the NVR and just plug into the router, but that does not work either. I can get the video feed in HA, but I ring the doorbell and nothing. Person detection/Motion doesn't work either but I read that you have to plug the doorbell into port 1 on your NVR for that to work. Getting the doorbell press in HA is really what I'm after.
I was able to figure it out.
First you need to connect the camera to your router directly and not directly to the NVR. You then need to find the IP Address of the doorbell camera given by your router which you can find under the leases section in your router. Then you need to connect to the doorbell from a browser from your LAN. Online it says to put a port 9000 on it, but you just put in the IP Address: http://192.168.1.127 - in my case). The password is blank. You need to change the password, so you can use it to connect in Home Assistant.
Now in Home Assistant, you need to go into the integrations and Reolink and connect to the host of the IP Address of the video doorbell (in my case it was 192.168.1.127) NOT the IP Address of the NVR (In my case it was 192.168.1.188).
Once you do that, now the Visitor status and motion detection will update in HA.
I'm sorry to repeat what other ppl already said, but i just got my POE doorbell and i'm noticing that the visitors sensors ain't doing jack in HA, and it was delivered WITH the "fixed" firmware, i even tried to re-update it with the firmware found in this thread just to be really really be sure that's not the problem and got this so pretty sure i'm covered there: "Upgrade Failed Failed to upgrade as the selected package is identical with the current version. Please try again."
there are actually 3 things that do not seem to work in HA that DO work via the reolink app(android) and that's:
- person detection (never changes state from clear)
- motion (never changes state from clear)
- visitors (it's always off)
Just trying to get some help here, i saw someone that started a new thread over at jim's and got it closed ans was told to take a look at all the other threads about it, i've been doing that for hours and i'm still nowhere closer to a solution -.-
I'll attach a debug with redacted domain name, i feel the debug gives out too much private information regarding stuff like that.
Do you have your POE doorbell plugged into the NVR directly? See my replies above. I had the same issue.
I don't have an NVR so yes, it's just a standalone unit in my lan, i did do what you wrote above.
Wh
This is a screenshot from the new Reolink PC client. As you can see, ONVIF port is 8000, not "on" and I cannot set it to "on".
Hey Gator, enable RTSP and that will enable ONVIF
Weirdly enough, my HA was working with ONVIF turned off on the camera.
gurkburk76,
What home assistant version do you have? JimStar says he hasn't tested in older versions: "I tested this component with Home assistant 2022.8.6. Not sure if it would work with a lot older one..."
Mine is 2022.10.4
Running the latest atm, Home Assistant 2022.12.6
I did however read this that would partially explain why the movement sensors don't work as i access HA via HTTPS even internally, perhaps it also affects the visitor sensor?
"For the motion detection to work, Home Assistant must be reachable via http from your local network. So when using https internally, motion detection will not work at this moment."
from https://github.com/JimStar/reolink_cctv
Conundrum, Thanks. I did not catch that. Turned it on. Executed doorbell push - nothing. Checked HA logs, nothing. Checked my automation trace - nothing. I am running HA on a synology using docker. I will check for a later version and post findings.
I am running through HTTPS and my motion sensor is working, so maybe that was fixed in his new version? I noticed it was updated twice in the last couple days.
Gator, what does your network info look like from the web connected to your camera? Don't send the mac address of your camera. You want to make sure your ip address of the camera is on the same network as your router.
Conundrum, thanks for the quick reply and input. The camera is working fine with the Reolink apps (pc and android). I am trying to get the doorbell push to trigger the visitor entity in HA so I can do some automation. No luck there. I just downloaded and checked latest synology docker version of HA. Now on 2022.12.6. Tested doorbell push with no luck. BUT, after doing your suggestion, I was able to turn on RTSP and ONVIF. However, neither synology surveillance station nor the onvif device manager can access the DB using onvif. Surveillance Station automatically sees the Hikvision cams that support onvif. Onvif device manager also auto sees the Hikvisions as well as the Surveillance Station (nvr software for synology) since it supports onvif. BTW I rebooted the Reolink just in case it needed to start the RTSP and onvif...no luck.
So i finally got some time to rearrange stuff and run HA on htt pand port 80 and the sensors work, did not work with http and port 8123. Also running pfsense with haproxy so i had to fiddle with that and some other allow proxy things. Pretty shitty that it dosen't work with https but that's on reolink i guess -.-
What are the substream resolution options for this camera?
Any followup on this? I can't seem to get it to work with this integration.
Use the official integration on the latest HA version.
Use the official integration on the latest HA version.
Running 2023.2.2, but I don't have a working visitor button there.
Nor can I enable alarm/siren or spotlight on my RLC-811A, but I'll try some more
edit:
After reading a few more threads it became clear to me. I am running both internally and externally on https. The webhooks of Reolink cannot send over https. I have changed this and now it works. Thanks for your reply.