Peripherals, Wearables & Smart Home Releases
Smartwatches, headsets, drones, smart home devices and the firmware and platform changes that keep them working.
Peripherals and connected devices have a release pattern unlike either software or core computing hardware. The initial launch is a single event, but the product continues changing for years afterwards through firmware, companion app updates and changes to the cloud platform it depends on. For a connected device, the platform change is often more consequential than the launch.
This is also the category most exposed to discontinuation. A smart home device whose vendor shuts down its cloud service does not degrade — it stops. Those shutdown notices are the events worth capturing well ahead of time, because they carry a firm date and there is usually nothing to be done about them afterwards.
What this category tracks
- Device launches
- Wearables, audio devices, headsets, drones and smart home hardware, with published specifications.
- Device firmware releases
- Over-the-air firmware updates and the features or fixes they carry.
- Platform and ecosystem changes
- Smart home standard support, hub compatibility and companion app requirement changes.
- Service shutdown notices
- Dated announcements that a cloud service or companion app supporting a device is being retired.
What matters most here
A connected device is only as durable as the service behind it, and that service has no version number you can check. The shutdown announcement is the only warning, it is usually published once, and the device keeps working normally right up until it does not. Recording those notices as dated deadlines gives you the months of notice the announcement technically provided but that nobody saw.
Where this data comes from
- Manufacturer product announcements and specification pages
- Firmware release notes and companion app changelogs
- Smart home standard and certification announcements
- Official service retirement and end-of-support notices
Every indexed entry links to its primary source. See our editorial and sourcing policy for what we verify and what we do not.
Common questions
Why track companion app updates separately from firmware?
Because they can require each other. A firmware update that needs a newer app version, or an app update that drops support for older firmware, creates a dependency that is only visible if both are recorded. Merging them hides exactly the detail that matters.
What happens to entries for discontinued devices?
They stay. A discontinued product's release history is often the only remaining public record of what it supported and when support ended, and removing it would make the archive less useful, not tidier.
Tracked releases in Hardware Peripherals
The live release list for this category loads below.