Agreed. I had a previous thread open that was locked but it is happening still today. I will contact Google again tomorrow because I can replicate everything about this.
TLDR: Battery Cameras Lose Live View or Shows Offline. If you unplug for a few minutes it comes back. On 1 occasion I had to reset 1 camera. Yesterday, one camera was offline and unplugging it didn't work. I left it unplugged over a few hours and plugged back in and now it's back but a different camera lost Live view. They seem to come an go if you leave them. I did notice that at one time all my cameras, battery and older gen went offline for a min. They all came back but 3 of the battery ones did not. Almost like an API Rate limit. Eventually they came back. When cameras are showing offline, Live notifications still work so it's not really offline and if you go to history, the recordings are up to live, you just can't see live. So it's obviously connected.
I have 10 Nest cameras total. 3 original, 2 Outdoor, 1 doorbell wired, and 6 battery. All my battery ones are wired to AC power for 24 hr recording. The battery ones have been working fine for a few months now, since they came out. Starting 2 weeks ago, I started losing the ability to view them live. All of them. It says the camera might be saving battery message but they are all wired. If you go to settings it even says plugged in. History and recordings all still work but no live viewing. One of them keeps showing offline too now. Unplugging them for a minute then plugging back in restores the live view. The one that says offline, I have to remove from magnet and push restart button. Anyone else getting this? They had been stable, but this last week have been terrible. Bad update maybe?
Spoke too soon. Of the 4 I reset, 3 are still working but 1 now shows offline again. The odd thing is, even though it's showing offline, I'm still getting immediate notifications for motion and it's still recording. I tried to restart it and now nothing. Doesn't even light up green anymore. Will contact Google again but it sure looks to me like a bad firmware push
