RF Wireless World

Browse articles, tutorials, tools, and vendors.

SIT vs LIT: Matter Over Thread IoT Configurations

By RF Wireless Expert Team

Introduction : In the rapidly evolving smart home ecosystem, the Matter protocol (running over Thread) has emerged as the gold standard for secure, interoperable and low power wireless connectivity.

However, designing battery powered Matter devices like smart locks, temperature sensors or window blinds presents a unique engineering challenge i.e.”How do you keep a device connected to the network without draining its battery in a matter of days?”

The Matter specification solves this by defining Intermittently Connected Devices (ICDs). Instead of keeping their radios on constantly, ICDs spend most of their time in an ultra-low power sleep state. Depending on what the device actually does, developers must choose between two distinct application layer configurations viz. SIT (Short Idle Time) and LIT (Long Idle Time).

Let us explore differences between SIT and LIT, and how to choose the right configuration to optimize your smart home device’s battery life and responsiveness.

What is SIT (Short Idle Time)?

SIT is a configuration designed for devices that need to be highly responsive to user commands. By definition within the Matter specification, a SIT device sleeps for less than 15 seconds at a time before waking up to check for messages from the network (its Thread parent/router).

  • SIT is ideal for actuators. These are devices that perform a physical action based on a user’s command.

  • Example: A smart door lock or a smart light switch. When a homeowner presses “Unlock” on their smartphone app, they expect the door to unlock almost instantly. The brief sleep interval of a SIT configuration ensures the device receives the command with minimal latency, providing a seamless user experience.

What is LIT (Long Idle Time)?

LIT is a configuration built for maximum energy conservation. A LIT device sleeps for more than 15 seconds, typically ranging from several minutes up to a maximum of 18 hours. Because it sleeps for so long, the Matter controller cannot reach the device on demand. Instead, the network must wait for the LIT device to wake up and initiate communication.

Because of this extended sleep behavior, LIT devices must support two additional features as follows.

  1. Check-In Protocol (CIP): A mechanism the LIT device uses upon waking up to notify client devices (like a smart home hub) that it is currently awake and available to receive queued messages.
  2. User Active Mode Trigger (UAT): A physical trigger (like pressing a button on the device) that forces the device to wake up and enter an active mode, which is usually necessary for initial network commissioning or firmware updates.
  • LIT is ideal for sensors which are devices that only need to report data periodically or when a specific event occurs.
  • Example: A Carbon Monoxide (CO) detector or an ambient temperature sensor. A temperature sensor might only need to wake up every 30 minutes to report the climate, allowing it to run on a simple coin cell battery for years.

Key Differences Between SIT and LIT

FeatureSIT (Short Idle Time)LIT (Long Idle Time)
Sleep DurationLess than 15 seconds.Greater than 15 seconds (up to 18 hours).
Primary RoleActuators (locks, blinds, switches).Sensors (temperature, motion, smoke alarms).
ResponsivenessHigh (Near real time).Low (Asynchronous, relies on device check-ins).
Power ConsumptionModerate to Low.Ultra-Low (Maximized battery life).
Required ProtocolsStandard polling.Requires Check-In Protocol (CIP) & User Active Mode Trigger (UAT).

The Lower Layer Impact: SED vs. SSED

While SIT and LIT are configurations at the “Matter application layer”, battery life is also heavily dictated by how the device behaves at the “Thread network layer”. Thread uses two main methods for sleeping devices.

  • Sleepy End Device (SED): The device wakes up periodically and blindly asks its parent router, “Do you have data for me?” This periodic polling is simple and reliable but can waste energy if the device frequently wakes up only to find no data waiting.
  • Synchronized Sleepy End Device (SSED): The device and the parent router agree on a synchronized schedule. The device only turns on its radio during highly specific, scheduled communication windows. This drastically reduces unnecessary radio usage, saving significant battery power, though it requires highly precise timing from the hardware.

How to Optimize Battery Life and Responsiveness in Matter Devices

To build a successful Matter over Thread product, developers must strike the perfect balance between user experience (i.e. responsiveness) and hardware constraints (i.e. battery capacity). Here are the best practices for optimization.

1. Match the Configuration to the Device Type

Never use a SIT configuration for a device that doesn’t require immediate user interaction. Forcing a simple humidity sensor to wake up every 5 seconds will needlessly drain its battery. Reserve SIT strictly for devices where latency breaks the user experience (like a door lock).

2. Utilize Modern, High Efficiency Hardware

Choice of wireless System on Chip (SoC) dictates baseline power consumption. Look for next-generation multiprotocol SoCs (e.g. Nordic nRF54L series) that feature modern architectures (like Arm Cortex-M33 processors) built on smaller process nodes (e.g. 22nm). These chips process data incredibly fast, meaning the radio is active for a shorter period, allowing the device to return to its ultra-low power sleep state faster.

3. Implement Dedicated Power Management

Don’t rely solely on the SoC’s internal power routing. Integrating a dedicated Power Management IC (PMIC) especially for devices running on primary cells like AA or AAA batteries ensures that maximum energy is extracted from the battery. Modern PMICs also offer hardware level hibernate modes and highly accurate fuel gauging without taxing the main processor.

4. Leverage SSED and SDK Tools

Whenever possible, utilize Synchronized Sleepy End Device (SSED) network behaviors rather than standard SEDs to minimize “empty” data polling. Furthermore, take advantage of mature Software Development Kits (SDKs). Providers often include energy optimized sample code for specific devices (e.g. a pre-configured SIT door lock sample or a LIT CO alarm sample) that takes the guesswork out of radio scheduling.

Conclusion

Understanding the distinction between SIT and LIT is the foundational step in developing a Matter over Thread device. By carefully aligning your device’s application layer configuration with its real world use case and backing it up with highly efficient hardware and synchronized network behaviors, you can deliver smart home accessories that respond instantly when needed while lasting years on a single battery.

Compare Matter With Other Technologies

Continue Learning Matter Protocol

Continue Learning Legacy Wi-Fi (IEEE 802.11b/a/g)

Explore Advanced WLAN Versions : Next Gen. Wi-Fi 4/5/6/7 & 8

Continue Learning THREAD Technology

Compare THREAD With Other Technologies

Keep Reading

Related Posts