When a camera refuses the Hub's sign-in
When a camera stops accepting the username and password the Hub holds, usually because its password was changed on the camera, the Hub stops signing in to it before the camera locks the account, and says so everywhere.
What the Hub does
Many cameras lock their account for a few minutes after a handful of failed sign-ins. A Hub that kept signing in with an old password would keep you locked out of your own camera. So when a camera refuses the Hub's sign-in, the Hub stops asking.
- It checks once, with a single sign-in to the camera's video, before it decides.
- If the camera refuses, the Hub stops signing in to that camera: no live view, no recording, no motion events and no clock check for it. Your other cameras carry on.
- It asks the camera again on its own after 15 minutes, then 30, then once an hour, and starts everything again as soon as the camera accepts.
- This holds across a restart of the Hub.
Where it says so
- On the camera's page on the Hub's web page, Detection: Where motion is decided shows SIGN-IN REFUSED, with an Ask again row and Try again.
- On a screen plugged into the Hub, the camera's tile shows SIGN-IN REFUSED.
- In the app's Playback, the stretch with no recording is labelled Camera refused the Hub's sign-in.
- In the app, the camera's tile says it refused the stream, with Sign in again, and the camera's page shows SIGN-IN REFUSED under Motion watch on the Hub.
Fix it
- If the camera's password was changed on purpose, update the camera's sign-in in the app: on the camera's tile, choose Sign in again, then Update Sign-In. The Hub tries the new sign-in at once.
- If it was changed by mistake, put the old password back on the camera, then choose Try again on Detection (or under Motion watch on the Hub in the app). Try again asks the camera once, and the Hub carries on only if the camera accepts.
Did this page help?