How are maintenance and updates handled for IoT devices?

How are IoT devices maintained and updated?

Keeping connected devices dependable throughout their working life

Hello, friends. Maintaining Internet of Things devices involves more than pressing an update button. Physical condition, power, connectivity, configuration, software and vendor support all need attention. The aim is accurate measurements, correct responses to commands and a workable recovery process. A home sensor and a gateway serving a production line need different maintenance arrangements; the difference between IoT and IIoT directly affects operational continuity.

1. Identify the devices you are responsible for

Record the manufacturer, full model, hardware revision, serial number, location, running firmware version and responsible person. Include the network address, associated hub, support end date and last successful backup. Use an identifiable name such as “North warehouse door, device 07” rather than “warehouse sensor”. NISTIR 8259A addresses device identification, configuration, access, data protection, software updates and visibility of cybersecurity state as baseline capabilities.

2. Apps, firmware and configuration files are different

Firmware is the embedded software running inside the device; the phone app, gateway software and cloud service are separate components. An up-to-date app does not prove that the device is up to date. A configuration backup may contain measurement ranges, alarm thresholds and network or communication settings; it is not a replacement firmware image. Read the release notes: does the new version require a different app, hub or data format? Check device compatibility before installation.

3. Software cannot replace physical maintenance

Following the manufacturer's instructions, inspect supply voltage, batteries, cables, antennas, connectors, contamination, moisture and temperature. A dirty optical surface or weakening battery can produce symptoms that resemble software problems. Cleaning materials and methods must suit the product; unnecessarily opening a sealed enclosure may compromise its seal. Comparing a measuring device against a reference is not the same as performing a calibration; calibration requirements depend on its purpose and manufacturer guidance.

4. Establish a recoverable starting point

Where supported, export the configuration and record the running version, alarm thresholds and important connection settings. Confirm that the backup can be restored to the relevant hardware and target version. Different hardware revisions bearing the same model name may need different images. Check internet connectivity, adequate battery charge or a stable power supply, and free storage where required. For industrial equipment, establish how restarting affects outputs and the connected machine before proceeding.

5. OTA describes delivery, not a security guarantee

Over-the-air updating transfers software over a network without a local service visit. Not every IoT device supports it; some require a local interface or service connection. Use the official vendor channel and the correct package. Encrypted transport, file integrity and software authenticity are different checks: TLS protects the connection, while a hash supplied alongside a file from an untrusted source does not establish who produced it. A signed package verified against a device's trusted key can establish origin and integrity. IETF RFC 9019 explains this update architecture.

Editor's note: Downloading, installing, booting the new version and passing functional checks are separate stages. A 100% indicator may describe only the transfer. A successful maintenance record should be supported by reading the running version from the device and testing its actual function.

6. Can every device return to an earlier version?

No. Recovery depends on the hardware and software design. Suitable systems can use separate firmware slots to return to a working image when the new one fails. Correct boot and health-check logic is also needed. Espressif's ESP-IDF documentation provides a concrete implementation example, rather than a feature shared by every IoT product. Anti-rollback can prevent returning to a version below an accepted security level. Recovering from a failed update and reinstalling a vulnerable old release are different operations.

7. Use appropriate automation and controlled rollout

Secure automatic updates provided by a consumer-device manufacturer can reduce maintenance effort. In production, industrial cybersecurity must be considered alongside operating conditions: define a trial device, maintenance window, responsible person and stopping criteria. For a fleet of 100 devices, for example, update one representative unit and then a small group. Stop the rollout if communication, restart behaviour or alarms change unexpectedly. Group size and observation time depend on the application; there is no universal percentage.

A battery-powered device that wakes infrequently may not receive an update immediately. Track disconnected units separately and use supported staggered retries rather than having everything reconnect at once. Given the attack surface of continuous connectivity, do not expose a management interface directly to the internet merely to deliver an update. Preserve access restrictions while improving distribution.

8. Verify actual operation after installation

Check the running version, retained settings, correct timestamps, real measurements, alarms and command results. On an industrial gateway, has Modbus communication resumed, and have register mapping and scaling been preserved? A temperature sensor appearing on a dashboard is insufficient: check, for example, that 24 °C is not displayed as 240 °C and that an old sample is not presented as fresh data. Test the alarm using an appropriate safe method rather than relying on its notification icon.

An example maintenance record might read: Device 07; previous version 2.3, new version 2.4; configuration backed up; measurement and notification tests passed; operator and time recorded. These version numbers are illustrative. Compare restart counts, data gaps and battery behaviour with the earlier baseline. In healthcare applications or other critical functions, verification must follow the product's intended use and applicable procedures.

9. Prioritise patches according to risk

Monitor vendor security notices as part of IoT security. Priority depends on the affected model and version, exploitation status, exposure and potential consequences. An internet-accessible vulnerability and an issue affecting an unused feature may need different responses. However, indefinitely postponing a patch because the device still works does not remove data-breach risk. If installation is delayed, apply appropriate vendor-recommended access restrictions and monitoring; treat these as interim measures.

10. Maintain credentials, certificates and data

Remove unauthorised accounts, disable unnecessary services and use strong authentication where supported. Monitor certificate expiry, device time and access permissions; an expired certificate can interrupt connectivity. Do not disable certificate validation to conceal the fault. Configuration backups may contain passwords or keys and therefore need protection for privacy and personal-data security too. The FTC's guidance treats access restrictions, secure data handling and ongoing security support as related responsibilities.

11. Plan inspection intervals and the end of support

There is no universal rule to update every device once a month. Schedule physical inspection and measurement verification according to manufacturer instructions, environment and criticality; assess security notices without waiting for that schedule. Recheck the relevant functions after network changes, battery replacement or a fault. Include subscriptions, spare devices and servicing in long-term costs.

The warranty period and security-update support period are different. ETSI EN 303 645 addresses disclosure of the support period for consumer IoT; it is not a universal industrial-device conformity standard. When support ends, assess replacement or safe isolation. At disposal, do more than assume a factory reset is sufficient: follow the vendor's data-erasure procedure, unlink cloud accounts, revoke access credentials and close the inventory record. This connects electronic-waste management with data security.

Related guides

Fundamentals: IoT guide, How IoT works and IoT versus IIoT.

Security and connectivity: IoT security, Continuous connectivity and cyber risk, Internet requirements and Compatibility issues.

Service life: Long-term costs, Environmental impact and electronic waste and Usability and accessibility.