fwestenberg / reolink_dev

Home Assistant Reolink addon
MIT License
550 stars 102 forks source link

E1 Outdoor no longer has working motion sensors following update (E1 Zoom is fine) #534

Open conma293 opened 2 years ago

conma293 commented 2 years ago

Describe the bug E1 outdoor binary motion sensors no longer operate - motion, person, vehicle, pet. Never says Detected, always clear, appears broken after firmware upgrade

To Reproduce Upgrade E1 Outdoor to v3.1.0.956_22041506

Expected behavior no motion is detected (from the integration - reolink apps pick it up fine)

Environment: Version core-2022.7.5
Installation Type Home Assistant OS
Development false
Supervisor true
Docker true
User root
Virtual Environment false
Python Version 3.10.5
Operating System Family Linux
Operating System Version 5.15.32-v8
mnpg commented 2 years ago

Onvif port must be open on your E1Outdoor to have the motion detections. With newer firmwares 3.1.x.x, some ports are disabled by default like onvif. Take a look at the network's advanced settings of your camera if it's the case and enable it In the Reolink client, go to Settings>Network Settings>Advanced>Port Settings

conma293 commented 2 years ago

just updated all the ports - you were right, they were closed..

Deleted and reinstalled the integration for that camera and it's back!!

Thankyou a lot!


From: mnpg @.> Sent: Tuesday, 19 July 2022 4:31 pm To: fwestenberg/reolink_dev @.> Cc: conma293 @.>; Author @.> Subject: Re: [fwestenberg/reolink_dev] E1 Outdoor no longer has working motion sensors following update (E1 Zoom is fine) (Issue #534)

With newer firmwares 3.1.x.x, some ports are disabled by default like onvif. Take a look at the network's advanced settings of your cameras to open (enable) them. In the Reolink client, Settings>Network Settings>Advanced>Port Settings

— Reply to this email directly, view it on GitHubhttps://github.com/fwestenberg/reolink_dev/issues/534#issuecomment-1188759753, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACM2FUKNWIZNIYAQCABAWULVUZRX7ANCNFSM536U335A. You are receiving this because you authored the thread.Message ID: @.***>