Arlo|Smart Home Security|Wireless HD Security Cameras

My device settings,,account and system settings are all greyed out on PC and mobile app !!

Reply
Discussion stats
  • 9 Replies
  • 2795 Views
  • 1 Like
  • 3 In Conversation
Stealthmode4u
Aspirant
Aspirant

I could not find a solution with support so I will make an attemot here. This is "another" new problem. I can no longer set the sensitivity on my camera system like I used to be able to do along with the amount of time each camera records. DEVICE, SYSTEM AND ACCOUNT ARE ALL GREYED OUT NOW AND DO NOT HAVE THE OPTION TO CLCIK ON THEM. Anyone brainstorm this one yet???

 

Thanks in advance,

 

RC

9 REPLIES 9
jguerdat
Guru Guru
Guru

Ha! Answered a similar question jus a bit ago. Those are simply section headers. It's the items below each header that are clickable, as you've discovered. Depending on what you're trying to do, you may want to check out your modes in the Mode tab, instead.

Stealthmode4u
Aspirant
Aspirant
Thanks for the reply but there is nothing below the greyed out areas that your calling "headers" and the video record time and sensitivity are not in the "mode" section. Again. Account, device and system you could at one time click on them which brought you to the screens for those settings I mentioned above.
jguerdat
Guru Guru
Guru

Perhaps you're referring to the old interface from before the beginning of this year.  If you're still seeing that, try updating (or reinstalling) your app and/or flush the cache in your browser or use a different browser. Here's a browser sample of what should be seen:

 

https://dl.dropboxusercontent.com/u/4960473/Image1.jpg

Stealthmode4u
Aspirant
Aspirant
I once again thank you for your input. As you can see, there are the three greyed out areas ad I stated, in the picture you sent below. Thos IS the exact software I have. I can not click on any of those areas. Maybe you can send a pic of the screen thats shows how to adjust the camera sensitivity and recording time like I use to be able to do. If Im not mistaken you can adjust up to 90 second record time. Hope this finally will help. Thanks RC
jguerdat
Guru Guru
Guru

So, you can't click on My Devices, Profile or Camera Order? Those, along with others with a white background, are the clickable ones. Maybe a screenshot of your display would help.

 

Edit: Oy! Read too fast. You're in the wrong area to make mode/rule changes. As of the update early this year, you find those under the Mode tab when you log in. Click Mode, choose your system and then edit your modes to make any changes to sensitivity, duration, and notifications.

JustLearning
Apprentice
Apprentice
The Arlo Q cameras both had turned on their night vision setting though I had turned it off! Can settings just change themselves?!
jguerdat
Guru Guru
Guru

I recently opened a trouble ticket on this.  My issue is that the camera is pointed outside through a window and a car's lights that are briefly bright (brake lights or headlights flashing on the camera) will cause the IR illuminators turn on, blinding the camera due to reflection,, even though specifically set to off. I had restarted the camera using the interface (no power cycle) and then saw a new firmware flashed the next night.  However, last night it happened again.  I've restarted once again and toggled the night vision setting to see if that helps at all.  Right now I'm in a test mode to see what happens.  If it does it again, I'll try power cycling the camera.  It's been escalated to level 3 support so we'll have to wait and see.

 

Open your own ticket to add emphasis.

JustLearning
Apprentice
Apprentice
Thank you for your helpful message. I have my own ticket but please could you post Netgear's response when you get one?
jguerdat
Guru Guru
Guru

Sure. The only info I have at the moment is that it's been escalated. Fwiw, this is the second night vision I've opened on the Q cameras. The other was early March when the LEDs would just turn on seemingly by themselves, although sometimes it happened when turning off room lights. That seemed to be resolved by a firmware update. Maybe not...