Cameras show as offline in Google Home

[morpheus2n2]

I found this post and its very similar behavior to what I have.
I have noticed that for the last few months my Cameras show as offline in Google home, I have just spent far to long relinking my account due to HTTP 400 error.
Anyway, MY Arlo app is the latest version, all my Cameras are up to date Firmware wise, and the Google Home app is the latest, my Arlo account is part of the Verisure Package if that helps.

[ShayneS]

I just wanted to let you know the issue has been identified and should resolved with the latest versions 6.6.8 - 6.6.9 which is in a slow rollout phase. Once you receive the update please test again and let me know if the symptom continues.

Thanks 

[ShayneS]

Just wanted to provide an update. It looks like the cause has been identified and it fix to resolve this is being prepared. 

[morpheus2n2]

 

[ShayneS]

what is the google home version?

[morpheus2n2]

Not a clue theres no way to check version thay I can see, not to mention that being google home its always upto date as old versions, stop working when they push a auto update out!

[ShayneS]

Hi @morpheus2n2 

Here are a few steps to retrieve the info for the google home version

"Method 1: Through the Play Store

Open the Google Play Store on your Android phone.

Tap your profile icon in the top-right corner.

Tap Manage apps & device → Manage.

Find and tap Google Home from the list of installed apps.

Scroll down to the App info section — it will show the version number.

From phone

Open Settings on your phone.

Go to Apps & notifications (or just Apps, depending on your device).

Find and tap Google Home.

Tap Advanced → App details (sometimes just About) → you’ll see the version number.

From the app

Open the Google Home app.

Tap your profile picture in the top-right.

Tap App settings → scroll down to About — the version number will be listed there."

[morpheus2n2]

4.6.55.1

[ShayneS]

@morpheus2n2 Thank you, I provided this to the appropriate team and I'm waiting to hear back with more info to share. 

[ShayneS · Accepted solution]

I just wanted to let you know the issue has been identified and should resolved with the latest versions 6.6.8 - 6.6.9 which is in a slow rollout phase. Once you receive the update please test again and let me know if the symptom continues.

Thanks