Just for info you can grab a still image from the camera at the following url -
http://192.168.2.119/cgi-bin/api.cgi?cmd=Snap&channel=0&user=admin&password=123456
Just for info you can grab a still image from the camera at the following url -
http://192.168.2.119/cgi-bin/api.cgi?cmd=Snap&channel=0&user=admin&password=123456
Ah that is a bummer...
I asked last week on their forum whether my other reolink cams would get webhooj support. But the feedback was that Reolink doesn't read those discussions and I had to contact theur support.
So my advice is to go to "contact" on the reolink website, waste a few minutes to have a complete useless discussion with thei AI chatbot, until it offers to type "talk to a human"...
BTW my onvif nodes have never been published to npm, so not available in your palette
npm install bartbutenaers/node-red-contrib-onvif-nodes
Seem to install OK but cannot be found in Pallet ?
Did you run that in the .node-red folder, and have you restarted node-red since installing it, and refreshed the browser page?
Thanks Colin for the kick, I thought I had refreshed but I guess not
That is the part I keep forgetting too.
The webhook option is still in the Web interface not the mobile app and I confirmed it is only in 4110 firmware version.
Does anyone know if they work with http and https?
Thanks for this great write-up
Got webhooks working a treat!
Does anyone know if there is a way to send a custom text or audio replies?
I have the same 340P model. However on the Reolink website there is no formware for this version only the "Reolink Video doorbell POE". If you try to update withe the firmwaer on the Reolink site it is running. but nothing happens firmware still the same. Support desk of Reolink confirmed this that there is no firmware for the 340P version on there website. There are two versions 340P end de video doorbell POE.
That error is because you are running Node-RED with NodeJS 16 (still running 3.1.x?) and one of the dependencies needs NodeJS 18.
You need to update the container you are using to one based on NodeJS 18, there should be a 3.1.15-18 tagged container or move to 4.0.x which is based on NodeJS 20 by default