This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Light Setting, Duration field is used to set how long the light stays on when manually enabled by the user from the app. The options are 1 min, 5 min, 10 min, 20 min, or Always On. My devices accept a setting of Always On, which is what I want, BUT the devices soon afterwards revert to the 5 min setting. I filed a Support Case and was told that 5 min is the max. This is a bug, there is no good reason for limiting the duration since the device is a Wired Floodlight Camera, model FLW2001Aer1.3 running firmware 1.7.0_462_d6d0f72, and is always powered from 120 VAC.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes they are all reporting v1.8.2_19_bb2940a. And more importantly they all are working like I wanted.
Thanks!!!
Specifically the Light Setting of Always On can be set and holds even when I exit and re-enter the app. I've tested by leaving the lights on for a long while and they've stayed on like they should with the Always On setting.
One negative is that although they honor the Manual Brightness setting, which I've set to 33%, Motion Events do not register any changes to the lighting brightness. Ideally, I would like them to be 100% brightness when motion is detected and then after that times out, revert to the manually setting, 33% brightness for example. If I manually turn the Lights off, then they activate at 100% brightness like they should during Motion Events. But when manually turned on, they just stay at the Manual Brightness level regardless of motion detection.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@majormix wrote:
I filed a Support Case and was told that 5 min is the max.
Sounds like support gave you the wrong information (likely confused on what model you have).
@majormix wrote:
My devices accept a setting of Always On, which is what I want, BUT the devices soon afterwards revert to the 5 min setting.
That does sound like a bug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @majormix
Are you still experiencing this symptom? Which version of the Arlo app are you using and model phone?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem persists. I am running the Arlo Secure app, version 6.2.8_6020802 released 7/25/2025, on a Samsung A71 Android phone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WHat happens if you use the web client (my.arlo.com) on a computer browser?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just noticed your private message today and emailed AskArlo a log file like you suggested.
I had to change the settings (again) from 5-minute default value to Always On.
The problem didn't surface yet, they are still reporting Always On.
I don't know what triggers the problem (event or duration) but I'll keep checking the setting and send another log when it reverts to the 5-minute default.
In the past I've ruled out that exiting and re-entering the app has any effect. It seems to revert after a short time,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the update. If the symptom surfaces again, please let me know and send that log over and I will be sure it's investigated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The wanted Always On setting persisted for over 2 hours, so I exited the Arlo app and re-entered to see if that had an effect and it did, the settings for all 3 floodlight cameras reverted to the 5-minute default. I collected another log file and emailed it to AskArlo just a few minutes ago. I recall testing this theory once before and it didn't cause the problem but that was at least a month ago so maybe the circumstances were a little bit different.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for testing and sending the log, I provided this to the dev team for review.
The Arlo development team is currently investigating this issue. We will provide an update as soon as we have more information to share with the community.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's been a while.. Any news?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The team is still investigating the root cause.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @majormix
The team has placed your devices on a test firmware that should help with the symptom you're experiencing. Can you please test again? This test firmware is: 1.8.1_13_7343f0d
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I go to settings, all three of my camera floodlights indicate they are running the same firmware v1.7.1_468_d45b6b1, and when I click on it I get the message: No Updates Available. Is it possible the test firmware is actually running but is not reporting the version correctly?
Regardless I did some tests. The Front Door device seems to be working correctly, but the Driveway and Backyard devices have the same problem as before. Is it possible the test firmware was only loaded on the Front Door device?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the update. I'm checking with the team to verify the test version number. Also, the production version that is meant to resolve this is currently released at 25% in a slow phase rollout. That version number is 1.8.2.x..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like the devices have updated sometime overnight. I believe all three should be on that test firmware now. I just checked.
Can you please test this again? And let me know the results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes they are all reporting v1.8.2_19_bb2940a. And more importantly they all are working like I wanted.
Thanks!!!
Specifically the Light Setting of Always On can be set and holds even when I exit and re-enter the app. I've tested by leaving the lights on for a long while and they've stayed on like they should with the Always On setting.
One negative is that although they honor the Manual Brightness setting, which I've set to 33%, Motion Events do not register any changes to the lighting brightness. Ideally, I would like them to be 100% brightness when motion is detected and then after that times out, revert to the manually setting, 33% brightness for example. If I manually turn the Lights off, then they activate at 100% brightness like they should during Motion Events. But when manually turned on, they just stay at the Manual Brightness level regardless of motion detection.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the update! glad it's working. For the new concern, if you don't mind creating a new thread and tagging me, and I can look into this if it's a potential issue, this helps the team provide the support possible.