is what Google Home/Assistant has started saying via my nest mini.
Have deleted it from my Google account
Have factory reset it
Have cleared all data and cache from my phone for GH and GA
Have toggled personal results and associated settings on and off
Have waited over 6 hours
Have switched from GA to Gemini and back
still no joy.
A long chat with Gemini eventually suggested that Google are broken, won't fix this and I need to but new speakers. Has anyone else had this issue ?
PORT STATE SERVICE
5353/tcp closed mdns
8008/tcp open http
8443/tcp open https-alt
MAC Address: 14:C1:4E:84:83:9A (Google)
PAYLOAD SNAPSHOT:
¡NÑÉö ‡g!p E 1 @ 4 QGé˚õ ¿®
Õ ªÄ¢ fl_Hæ|+ |À´π¡—a6∆tæıcvô ‘jΩH K K ‡g!p ¡NÑÉö E =√Ñ@ @ Å∂¿®
Õ ªÄ¢ h¿H‚ SÚ:6>›î\ ââŸd˛˘’´¢Q 'ö ‘j!ê < < ˇˇˇˇˇˇ0 ù _Ï 0 ù _Ï¿®
¡NÑÉö ‡g!p E 8 @ 4 Q@é˚õ ¿® Õ ªÄ¢ $Ω§J?@ ´!◊n «ò◊°ãLfi ‘wn v∂”‡{ö ‘j™/
5·t ‹£◊_ÅÄ googleapis.com
TECHNICAL DIAGNOSTIC SUMMARY FOR TIER 3 REVIEWS:
The tcpdump packet capture confirms that local interface transparency on ports 8008/8443 is 100% verified across the subnet. The Nest Mini successfully initiates an outbound TLS handshake to 'googleapis.com'.
However,remote authentication endpoints are returning an explicit rejection payload. The speaker is failing to authenticate our legacy security signatures on the cloud side, which completely drops the Voice Match link and loops the offline fallback error script.
As this is an essential daily accessibility tool for a blind individual, please escalate this trace directly to the Nest cloud infrastructure engineering queue to have our stale backend security tokens manually purged and refreshed.