search

fwestenberg / reolink_dev

Home Assistant Reolink addon
MIT License
553 stars 101 forks source link

no motion detection notification on home assistant even if the subscription is fine (and it is captured by tcpdump) #344

Open marcob79 opened 2 years ago

marcob79 commented 2 years ago

Reolink dev 0.33 running on hassio on Rpi4. Reolink RLC 410 camera

After setting it up on home assistant GUI with HTTP on port 80, the subscription seems fine. Anyway, even if I got the event notification from the camera as per tcpdump attached, it seems there is not any relevant message related to it in the debug log.

find here attached home-assistant.log and tcpdump

home-assistant.log

cpainchaud commented 2 years ago

Thank you,

Can you please tell me how many cameras you have? I am reading some weird errors in the logs.

cpainchaud commented 2 years ago

can you remove your TCPDUMP from attachments? they may contain sensitive data/passwords

marcob79 commented 2 years ago

just one reolink camera RLC-410-5MP i have other non reolink camera's

thanks

rfporter commented 2 years ago

I have a reolink RLN8-410-E NVR with four RLC-410-5MP cameras. Streams work fine. Motion sensor continuously shows Clear in home assistant despite motion being picked up at the NVR. I have updated the firmaware of the NVR to latest. I also have a Lumus going through the NVR. Same issue with home assistant not picking up on the motion. So I doubt that it has anything to do with camera firmware.

rfporter commented 2 years ago

In my case, this issue was resolved by setting the internal and external URLs of home assistant to static IP addresses.

UberWagen commented 2 years ago

In my case, this issue was resolved by setting the internal and external URLs of home assistant to static IP addresses.

You mean to say that you're now passing motion into home assistant by just setting the internal and external IP's?

cpainchaud commented 2 years ago

@marcob79 v0.47 is out and the following was added in https://github.com/fwestenberg/reolink_dev/blob/master/TSHOOT.md: You can re-configure default timer called "Motion states update fallback delay (seconds)" for a specific camera, it defaults to 30 seconds but you can go down to 2-5 seconds. Because it will hammer your camera's API every X seconds, it may have CPU/RAM/stability impacts on your camera.

marcob79 commented 2 years ago

Thank you for this update. I had a quick try by lowering this polling interval to 3s and seems working. Anyway I think that this polling mechanism is more a workaround or anyway a fallback. The strange thing is that, according to the previously collected tcpdump, it seems that the event registration is fine, and the event reach my raspberry pi with home assistant running. But this event is not received/catched by the application