I spent a week trying to get my ReoLink E1 Pro into HA. I want to use it with Frigate. I found an instruction to load go2rtc and put the cameras in there, then bring them into Frigate.
What I discovered:
By default, rtsp and onvif are turned OFF. Not knowing this, I tried 100s of different urls which never were going to connect. I could not find where to enable this in the phone app so downloaded the reolink app to my Mac. In there, go to the camera > settings > Network > advanced > server settings and there are the check boxes. tick rtsp which then allows the tick on onvif. Click save.
I also went into the camera > system > user management and made a different admin account to use to connect HA to my cameras. I went with Admin4 but will probably change it to something more random and longer. Long Random username and long random password makes brute force guessing a little harder.
Now that rtsp/onvif are enabled, my instructions to use Frigate in HA included loading go2rtc. In the config for go2rtc, I name the camera and I put in this line onvif://Admin4:[email protected]:8000?subtype=001 with your actual name/password/IP address. subtype 0 is low res stream, 1 is hires stream.
next telling frigate the name of the cameras in go2rtc and setting up their configurations.
Another troubleshooting hint for us noobs is learning that spaces mean something in Yaml so making a config and branching the settings with spaces (not tabs) makes things work better.
Another bug I found in reolink on the macOS is when the IP address changes, restart the app. I change the IP during setup and once I have it right, it wonât matter when in production as it wonât change.
I was also successful in blocking the camera from the internet in my router while still feeding my phone (local ip only) and HA server (also local ip) and setting my router to be a NTP server. To change the NTP, go into each camera > settings > network > advanced > NTP settings and pick âotherâ in the drop down. I put in my router IP address and now it gets the updated time. Blocking the internet also means manual firmware updates but these new cameras out of the box did not detect a new firmware online when there really was one (1/10/2024) do downloaded it from reolink and applied.
If you have the reolink integration installed, it will often discover the e1 pro, but as @afsy_d said, it wonât work when you try to actually add it to ha. i think itâs related to the proprietary protocol reolink uses for rtsp/onvif. The frigate approach outlined by @darkknyght above is an alternative way to integrate the e1 pro. another is neolink
can someone go into detail on how to add a user for this camera?i have 2 cameras, a reolink doorbell and a E1 pro. i had the doorbell first and i was able to go into device settings â advanced â user management and create a new user. the E1 pro does not have user management and all i can find is âshareâ so i canât seem to add the same user that i use for my doorbell to the E1 pro. i donât know what to do
I know its late in the game, but did you ever get an answer for this?
For my E1 Pro, I had to use the Reolink application on the phone, and could set an additional username/password in the Advanced/User management portion, when accessing the camera.
I had a wrong character in my password, so I went searching for answers. Turns out I was commenting out the rest of the connect string. Pretty silly. (how I found this thread)
Once rtsp, etc, is enabled the camera is accessible by anything accessing the connect string. path: rtsp://admin:[email protected]:554/h264Preview_01_sub
On the mobile app, I found a place to generate authorization tokens with instructions to âCopy this and paste it on the input box of âAdd Device > Linkâ to authorize the device.â which I presume is for sharing to another reolink app.
But the firmware on the E1 Pro I have isnât capable of adding additional users so far as I can tell. Iâd be more than content to be corrected about that as I would also like to segregate all of that across RO accounts, etc.
