Android app 5.6.1_28823

[alex_loo]

5.6.1_28823

Confirmed fixed in 5.6.1:

• FEED page misbehaviour (confirmed by @alex_loo ) (reported since sept/oct-2024?) (as reported by @KachinaShadow and @alex_loo  in this message)
  • redundant dates that are not grouped together (and this is wrong)
  • recordings grouped under wrong date (especially for those around the midnight.  I am suspecting this has something to do with wrong use of time in different timezone)
  • recordings time sometimes wrong

Unknown as to whether 5.6.1 fixes these:

• "library" version crashing when clicking push notification (since 5.5.2) (reference and then this message as reported by @Trusti; and then not fixed by 5.5.3)
• can't access local recordings since at least 5.5.2 (as reported by @JP-FR in this message, then still not fixed in 5.6.0 as mentioned here)
• geofencing not working all the times (since at least 5.4.2) (reported by @alex_loo )
• leave home automation not working since 5.5.2  (reference as reported by @jguerdat )

Alex

[JP-FR]

@alex_loo 

access local recordings still not fixed

[alex_loo]

5.6.1_28823

Confirmed fixed in 5.6.1:

• FEED page misbehaviour (confirmed by @alex_loo ) (reported since sept/oct-2024?) (as reported by @KachinaShadow and @alex_loo  in this message)
  • redundant dates that are not grouped together (and this is wrong)
  • recordings grouped under wrong date (especially for those around the midnight.  I am suspecting this has something to do with wrong use of time in different timezone)
  • recordings time sometimes wrong

Confirmed NOT fixed still in 5.6.1:

• can't access local recordings since at least 5.5.2 (as reported by @JP-FR in this message, then still not fixed in 5.6.0 as mentioned here, then still not fixed in 5.6.1 as reported by @JP-FR in this message)

Unknown as to whether 5.6.1 fixes these:

• "library" version crashing when clicking push notification (since 5.5.2) (reference and then this message as reported by @Trusti; and then not fixed by 5.5.3)
• geofencing not working all the times (since at least 5.4.2) (reported by @alex_loo )
• leave home automation not working since 5.5.2  (reference as reported by @jguerdat )

Alex

[jguerdat]

There's still more testing to do but my GF seems to generally be working properly for the most part. I did have a miss several days ago but recently it's been working fine.

Accessing local recordings is hit and miss but can work. I've been getting "There was an issue loading feed events. Try again" messages but if I persist I can get them to load. Try again may or may not work but leaving Feed and returning may eventually show the recordings.

[alex_loo]

---

@jguerdat wrote:

There's still more testing to do but my GF seems to generally be working properly for the most part. I did have a miss several days ago but recently it's been working fine.

---

I understand that GF is not 100% failing, but I am not after such low level of reliability.  If you have got GF tested positive 100% for multiple device scenarios, over at least a week --- please let me know.  Otherwise, I'd just consider it an outstanding issue and not bother to test it, until ARLO says it's been fixed.  (According to @BrookeN in this message, ARLO is looking into GF now)

Accessing local recordings is hit and miss but can work. I've been getting "There was an issue loading feed events. Try again" messages but if I persist I can get them to load. Try again may or may not work but leaving Feed and returning may eventually show the recordings.

---

To be honest, I don't have the local recordings issue here.  I'd consider it not even a hit-and-miss.  It's 100% working to me (even though the FEED needs to be pushed for the second time for "local" to appear).  Having said that, I trust that @JP-FR  's issue still needs to be followed up by ARLO.  I am only here to consolidate issue list, for the benefit of myself and the community.  Afterall, I am on the user side, and I don't work for ARLO.

Alex

[jguerdat]

Additional testing yesterday showed GF to work properly. All I can say is what I'm experiencing.

[alex_loo]

Are you able to share what cases you tested?  While we only need a single case to demonstrate GF is not working, we need ALL relevant test cases to be passed, before it can be claimed "working properly".

Alex

[jguerdat]

I've seen GF work properly when taking a walk as well as driving, both multiple times. Dunno what else you may think is needed. A single shot of not working is statistically useless.

[jguerdat]

BTW, more "testing" (I.e. leaving home for walks or short trips with my wife) shows more instances of GF failing. I have tried enabling Arm Away manually (need to try that more) and having Arrive work properly. So, GF is still having the same issues as before.

[StephenB]

---

@jguerdat wrote:

BTW, more "testing" (I.e. leaving home for walks or short trips with my wife) shows more instances of GF failing. I have tried enabling Arm Away manually (need to try that more) and having Arrive work properly. So, GF is still having the same issues as before.

---

Do you know if your issue is

• with Arrive only
• with Leave only
• or both?

I found it was Arrive that was misbehaving - and that enabling it in both Arm Home and Arm Away seemed to resolve it.  (Other combinations might also work).  Very strange behavior.

[jguerdat]

I have a simple setup, not using your solution of using Arm Away only for GF. That means I have schedules (day and night) as well as GF that uses Arm Away for Leave and Arm Home for Arrive. Our leaving the house is almost always during the day and only for random trips overnight. 

Generally, Leave is the problem - both phones are outside the small zone (and logged in) but aren't detected. I have tried to manually set Arm Away a couple of times while outside the zone and had Arrive work only once. This needs more testing which is usually only when we go for a walk once a day so that testing is slow to happen.

If Leave works, Arrive also works (so far).