12-14-2022 04:49 PM
Hi, I'm experiencing the exact same problem as this post: https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Google-Nest-Hub-stuck-on-clock-screen/t...
There's a couple more. I've tried resetting, flowed everything I can, but none of the posts seem to have any resolutions.
This is the device information:
System firmware version: 324896
Cast firmware: 1.56.324896
12-14-2022 11:48 PM
As I already mentioned, I've tried resetting.
12-18-2022 12:04 PM
Hey cneophytou,
We appreciate you for trying the steps shared on that Community thread.
We have additional questions we'd like to ask.
We appreciate the assistance, MikeClark!
Regards,
Alex
12-19-2022 03:52 AM
A couple of weeks ago. I use the nest hub as a nest cam monitor, and I've managed to narrow this down to happening while viewing a nest cam. Often times it'll crash on that screen. When I try to interact with it, it falls back into the Clock-only mode. Restarting the device (pulling the plug) helps temporarily. Also quite often (in the middle of the night) while in nest cam viewing mode, the device will loudly proclaim "Something's gone wrong" with no other indication, and find itself in this crashed mode.
I am using the original power adaptor, purchased from the Google store.
12-20-2022 02:30 PM
Hello there,
Thanks for the update. To make sure we cover all our bases, could you try resetting your Nest Hub to its default settings? If the issue persists, provide us the fuchsia version of you display.
Best,
Alex
12-20-2022 02:35 PM
It doesn't look like the hub is running Fuscia, it says software version 47.9.4.447810048
12-20-2022 02:40 PM
Hi cneophytou,
Gotcha. Did resetting your Nest Hub work? If not, could you fill out this form so that we can check this with our team?
Thanks,
Alex
12-20-2022 02:52 PM
As I mentioned in my first amd third messages, I've ready tried resetting. For good measure, I reset yet again. It didn't help (if anything it looks like it's made it worse).
Fill out what form?
12-20-2022 03:09 PM
12-20-2022 03:41 PM
Submitted
12-25-2022 08:26 AM
Hi cneophytou,
We're sorry for the delayed response. We received your form — thanks for filling it out. Our team will reach out to you via email to further assist you. Also, please be advised that this thread will be locked after 24 hours.
Cheers,
Alex
12-25-2022 11:29 PM
given there's multiple threads for this exact issue, none of them with a resolution but rather being sent offline through the form, I think it would be advisable to keep the thread open to update once the issue is traced.
12-26-2022 01:09 PM
Hi cneophytou,
Understood! We'll keep track of this case until you're contacted by our higher support team.
Kind regards,
Dan
01-07-2023 04:04 PM
Hey there,
Upon checking, our team has already sent further troubleshooting instructions to your email. Let’s continue through that channel. Also, please be advised that this thread will be locked after 24 hours.
We appreciate your patience.
Cheers,
Dan
01-08-2023 01:18 AM
They didn't, they asked for a video of what's happening, so starting the debugging from scratch.
As for this thread, I highly recommend leaving it open until a resolution is reached, there's multiple threads on this issue and all of them closed in the same fashion without amy updates.
01-08-2023 05:46 PM
Hey cneophytou,
Chiming in, could you share the link so we can check it? Please note that we as Community Specialists, we occasionally do a bit of housekeeping to keep the conversations in our community fresh and relevant. This includes locking threads after a period of inactivity.
Moving forward, please send the required video needed. This is for us to investigate the issue further. Make sure to send it via email on case ID: 2-6547000033597.
Cheers,
Muddi
01-10-2023 07:55 AM
Identical threads:
I think there were at least 2 more I found, but can't locate them now.
01-14-2023 12:52 PM
Hi cneophytou,
Our team has sent additional questions to further the troubleshooting steps to your email. Please continue the conversation there as this thread will be locked after 24 hours.
Kind regards,
Dan