Did anyone get their battery-powered Reolink device (in my case an Argus 3 Ultra) running? @starkillerOG made a dream come true (thank you!), but the docs do not mention this new option and the way to get it running as a camera.
I also checked the changelogs and the merge process docs, but I found no hint.
Currently, I just find several camera entities, but neither an image nor a stream.
So I currently only tested using the Reolink video doorbell battery. I have many more battery cameras laying around, but I just did not have the time to check more models.
You should be able to just go to settings>devices>+ add integration>Reolink and then just put in the username, password and IP. Then it should connect. If not, I would need to debug and look into that specific model.
I know that Reolink is working on a improved version of the battery protocol (combining UDP and TCP). I am not sure if that protocol is already in newer Reolink battery models. If so, those models will likely not yet work.
I did not mention this in the docs yet because it is still very much a work in progress. Yes the battery doorbell works, but I have no idea about the other models. Moreover the Motion and AI sensors don't work yet since I need a new push protocol for battery cameras that wake by themselfs. (working on that next). So currently you can see/make snapshots and control settings and things like the lights and siren. But some essential features are still missing.
So I did not want to put it in the docs and get wrong expectations that it is actually feature complete. I will update the docs once I feel comfident it works on most models and the most essential features are all working.
There are two disabled camera entities called "snapshots fluent" and "snapshots clear", you can enable those to get a "choppy" camera stream.
I did not implement the live streaming yet. (I will work on that, but that will be a while. push protocol and newer TCP battery protocol will be implemented first).
Noteworthy, I get an warning message (sorry, it's German for Reolink-Webhook-URL not reachable) regarding ONVIF video transmission:
Reolink-Webhook-URL nicht erreichbar
Warnung · Von Reolink gemeldet
Der anfängliche ONVIF-Zustand von Argus 3 Ultra wurde nicht empfangen. Höchstwahrscheinlich kann die Reolink-Kamera die aktuelle (lokale) Home Assistant URL `` nicht erreichen. Bitte konfiguriere eine (lokale) HTTP-Adresse unter „Home Assistant URL“ in den [Netzwerkeinstellungen](https://my.home-assistant.io/redirect/network/), die auf Home Assistant verweist. Zum Beispiel `http://192.168.1.10:8123`, wobei `192.168.1.10` die IP-Adresse des Home Assistant-Geräts ist. Stelle außerdem sicher, dass die Reolink-Kamera diese URL erreichen kann. Bis zum Empfang des ersten ONVIF-Pushs werden für Bewegung/KI schnelle Zustandsabfragen verwendet.
Is this an expected message? The local IP is (and was) correctly set there.
I was able to connect my Argus PT Ultra using the device password. Thanks for that @starkillerOG !
However, I'm getting the same error message as above regarding the webhook URL.
Also, I got 51 entities, but no camera stream or snapshots as described by @starkillerOG. I didn't find them among the deactivated entities either… plus, the camera seems to be constantly awake. At least its status is always set to "awake," and the battery consumption is quite high.
The sleep sensor in HomeAssistant is not working yet. It only polls its status when their is a connection to the camera and then it is awake (for 10 seconds). but just after polling it should go back to sleep. This will hopefully start working once the push protocol has been implemented.
Battery consumption should not be impacted by having it in HomeAssistant. It should only poll for data every 6 hours waking the camera for about 10 seconds.
Of course each time you use a entity of the camera, it will wake the camera to apply the settings change or for instance turn on the floodlight/siren. Therefore while playing with the camera you can expect higher battery usage. But when you leave it allone, Home Assistant should not cause extra battery usage.
Port scan while testing showed the usual streaming ports closed:
80 closed
443 closed
554 closed
1935 closed
8000 closed
8554 closed
9000 closed
Switching the Reolink integration protocol option from RTSP to FLV made the camera entity appear, but the stream worker still seems to try RTSP when live view is requested.
I have a Reolink Solar Floodlight Cam that I have not setup yet, so yes I will definitly make that work. However I am first focusing on the battery doorbell to get that good before continuing to the next model.
Eventually I am sure I will get the Reolink Solar Floodlight cam supported with a direct connection, but I don't know how long it will take.
My guess is that its using the newer protocol which I did not implement yet since this is one of their latest battery models.
These battery cams do not support any normal streaming protocol like RTSP, FLV or RTMP. They have their own reolink build streaming protocol. Eventually I will implement that, but that is going to take quite some time.
So for now their is no life stream if you connect a battery camera directly, only the choppy snapshots streams.
I would be happy to have this for the moment. But I did not find those hidden settings "snapshots fluent" and "snapshots clear" you mentioned. This refers to hidden HA entities, right? There's nothing like this for me, only lots of other entities such as floodlight, AI settings, image saturation etc.
Just wanted to say that my reolink video doorbell battery integrated into HA with this latest update. Hardware DB_560 with build 25082501 . purchased within the last 30 days from amazon.
After reading this thread I ignored the onvif error and activated the snapshots. my login was the same as what was setup for the reolink app. aka admin:xxxxxx.
The battery level was reported in the maintenance section of the HA overview summaries. Looks like 41 entities were reported. I can see the snapshots after enabling them.
thanks for all the work and looking forward to updates
settings, devices and services, reolink,3 dots to right of doorbell, 41 entities, snapshots fluent(or clear),click gear, enable.
then the snapshot could be viewed from the overview card when you select the area that the camera was assigned to. note it takes about 10 seconds for the snapshot to appear.
then I added another card to the dashboard and selected by card type, picture glance, and selected the appropriate camera entry.
remember this is a work in progress and I am a novice grade HA user