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
Just curious about how bridge may be interfacing with a battery cam that does not stream constantly. Not sure I noticed a polling frequency or if it somehow "listens" for stream activity between cam and app/serrver. I never had a wyze battery cam so it's never come to mind how to best configure one. I wouldn't want the bridge to constantly trigger a live stream and run down the battery, seems best for it to stream upon motion detection as set in the camera and communicated to the server, or maybe poll it on a schedule. Battery cams actually seem like a big hassle but I may use one out back at some point.
Another question - let say there is a new beta cam being tested that is using same system as an existing cam that is compatible with the bridge - but this device is not yet supported by the retail app so probably is authenticated by some other beta system server. I'm guessing the bridge may see the cam as the existing supported cam but will throw an error being unable to login or authenticate - sound logical?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Just curious about how bridge may be interfacing with a battery cam that does not stream constantly. Not sure I noticed a polling frequency or if it somehow "listens" for stream activity between cam and app/serrver. I never had a wyze battery cam so it's never come to mind how to best configure one. I wouldn't want the bridge to constantly trigger a live stream and run down the battery, seems best for it to stream upon motion detection as set in the camera and communicated to the server, or maybe poll it on a schedule. Battery cams actually seem like a big hassle but I may use one out back at some point.
Another question - let say there is a new beta cam being tested that is using same system as an existing cam that is compatible with the bridge - but this device is not yet supported by the retail app so probably is authenticated by some other beta system server. I'm guessing the bridge may see the cam as the existing supported cam but will throw an error being unable to login or authenticate - sound logical?
Beta Was this translation helpful? Give feedback.
All reactions