Urgent.News

What's breaking now, across thousands of outlets.

Tech

I stopped renaming devices in Home Assistant after my automations silently broke

Three different device names might be a bit overkill.

I stopped renaming devices in Home Assistant after my automations silently broke

Google Home users are experiencing issues with automations that are linked to TV starters. The tech giant Google has acknowledged an investigation into the problems with TV-based automations. Reports so far suggest that the problems are primarily affecting TCL models, although it is unclear if other brands are similarly impacted.

Google Home automations are a valuable tool for creating sophisticated smart home systems. These automations can execute intricate multi-device workflows automatically, rather than requiring manual activation of routines. Essentially, automations initiate themselves as soon as their triggering event occurs. However, a perplexing glitch is currently affecting automations that are tied to TVs.

On Reddit's Google Home sub, users have been voicing their complaints about automations involving their TVs failing to function properly. Despite the expectation that events such as turning your TV on or off should trigger an automation, Google Home appears to be unable to recognize these starter events.

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

Also reported by 1 other outlet

Read the original at xda-developers.com →

More in Tech

FieldOS, Part 2: Nine Add-Ons You Only Pay for If You Need Them

The core of FieldOS — jobs, parts, dispatch, billing — runs the daily grind for any field service business. But "runs the daily grind" and "runs the whole business" are different problems, and every…

  • FieldOS offers nine add-ons for businesses to pay for only if needed.
  • Add-ons address specific gaps like automatic recurring care and real-time sheets.
  • These nine add-ons cover the entire job lifecycle from start to finish.

ISC BIND 9.18.42 Released: Major Milestone for DNS Security

ISC BIND 9.18.42 Released: Major Milestone for DNS Security Meta: ISC’s BIND 9.18.42 hit the open‑source stage on November 5, 2025, delivering a suite of security hardening, performance upgrades, and…

  • ISC releases BIND 9.18.42 on November 5, 2025
  • Enhances DNSSEC with new key-rolling policies and validation
  • Adds support for DNS over HTTPS and DNS over TLS

More from Tuesday 25 August →