Have you also enabled you events in the web interface of your camera as I explained? Because if you don't tell your camera which events it needs to stream, then it won't stream any events.
Which info is being displayed in the Event node status (i.e. the text that appears directly below the event node rectangle)?
Do you see errors in the Debug sidepanel or in the Node-RED log?
Seems that there was 3 days ago a new version released of the onvif library that I use. They now allow to catch exceptions caused by responses from cameras that cannot be parsed. Perhaps that might be the case here. Don't know... I have asked them here for more information. But meanwhile I have again pushed a fix to github to show such errors in the Node-RED Debug sidebar. So if you can again install my node and then see in the Debug sidebar - after you have triggered the Discovery node - if we get extra information.
When I look at your corresponding screenshot, the Event node has status "disconnected":
When the node is disconnected, that is normally due to wrong ip/port/username/password. But of course there can also be a bug in the code. Because the whole (dis)connect recently has been rewritten for this issue, but it is not tested yet by the people that can reproduce the issue.
But I can imagine that a disconnected node results in errors like "TypeError: Cannot read property 'device' of undefined". Of course the message should become user friendly...
Does this error appear when you inject a message via the "start listening" button???
Ok thanks for confirming that!
I don't see any node status:
Is there also no status visible when you have injected an input message, to start the discovery?
I found also a bug in my discovery node, which I need to solve somehow (see discussion).
Seems other people with such a camera had the same issue with the library that I'm using ;-(
Hmm I should have the possibility to debug this. Is there a possibility that you setup port forwarding to that cam on your router, and send me a private message with ip adress/username/password? You can cover it, because I don't need to see anything...
Most of my cams are prety old Panasonic cams.
I have also one Hikvision DS-2CD2442FWD-IW to experiment with Onvif...
You can better start a new discussion (category "hardware") to ask people which cam they advise...
I see now that on my system version 0.6.3 of that library was installed, while their latest version is 0.6.5 (which has been published about 7 days ago).
I have now installed version 0.6.5 to make sure I have the same setup as you. But I see that your camera is not available anymore. Could you please make it public again? I will try to find some time tomorrow evening to test it again with the updated library.
That is the last thing I can try to analyse your problem.
I can confirm that with the latest version, I indeed have exactly the same issues as you have reported.
Now I need to start debugging... But I have only few spare time in the evenings, so you might have to leave your cam public available for a couple of days. Hopefully that is not a problem ...
You are welcome.
The TypeError seemed to be because the Onvif library - for some reason not clear to me yet - does not fetch the capabilities (e.g. events, ptz, ...) from your camera. So it doesn't know whether it supports events.
In my (local) version I have now fixed this, to show a new status in this case:
But that doesn't help you very much.
I need to figure out why the hell I don't get your cam's capabilities
The capabilities are undefined, which resulted in the TypeError.
Now all your capabilities are loaded together with the other service data.
In the service list you can see which services your camera supports.
So I need to use this list instead...
Seems my older Panasonic camera's don't return services, but only capabilities. While your ReoLink camera only supports services, but no capabilities. So I had to support both types at the end...
I had to do quite some changes, but I can now connect both to my Panasonic and your ReoLink cameras. I will push it to Github tomorrow evening, because it is getting too late now...
Unfortunately I don't know anyh way to test the discovery and event streams remotely from here ...