A smart-home device can keep turning on, locking a door, showing video, or reporting motion long after the manufacturer has stopped promising security updates. That is why “still works” and “still supported” are not the same thing.
WesternTechy checked current public support policies from Google Nest, Ring and Philips Hue on October 3, 2026. The important lesson is not that one number applies to every brand. It is that vendors start their support clocks differently, cover different kinds of updates, and may publish model-specific end dates separately from the general policy.
The quick comparison
| Vendor | Published minimum | Where the clock starts | What to verify |
|---|---|---|---|
| Google Nest | At least 5 years | From when Google starts selling the device on the U.S. Google Store | Whether your exact model is still listed as receiving critical security updates |
| Ring | At least 4 years for qualifying new purchases, or the listed device date if later | Ring’s policy depends on where and when the device was bought; device-specific dates also matter | Your exact model’s entry in Ring’s Software Security Updates page / Control Center |
| Philips Hue | Hue publishes minimum support periods that differ between Bridges and other Hue products | The detailed policy uses purchase/support-life language and maintains product-specific status information | Your product generation plus the current End of Support status table |
These are not directly interchangeable promises. Google frames its connected-home policy around critical security issues that can be fixed remotely. Ring describes software security updates and publishes device-specific support information. Philips Hue combines security with quality, interoperability and compatibility language in its End of Support policy.
Google Nest: at least five years from first U.S. sale
Google says its Nest connected-home devices receive automatic security updates for at least five years from the date Google starts selling them on the U.S. Google Store. Its support table also shows whether a model is currently receiving critical security updates and the minimum date implied by that five-year window.
For example, Google’s current table lists the Google Home Speaker (2026) with a June 25, 2026 release date and a minimum security-update date of June 25, 2031. It lists the current wired Nest cameras and third-generation wired Nest Doorbell with October 2025 release dates and minimum windows extending into 2030.
Google also publishes Nest Security Bulletins. The August 2026 bulletin documents vulnerabilities that had affected connected-home devices and says the listed issues were addressed through over-the-air updates. That is useful evidence that the support policy is tied to an active patching process rather than being only a marketing statement.
Official references: Google connected-home security update policy and Nest Security Bulletin—August 2026.
Ring: read the device-specific support entry, not just the box
Ring’s current general policy says devices bought new from ring.com or from Amazon where Amazon is the seller receive software security updates for at least four years from purchase, or until the device-specific date Ring lists if that date is later. Ring says it may continue updates beyond that minimum, subject to technical and other limits.
That means a second-hand Ring device, a marketplace purchase, and a new unit bought directly from an eligible seller should not automatically be treated as having the same remaining support window. The practical step is to identify the exact model and check Ring’s current Software Security Updates page or the device information in Ring Control Center.
Ring product pages can also publish security-support language for current hardware. The 2026 Battery Doorbell 2K Plus page, for example, includes a software-security-update section and points owners back to Ring’s device-specific support information.
Official reference: Ring devices software security updates.
Philips Hue: the Bridge and other Hue products have different policies
Philips Hue publishes a formal End of Support policy rather than one universal number for everything it sells. The policy separates the Hue Bridge from lights, cameras and other devices.
For Hue lights, devices and accessories other than the Bridge, Signify states an intention to provide required security, quality and interoperability updates, plus compatibility with relevant Hue services and apps, for a minimum total period described in the policy as five years. The Bridge section uses a shorter minimum support period and separately discusses major platform updates, service compatibility and security updates.
Hue also maintains a current product-support status section, which matters because a policy summary is less useful than the status of the exact generation in your home. The company advises users to keep devices on current software and provides a separate security-advisory page for update guidance.
Official references: Philips Hue End of Support policy and Hue security advisory and update guidance.
Why support windows are easy to misread
There are at least five different dates that can appear around one smart-home device:
- the original product announcement date;
- the date your regional store first sold it;
- the date you purchased your unit;
- the date the vendor stopped selling that generation;
- the last date the vendor promises security updates.
A policy based on first sale can leave a later buyer with less of the minimum window remaining. A policy tied to purchase can depend on seller and proof of purchase. A policy tied to end-of-sale may be generous for mature products but requires the vendor to publish or maintain the relevant date.
That is why a buying guide should not simply say “five years of updates” without explaining what starts the clock.
Security updates are not the same as feature support
A device can continue receiving critical security patches while losing an optional integration, cloud feature, subscription tier, voice-assistant function or app interface. The reverse can also happen: a legacy device may continue to function locally after the vendor no longer promises security maintenance.
For that reason, track at least three things separately: security support, service/app compatibility, and physical functionality. Treating those as one status hides the real risk.
What to record before buying a connected device
| Record | Why it matters |
|---|---|
| Exact model and hardware generation | Support policies and firmware can differ inside one product family. |
| Purchase date and seller | Some support promises depend on when and where the device was bought. |
| Vendor support-policy URL | Lets you recheck the promise later instead of relying on a retailer listing. |
| Current firmware / software version | Shows whether the device is actually receiving the vendor’s current release. |
| Account owner and recovery method | Important when an update, reset or ownership transfer requires the primary account. |
| Replacement trigger | Decide in advance whether end of security support means retire, isolate or replace. |
The WesternTechy Device Inventory & Account Transfer Tracker is designed for exactly this kind of record. Do not store passwords in it; record ownership, model, controller, support state and handover information instead.
Which devices deserve the strictest support standard?
Prioritize update support for devices that can reveal sensitive information or control physical access: cameras, doorbells, locks, alarm components, hubs, routers and account-connected controllers. A discontinued decorative bulb is inconvenient. An unsupported camera or lock can expose a more consequential part of the home.
For cameras, also review our camera placement, privacy and acceptance-test guide. For accounts and shared access, use the smart-home access and ownership audit.
What to do when a device approaches end of support
- Confirm the exact model. Do not assume the whole product family has the same date.
- Install the final available updates. Keep the device on supported firmware while you plan.
- Review exposure. A local-only sensor has a different risk profile from an internet-facing camera or lock.
- Check account access. Remove former household members and unused integrations before migration.
- Plan the replacement path. Export anything you need, document automations, and identify a compatible successor before factory-resetting the old unit.
- Reset before disposal or transfer. Follow the manufacturer’s account-removal and factory-reset process.
Our local-control and graceful-failure analysis explains why fewer cloud dependencies can make recovery easier, but local control is not a substitute for maintained firmware on a network-connected device.
A practical buying rule
Before buying a connected device that you expect to keep for years, search the manufacturer’s site for three things: a security-update policy, a product-specific support-status page, and a firmware or security-bulletin history. If you cannot find any of them, treat the absence as information you should resolve before purchase rather than assuming indefinite support.
For current camera and doorbell comparisons, see Best Home Security Cameras in 2026 and Best Video Doorbells in 2026. Those guides separate recording, storage and subscription questions from the longer-term support question covered here.
Sources and editorial method
Checked October 3, 2026. This article summarizes current public support-policy language from Google, Ring and Philips Hue. It does not guarantee that a particular device will receive updates beyond the vendor’s published minimum, and it does not treat security updates as identical to feature or cloud-service support. Recheck the exact model’s support page before making a replacement or purchase decision.