You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've switched from manual configuration to using this integration recently.
I have several cams (11) configured.
2 of them are showing an abnormal behaviour on their "motion" binary_sensor.
What i have checked is:
The binary_sensor shows "detected" even if the cam in BI is not triggered. Nor it goes "clear" when the cam does stop the alarm. It seems to start with the first motion triggering. After that, it stays "on".
If i set it to off the motion binary sensor via developer tools, it turns on again after few seconds. This happens even if BI is totally shut down.
no MQTT communication over those with those two cams and MQTT server takes place when it happens. So it's not a problem of the BI side. So it must be a problem of the Integration's side, not BI's.
It does happen only with those 2 cams, The others are working fine, the "_motion" binary sensor goes on and off when it has to.
The text was updated successfully, but these errors were encountered:
I am having the exact same problem here. 2 cameras show motion detected no matter what. Turn it off manually and it turns back on. MQTT messages show no motion detected and the cameras are not triggered in blue iris yet still they are on. Its interesting its exactly two cameras.
I've switched from manual configuration to using this integration recently.
I have several cams (11) configured.
2 of them are showing an abnormal behaviour on their "motion" binary_sensor.
What i have checked is:
The text was updated successfully, but these errors were encountered: