Why IoT Devices Are Prone to Failure

Author: Leor Grebler

Source: IoT Home

Published by IoT Think Tank

Please indicate the source and origin when reprinting

For various reasons, IoT devices are particularly prone to failure or even scrapping. The Ubi device’s blue LED indicator lights up when powered on, but two minutes later it inexplicably restarts, and this process repeats until the user loses patience. Sometimes, the blue-ringed Ubi emits hissing or popping sounds upon rebooting or produces faint screeching sounds from the speaker. Ubi is a consumer IoT smart hardware launched by UCIC on Kickstarter in 2012. It is a voice-controlled assistant device that can directly control smart bulbs, thermostats, and small appliances via voice, functioning similarly to the Amazon Echo, but launched two years earlier. As a company developing IoT smart hardware for the first time, we faced many challenges that needed to be overcome. We not only had to design, develop, build, and launch the product but also guide users through the initial installation and debugging. We should have been able to identify hardware issues immediately to quickly find the cause of the failure and devise solutions. IoT devices pose certain risks to users. As more devices are added to the home, the likelihood of failure increases. These IoT devices often lack simple user interfaces, have complex installation processes, and provide little warning before failing. IoT devices require a continuous internet connection to function, making them susceptible to network or hardware issues, which can turn them into bricks. Device manufacturers must ensure that their products can continuously meet customer needs long after installation.

UBI

Two Ways Devices Can Be Scrapped IoT devices can be scrapped in various ways, but it usually occurs during one of two cycles: the operational cycle or the lifecycle, the latter being akin to dying in old age. To some extent, even the best internet services can become tiresome, and when we tire of a product, we unplug it and stop using it. The pinnacle of device usage is to continue using it until the end of its lifecycle (consider the oldest cameras that are still operational). However, the operational cycle may end before the product lifecycle concludes, and for IoT devices, either hardware or software can lead to device failure. There are often signs of malfunction before a device is scrapped. For starting devices, such as switches, plugs, lights, and thermostats, failures are primarily manifested in longer-than-usual delays, partial command completion (e.g., a thermostat providing heat but not reaching the desired temperature), lack of confirmation after success, or complete errors. For voice assistant devices, failures may present as slow or unclear voice responses, inability to respond correctly, or failure to understand user commands. For WiFi speakers, playback may often produce crackling, popping, or buzzing noises. Generally speaking, for all IoT devices, over time, the endpoint of the operational cycle may be indicated by non-functional LED blinking, different LED colors flashing upon startup, physical discoloration of the device, and unstable network connections, etc. Reasons for Device Scrapping Bringing IoT devices to market requires assuming more responsibilities; you need to continuously improve, adjust, and add new features after users first interact with the product. Without these improvements, the product will prematurely end its mission. There are many reasons for IoT device scrapping, which may occur due to network service failures, software crashes from local operation to the device, or hardware aging. The “I” in IoT signifies that devices require backend operational support services. IoT aims to remotely drive devices, collect sensor data, or both; as product functionalities iterate, servers must also be continuously updated; if backend operational support services encounter issues or priority changes, the device service may terminate, rendering the IoT device useless. Voice interaction features are composed of Google and Android voice recognition software. If Google updates this service, Android must also support the update, necessitating continuous new updates to keep the device operational, creating an ongoing infinite loop. Any IoT device running applications on an operating system that needs updates will encounter problems, especially if the device operation depends on the registered operating system (e.g., Android’s Google Play services); to some extent, application services may be terminated, and for IoT devices with touch screens, users may have to manually stop operations or program updates. The most challenging cause of device scrapping is physical failure of components. During the operational cycle, this may be due to wear and tear, thermal factors, or other mechanical failures; plugs and connectors have limitations on the number of times cables can be plugged and unplugged, battery charge cycles are also limited, and heat can cause components to age prematurely. Why IoT Devices Are More Prone to Scrapping For various reasons, IoT devices are particularly prone to failure or even scrapping. Firstly, IoT is a new product type with less accumulated iterative experience compared to appliances or vehicles; many startups are venturing into IoT, and these startups are also producing consumer devices for the first time. To change the industry’s common lack of experienced knowledge, they need to learn about quality assurance and product testing. Another major factor contributing to IoT device scrapping is usage patterns. Typically, these devices are always on, waiting to receive commands or transmit data, whereas non-IoT devices can enter sleep mode; however, IoT devices (like network cameras) remain continuously on and generate heat, making components susceptible to heat damage. Furthermore, devices may be installed in confined spaces where heat dissipation is challenging. Often, devices scrap themselves without showing any signs of failure. The infrastructure behind IoT devices also requires continuous maintenance and updates; many first-generation smart hardware companies may not consider the costs and efforts to keep services alive, ultimately leading to service shutdowns. Additionally, changes in security protocols or security vulnerability patches require device manufacturers to remain vigilant to ensure devices are not exploited by hackers.What Device Manufacturers Can Do? Preventing device scrapping should begin at the product design stage. Product managers can provide expected goals for the device lifecycle, and designers can design and select the BOM (Bill of Materials) based on these goals. Testing devices is crucial to prevent scrapping, which includes turning the device on and running multiple test cycles after production (before shipping), testing in extreme environments (high/low humidity and temperature), and fault inspection.

UBI Testing

A warning system that alerts users to faults is also helpful, such as monitoring the internal temperature of devices, measuring startup delay times, or alerting users and maintenance teams when a device disconnects. Similarly, users can access the official website to communicate issues with devices and obtain diagnostic and repair tools. For any IoT product, wireless updates can quickly mitigate any potential software or firmware issues. For devices that require installation, having replaceable modules (like computational modules) that users can remove leads to a better user experience. We consider what a 10/10 iFixit rating might look like during the product design phase and then work backwards to determine what needs to be done during the design phase. Dealing with Inevitable Issues If a device that users love is scrapped too early, manufacturers can respond in the following ways: ◆ Provide alternatives for users who love the product ◆ Inform users of the expected lifespan in advance ◆ Offer discounts for upgrades to the next generation of devices ◆ Form or support teams for users to repair or refurbish products ◆ Monitor and report not just the health of individual user devices but also the health of all devices and systems ◆ Send early alerts about potential failures before users are aware of issues. All devices will eventually be phased out; no device can guarantee 100% reliability, nor will any device remain useful forever. As IoT devices have become a part of homes and workplaces, we should plan for the long term to ensure more stable and longer-lasting service.

Previous Popular Science Articles (Click on the title to read directly):

• “How Difficult Is It to Make a Smart Lock on Shared Bicycles?”

• “What Is the Blockchain Technology That Is Disrupting Banks and IoT, Attracting Siemens and Alibaba to Compete for Layout?”

• “Explaining CPU/GPU/TPU/NPU… What Are These XPU Devices?”

• “A Cartoon Explains: Besides WiFi and Bluetooth, What Can the Recently Hot NB-IoT Do?”

• “A Cartoon Explains: What Is the LoRa That Everyone Is Talking About Behind NB-IoT?”