Cancel

Matter over Thread Troubleshooting

Last Updated on：2024-01-19 07:23:23

This topic describes the common issues with Matter over Thread development and solutions to them.

Module resources and usage

Timer: The module does not have a hardware timer. You can create software timers using the same method as with FreeRTOS.
RAM: 192 KB. Flash: 1.5 MB. Approximately 50 KB is available for application development.

Device pairing

Before pairing a device over Bluetooth, the system Bluetooth must be turned on.
A device remains in pairing mode for a specified time period.
To pair a device again after a failure, it is recommended to restart the device and then activate the pairing mode.

Online and offline

The gateway regularly sends heartbeat packets to mains-powered devices. If a device fails to respond to the heartbeat check multiple times consecutively, it will be shown as offline on the mobile app. Manufacturers have their specific implementations of heartbeat policies. Therefore, the heartbeat interval and the number of retries before declaring a device offline vary by manufacturer. For mains-power devices, the offline time typically ranges from a few seconds to several minutes.
For low power devices, their offline status is determined by the occurrence of proactive data reporting. If the gateway does not receive a data reporting message from a device within the specified period consecutively, it will declare it offline. The offline time for a low power device typically ranges from tens of minutes to several hours. For example, the offline time specified for Tuya-enabled devices is 12 hours.

Network capacity

The test results indicate that a stable Thread network can support up to 64 connected devices.

Module consumption in low power

Test item	Average measurement
Static power consumption in sleep mode(not connected)	3.28 μA
Static power consumption in sleep mode(connected)	3.16 μA
Power consumption in network scan	2.36 mA (quick scan), 1.02 mA (slow scan)
Data reporting peak	30.95 mA
Power consumption for a poll request	-
Power consumption for data reporting woken up by button	619.03 nWh
Power consumption for data reporting woken up by heartbeat	576 nWh
Average current in OTA update	4.48 mA

Logic for low power devices

Low power devices are in sleep mode most of the time. Data exchange occurs in two ways:

Report data: The device reports data after being woken up by a timer or a button press.
Receive commands: The device cannot receive commands in sleep mode. After sending a command, the gateway can either wake up the device or wait for the device to wake up autonomously.

The retransmission mechanism may cause the gateway to resend a command multiple times, leading to multiple cached commands. Therefore, after wake-up, the device will receive multiple commands.

Module range test

HeadThread PIRpowered by regulated 3.3Vin basement level 2	Report data 20 timesPower cycle and reconnect 10 times
Distance	70m, 80m, 90m
Success rate of data reporting	100%, 100%, 100%
Success rate of reconnect attempt	100%, 100%, 100%