Urgent.News

What's breaking now, across thousands of outlets.

Tech

I bought cheap smoke detectors and soon regretted it - here's what I recommend now

The X-Sense smoke and carbon monoxide alarms are easy to install and offer good value for money.

When the writer moved into their almost 30-year-old home, the original smoke detectors were still in place. Being budget-conscious, they replaced all the detectors with inexpensive battery-powered ones. However, these detectors began chirping low-battery alerts, causing annoyance. After replacing them with the CO combo X-Sense XP0H-WN smoke and carbon monoxide detectors, the writer no longer worries about replacing them or their batteries for a decade.

These detectors, with a sealed, built-in battery, last a decade just like the device itself. The X-Sense interconnected model comes with a network that connects up to 18 detectors, making it easier to test and silence all alarms simultaneously. While the X-Sense detectors don't have Wi-Fi, a $18 remote control can test and silence all interconnected detectors without climbing a ladder.

The US Fire Administration recommends replacing smoke alarms every 10 years from the date of manufacture, placing them on ceilings or high walls, and testing them monthly.

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

Read the original at zdnet.com →

More in Tech

Show DEV: Building Smartphone Specs API with .NET and Caddy

Mobile hardware specification APIs have long been messy and hard to integrate, largely due to incomplete and unnormalized data. Raw strings as specs are frustrating to use in program logic.

  • API solves messy mobile hardware spec data issues
  • Backend transforms parsing to clean JSON output
  • Supports deep filtering by URL parameters

Building the foundation Claudius runs on

This tutorial was written by Néstor Daza . This is the third article in a series about building Claudius , my own Claude-based chatbot ( Github ).

  • Identity system prevents client from tampering with user roles on server
  • Three roles (admin, member, guest) resolved in specific order on server
  • Deployment requires OAuth client identifier and secret in Google Cloud Console

More from Tuesday 4 August →