Device Shadow
Definition
Cloud virtual representation of an IoT device storing last-known and desired states so apps can interact with it even when the device is offline.
Use Cases
- John Deere: Managing connected agricultural equipment that may operate in fields with intermittent connectivity — John Deere has publicly described using AWS IoT services for connected equipment. A device-shadow pattern lets cloud applications store desired settings and last reported machine state so tractors and implements can synchronize when connectivity returns. (Improved remote visibility into equipment status and more reliable coordination between cloud applications and intermittently connected machines.)
- LG Electronics: Controlling and monitoring smart home appliances from mobile apps even when devices are temporarily offline — In a smart appliance scenario, a cloud-side shadow or twin stores desired settings such as temperature, mode, or power state. When the appliance reconnects, it reads the pending desired state and reports its actual state back to the cloud. (Better user experience because app commands are not lost during short outages, and users can still see the last known device status.)
- Philips: Managing connected lighting devices across homes and buildings — A device-shadow style design allows lighting control applications to keep desired brightness, color, and on/off state in the cloud, then synchronize those settings to bulbs or gateways when they reconnect. (More consistent remote control behavior and simpler application logic for large fleets of devices with varying network reliability.)
Provider Equivalents
- AWS: AWS IoT Device Shadow
- Azure: Azure IoT Hub device twins
- GCP: Cloud IoT Core device state/config concept (service retired)
Frequently Asked Questions
- What's the difference between Device Shadow and a digital twin?
- A Device Shadow usually focuses on a device's current reported state and desired future state so applications can send commands even when the device is offline. A digital twin is often broader. It may include telemetry history, relationships, simulation data, business context, and analytics models. In simple terms, a device shadow is a lightweight synchronization document, while a digital twin can be a richer virtual model of the asset.
- When should I use Device Shadow?
- Use a device shadow when your devices are not always online, when mobile or web apps need to read the last known device state, or when you want to store desired settings until the device reconnects. It is especially useful for IoT devices such as thermostats, vehicles, industrial sensors, and smart appliances that may lose connectivity or sleep to save power.
- How much does Device Shadow cost?
- Cost depends on the cloud provider and how often your application reads, updates, or synchronizes shadow documents. On AWS, pricing is typically tied to AWS IoT Core messaging and shadow operations rather than a flat per-device fee for the shadow itself. Main cost drivers include number of devices, update frequency, message size, retained state size, and related services such as rules engines, storage, and analytics. Always check the current provider pricing page because rates vary by region and service tier.
Category: cloud
Difficulty: advanced
Related Terms
See Also