Urgent.News

What's breaking now, across thousands of outlets.

Tech

I've been waiting years for a new Google smart display; my patience is about to run out

It's been half a decade since a new Google smart display was released.

I've been waiting years for a new Google smart display; my patience is about to run out

A bug in Google Home is affecting color LED bulbs, causing them to fail in their intended function. Users have reported that Google Home is unable to adjust the color on smart bulbs from various brands, including Philips Hue, Tuya, and Lumiman. The problem impacts both voice commands and app controls, which are typically more dependable than other methods.

Google acknowledged the issue on a Reddit thread, stating that a fix is currently being rolled out. One user who had posted about their experience claimed that the voice commands and app controls were now reliably controlling the bulb color. Google first mentioned it was working on a fix a day after the problem was reported, and the update was promptly released.

This rapid response is likely well-received since the bug compromised a crucial feature for Google Home and smart bulb manufacturers alike. It's possible that the color control issue remained unresolved while Google worked on additional updates to the app. Google releases monthly updates to address functions and bugs as the Assistant becomes more integrated into daily life.

If you've experienced this bug causing smart bulb color control to fail, it should be fixed now. However, if it persists, please share your experience. For more news, check out 9to5Google on YouTube.

Written by urgent.news from 9to5Google's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at androidpolice.com →

More in Tech

Seccomp profiles for real workloads, not for demos

Seccomp profiles for real workloads, not for demos A seccomp profile that denies everything except the calls a container needs is one of the strongest single controls in a Kubernetes cluster.

  • Seccomp profiles limit container calls to workload requirements, not just demos.
  • Most Kubernetes clusters use overly permissive RuntimeDefault profile.
  • Custom profiles needed for threat models involving container itself, not just boundary.

More from Wednesday 7 October →