search

bartbutenaers / node-red-contrib-onvif-nodes

Node Red nodes for communicating with OnVif compliant IP devices
Apache License 2.0
65 stars 25 forks source link

Action start (stop) is not supported #24

Closed ghost closed 2 years ago

ghost commented 2 years ago

Hi, I need your help .... For my Reolink from RLC-410 I used your node without problem. Two days ago I bought a Reolink RLC-510WA and I have a problem with motion detection. The instruction "Set - msg.action - start (and stop)" in node red return this error "Action start (stop) is not supported". So the cam is CONNECTED but not LISTENING. Can you help me to fix this error?

bartbutenaers commented 2 years ago

Hi @RitaSghe,

When you talk about motion detection, then I "assume" you use the event node?? If so you can find explanation and an example flow in the event-node section on my readme page.

You can send "start" or "stop", but not "start (stop)"...

Bart

ghost commented 2 years ago

Hi, yes, I use the event node and I send "start" or "stop", of course :) I've already read the example in your readme page and with RLC-410 the event node work fine, rather with RLC-510wa I have the error .... msg.action=start don't work and my cam is not in LISTENING mode ...

bartbutenaers commented 2 years ago

Ah ok, I had interpreted you "Action start (stop) is not supported" a bit incorrectly ;-) Can export this part of your flow (both the config node and the node that sends the msg.action input message), and share it here?

ghost commented 2 years ago

I just used your example ....

img01

The config node ...

img02

When I start listening nothing happens and this is the error ...

img032

The cam is CONNECTED but not LISTENING ...

Tell me if you need more information ...

bartbutenaers commented 2 years ago

I have been testing this over and over again, and I couldn't understand how this issue could arrise. Because that error (normally) can never occur in this node.

I just used your example ....

Are you sure about that, or have you replaced the Onvif-Event node by an Onvif-Device node? Because the icon in my example flow looks very different:

image

Unless I have somewhere posted an incorrect flow (which I cannot find), I assume that is the problem. When you want to listen to events, you need to use the Onvif-Events node ...

ghost commented 2 years ago

Yes, you're right .... I have seen the node "onvif device" and I thought needed for the configuration of the cam and then I continued with this node. Thank you very much, I'm so sorry for your trouble and yes, I'm an idiot ......

The only thing I noticed is the long time from when I press "Start listening" to when the node events become "listening" (15/30 sec.); with the old cam this step was immediate (and the same time it's necessary to Stop listening) .... but this is not a problem of your node. Today I test the motion alert ...

Excuse me again, have a nice day.

bartbutenaers commented 2 years ago

Hi @RitaSghe, I'm glad it finally works!
Yes I expect the waiting time to be an issue with the new sotware of your new camera. Might be worth to contact Reolink about that... Bart