08-16-2019 07:55 PM
08-17-2019 10:49 AM
Welcome to our community! A smart enabled speaker can certainly be a game changer to help with bedtime and certain routines. We appreciate the time you’ve taken out of your day to share that one of your Insignia Smart Speakers is having some issues after you reset it. We’d be happy to point in you the correct direction on this matter.
We’d highly recommend giving our support teams at (877) 467-4289 a call to see what advice may be available on this matter. Our teams noted above would be best positioned to advise and troubleshoot the issues you've described. Alternatively, reaching out to Google may be fruitful, as well, and sometimes they may be able to provide some additional context or advice, too.
08-26-2019 08:06 PM
I was able to connect with the Insignia team, who connected me to YouTube!, who connected me to Google Home. While I don't have a conclusive answer after an hour and 15 minutes on the phone, it appears that the Google Home app has changed such that it doesn't recognize the Insignia smart speakers as Google Home deviices and, therefore, eligible for Digital Wellbeing. I had them submit a feature request to the Google Home product team to support third-party smart speakers. Until that happens, “¯\_(ツ)_/¯“.
After I was finally routed to the right tech support rep (for Google, BTW, not Best Buy/Insignia), we did some troubleshooting and quickly identified that the Google Home app supports setup and management of Digital Wellbeing controls on the three Google branded speakers on my network just fine. It just doesn't for my two Insignia speakers. This is a shame, because until very recently, it did.
Apparently Digital Wellbeing is also only supported in certain markets (i.e. the US). Editorial: it's super common for Google to test new features with small pilot groups before rolling them out to the general population. This helps them test features, but also can be due to navigating different local laws/regulations/customs. My guess is they're still experimenting with the code. It's possible they didn't intend to turn off third-party devices, but it's also possible they did to simplify integration testing. It's easier to ensure your code works on your own hardware.
I'm quite bummed contentand bedtime controls aren't available for the two devices in my children's rooms - that's where I most want them. I'm hopeful that functionality will come back soon.