Test Cases

This topic describes the test cases for verifying the functionality of the gateway.

Gateway OTA updates

Update the gateway’s MCU firmware

Test case 1: Update from the installed version to the test version.

• Prerequisites
  • A firmware version has been released. The device is running the latest version.
• Steps
  • On the Tuya IoT Development Platform, configure the target version (test version), choose an app update method, and then add the device ID to the allowlist.
  • Open the app and tap the target device. In the device panel, tap the pencil icon in the top right corner and then check for Device Update. If a new version is available, install it.
• Expected result
  • The device is successfully updated, with the previous status and parameters preserved. All functions work properly.

Test case 2: Update from the test version to a newer version.

• Prerequisites
  • The device is running the test version. Configure a newer version for OTA tests.
• Steps
  • On the Tuya IoT Development Platform, configure the target version (test version), choose an app update method, and then add the device ID to the allowlist.
  • Open the app and tap the target device. In the device panel, tap the pencil icon in the top right corner and then check for Device Update. If a new version is available, install it.
• Expected result
  • The device is successfully updated, with the previous status and parameters preserved. All functions work properly.

Test case 3: Update the firmware after full firmware flashing.

• Prerequisites
  • The device has been flashed with the full firmware and license and is running the test version. Configure a newer version for OTA tests.
• Steps
  • On the Tuya IoT Development Platform, configure the target version, choose an app update method, and then add the device ID to the allowlist.
  • Open the app and tap the target device. In the device panel, tap the pencil icon in the top right corner and then check for Device Update. If a new version is available, install it.
• Expected result
  • The device is successfully updated, with the previous status and parameters preserved. All functions work properly.

Update the gateway’s Zigbee module firmware

Test case 1: Update from the installed version to the test version.

• Prerequisites
  • A firmware version has been released, and the device is running it.
• Steps
  • On the Tuya IoT Development Platform, configure the target version, choose an app update method, and then add the device ID to the allowlist.
  • Open the app and tap the target device. In the device panel, tap the pencil icon in the top right corner and then check for Device Update. If a new version is available, install it.
• Expected result
  • The device is successfully updated, with the previous status and parameters preserved. All functions work properly.

Test case 2: Update from the test version to a newer version.

• Prerequisites
  • The device is running the test version. Configure a newer version for OTA tests.
• Steps
  • On the Tuya IoT Development Platform, configure the target version, choose an app update method, and then add the device ID to the allowlist.
  • Open the app and tap the target device. In the device panel, tap the pencil icon in the top right corner and then check for Device Update. If a new version is available, install it.
• Expected result
  • The device is successfully updated, with the previous status and parameters preserved. All functions work properly.

Scene linkage

Cloud scene

Test case 1: Create and run a cloud linkage.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
  • All gateways are not on the same LAN.
• Steps
  • Open the app and choose Scene > Tap-to-Run. Tap the + icon in the top right corner.
  • Select the sub-devices under different gateways and save.
  • Tap the created tap-to-run.
• Expected result
  • The scene is created and works as expected.

Local scene

Test case 1: Create and run a local linkage.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
• Steps
  • Open the app and choose Scene > Tap-to-Run. Tap the + icon in the top right corner.
  • Select the sub-devices under the same gateway and save.
  • Tap the created tap-to-run.
• Expected result
  • The scene is created and can work with or without internet access.

Zigbee standard scene

Test case 1: Create and bind a standard scene with a scene switch.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
• Steps
  • Open the app and then the Zigbee scene switch panel. Press and hold any control and select a device DP action to create a scene.
  • After the scene is created, bind it with a scene switch button.
• Expected result
  • The scene is created and bound.

Test case 2: Press the physical scene switch to trigger a standard scene.

• Prerequisites
  • Press the physical scene switch button that has been bound with a standard scene.
  • Power off the gateway, trigger the scene switch button, and verify if the scene works as expected.
• Steps
  • Open the app and then the Zigbee scene switch panel. Press and hold any control and select a device DP action to create a scene.
  • After the scene is created, bind it with a scene switch button.
• Expected result
  • All target sub-devices can run the scene properly.

Test case 3: Send a Zigbee standard scene to the sub-device.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
  • Create a Zigbee standard scene using a scene switch.
• Steps
  • Open the app and then the scene switch panel. Tap the switch that is bound with a standard scene.
• Expected result
  • All target sub-devices can run the scene properly.

Test case 4: Query device status after a Zigbee standard scene is run.

• Prerequisites
  • All the devices have joined the network. The internet is connected.
  • Support for sub-devices that cannot proactively report their status.
• Steps
  • After N devices join the network, create N Zigbee standard scenes, with one DP added per device.
  • Trigger the created Zigbee standard scenes.
  • Wait for a while and verify the status of all devices in the group on the panel.
• Expected result
  • After a delay (15 seconds for Zigbee and 3 seconds for Bluetooth), the gateway begins polling and eventually synchronizes the status of all devices.

Test case 5: Modify a Zigbee standard scene.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
  • Create a Zigbee standard scene using a scene switch.
• Steps
  • Create a Zigbee standard scene using a scene switch and bind it with a scene switch button.
  • When the gateway and devices are online, modify and save the Zigbee standard scene on the app.
  • Press the physical scene switch button that is bound with this scene.
• Expected result
  • The updated standard scene is run.

Test case 6: Delete a Zigbee standard scene.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
  • Create a Zigbee standard scene using a scene switch.
• Steps
  • Create a Zigbee standard scene using a scene switch and bind it with a scene switch button.
  • When the gateway and devices are online, delete the Zigbee standard scene on the app.
  • Check the button configuration of the scene switch on the app, and trigger the button bound with the deleted scene.
• Expected result
  • The button configuration is reset, and no action is performed when the button is activated.

Cloud linkage

Test case 1: Create and run a cloud linkage.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Open the app and choose Scene > Automation. Tap the + icon in the top right corner.
  • Add a condition: Choose When Device Status Changes and select a device action.
  • Add a task: Choose Control Single Device. Select the action of a device on a different LAN and Save.
  • Choose When any condition is met for the validity scope. Then, add another condition of When Device Status Changes and select a device on a different LAN. Tap Save and then Yes on the prompt.
  • Traverse and trigger any condition action, and check if the specified task is executed.
• Expected result
  • The automaton can be saved and executed correctly, but it fails to run when the internet is disconnected.

Local linkage

Test case 1: Create and run a local linkage.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The mobile phone and the gateway are on the same LAN.
• Steps
  • Open the app and choose Scene > Automation. Tap the + icon in the top right corner.
  • Add a condition: Choose When Device Status Changes, select a condition, and Save.
  • Add a task: Choose Control Single Device. Select the action of a device on the same LAN. Tap Save and then Yes on the prompt.
  • Trigger the condition action and check if the specified task is executed.
  • Tap Validity Scope > Effective Period > Custom. Set an appropriate start and end time and the Repeat pattern.
  • Trigger the condition action within and outside the effective period respectively and check if the specified task is executed.
• Expected result
  • The gateway takes over the automation locally when the effective period is all day or custom. When the condition action is triggered during the preset effective period, the specified task is executed. When the condition action is triggered outside the preset effective period, the specified task is not executed.
  • The specified task can be executed with or without internet access. There is a Local Linkage flag in the top left corner of the automation details page.

LAN linkage

Test case 1: Create and run a LAN linkage.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
  • Connect all the gateways to the same router to form a LAN. Prepare a main gateway, a node device, and several sub-devices.
• Steps
  • Open the app and choose Scene > Automation. Tap the + icon in the top right corner.
  • Add a condition: Choose When Device Status Changes, select a condition, and Save.
  • Add a task: Choose Control Single Device. Select the action of a device on the same LAN but under a different gateway. Tap Save and then Yes on the prompt.
  • Trigger the condition action, check if the specified task is executed, and disconnect the internet.
• Expected result
  • The specified task can be executed with or without internet access. There is a LAN Linkage flag in the top left corner of the automation details page.

Group

Create a group

Test case 1: Create a group.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Select devices that support grouping on the app.
  • All devices are connected to the same gateway.
  • Group the devices of the same type.
• Expected result
  • The group is created.

Control a group over LAN

Test case 1: Control a group over LAN

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Create a group and connect all devices in the group to the LAN.
  • Connect the mobile phone to the same router as the gateway, disconnect the internet access of the router, and control the group.
• Expected result
  • The group can be controlled over the LAN.

Control a group over internet

Test case 1: Control a group over internet

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Create a group and connect all devices in the group to the internet.
  • Control the group.
• Expected result
  • The group can be controlled.

Query a group

Test case 1: Query a group.

• Prerequisites
  • All the devices have joined the network.
• Steps
  • After N devices join the network, create a group for these devices.
  • Trigger the group.
  • Check the device status on the app.
• Expected result
  • The gateway begins polling after a delay and eventually synchronizes the status of all devices. After a 15-second delay, the gateway queries and synchronizes the status at a rate of one device per second until all devices are polled.

Dismiss a group

Test case 1: Dismiss a group.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Open the edit page of the group on the app and dismiss the group.
• Expected result
  • The group is dismissed and does not exist on the device list.

Gateway failover

Test case 1: Gateway failover.

• Prerequisites
  • The gateway has been paired and can connect to the internet.
  • The gateway has added sub-devices, groups, standard scenes, and automations, all of which have been backed up.
• Steps
  • Power off the faulty gateway and wait for it to go offline.
  • Open the app and tap the target device. On the page of device details, tap Replace Faulty Gateway.
  • Wait for a while and check the new gateway for recovering sub-devices, groups, scenes, and automations. Verify the basic functions such as controlling and adding sub-devices.
• Expected result
  • The sub-devices, groups, scenes, and automations of the new gateway work properly.

Gateway’s Zigbee channel

Test case 1: Report the gateway’s Zigbee channel.

• Prerequisites
  • The gateway has been paired and can connect to the internet.
• Steps
  • Use packet capture to get the channel ID used for gateway pairing.
  • The gateway has been paired. Open the gateway panel and tap the top right corner of the screen to open device information.
  • Check if the channel information exists and, if it does, verify if it matches the one obtained in step 1.
• Expected result
  • The channel information is present in the device information and matches the one obtained in step 1.

Gateway pairing

Enter pairing automatically upon initial power-on

Test case 1: Pairing mode upon initial power-on.

• Prerequisites
  • The gateway has not been paired after it is flashed with the firmware.
  • The gateway is not powered on.
• Steps
  • Power on the gateway.
• Expected result
  • The gateway enters pairing mode automatically after startup.

Wired pairing

Test case 1: Add a gateway manually in wired pairing mode.

• Prerequisites
  • The gateway enters pairing mode.
  • The mobile phone and the gateway are on the same LAN.
• Steps
  • Tap Add Device on the app.
  • Locate and select the target gateway device from the device list.
  • Add the gateway as instructed.
• Expected result
  • The app prompts that the gateway is added successfully.
  • You can open the gateway panel.
  • The added gateway is displayed in the device list on the homepage.
  • Tapping on the gateway in the device list will open the gateway panel.

Test case 2: Add a gateway automatically in wired pairing mode.

• Prerequisites
  • The gateway enters pairing mode.
  • The mobile phone and the gateway are on the same LAN.
  • Do not turn on Bluetooth on the mobile phone.
• Steps
  • Tap Add Device on the app.
  • Wait for the app to scan for nearby devices.
  • When the gateway is found, tap Next to add it.
• Expected result
  • The app prompts that the gateway is added successfully.
  • You can open the gateway panel.
  • The added gateway is displayed in the device list on the homepage.

Wi-Fi AP pairing

Test case 1: Add a gateway manually in Wi-Fi AP pairing mode.

• Prerequisites
  • The gateway enters AP pairing mode.
  • The mobile phone and the gateway are connected to the same 2.4 GHz Wi-Fi network.
• Steps
  • Tap Add Device on the app.
  • Locate and select the target gateway device from the device list.
  • Add the gateway as instructed.
• Expected result
  • The app prompts that the gateway is added successfully.
  • You can open the gateway panel.
  • The added gateway is displayed in the device list on the homepage.

Bluetooth pairing

Test case 1: Add a gateway automatically in Bluetooth pairing mode.

• Prerequisites
  • The gateway is open for pairing.
  • Bluetooth on the mobile phone is turned on.
• Steps
  • Tap Add Device on the app.
  • Wait for the app to scan for nearby devices.
  • When the gateway is found, tap Next, select a Wi-Fi network, and enter the password.
• Expected result
  • The app prompts that the gateway is added successfully.

Gateway online/offline

Test case 1: Gateway online/offline.

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
  • The gateway has added a sub-device.
  • The mobile phone and the gateway are connected to separate LANs.
• Steps
  • Disconnect the gateway from the internet and then check the gateway status on the app.
  • Connect the gateway to the internet.
• Expected result
  • The gateway and its sub-devices show offline on the app about three minutes after the internet connection is lost.
  • The gateway and its sub-devices show online on the app about 30 seconds after the internet connection is restored.

Remove a gateway

Reset a gateway locally

Test case 1: Reset the gateway using the physical button.

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • Press and hold the reset button on the gateway for X seconds to reset it. X: Set the duration based on the hardware reset requirements. It is generally set to five seconds.
• Expected result
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • The gateway has been removed from the device list on the app.
  • If Bluetooth Low Energy (LE) and Bluetooth mesh sub-devices have been connected to the gateway, they still appear on the device list on the app’s homepage. Sub-devices using other protocols such as Zigbee, Thread, and Sub-GHz will be removed from the device list but will remain connected without being reset.

Pair a gateway after a local reset

Test case 1: After resetting a gateway using the physical button, add it to its previous account and home.

• Prerequisites
  • The gateway has been paired, with a sub-device connected.
  • The gateway is started.
• Steps
  • Press and hold the reset button on the gateway for X seconds to reset it. X: Set the duration based on the hardware reset requirements.
  • After resetting the gateway, check its pairing mode. Then, on the app, choose the respective pairing mode and add the gateway to its previous account and home again.
• Expected result
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • The app prompts that the gateway is removed successfully.
  • The gateway is paired and correctly indicates its status.
  • After the gateway is paired, the data of the sub-device is recovered from the preserved data.
  • The custom name of the sub-device’s DP is recovered. The sub-device is online and controllable. All scenes and automations are back and work properly.

Remove a gateway from the app (disconnect)

Test case 1: Remove a gateway from the app (disconnect).

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • On the app, select the gateway from the device list and open the gateway details page. Tap Remove Device > Disconnect > Confirm.
• Expected result
  • The gateway has been removed from the device list on the app.
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • If Bluetooth Low Energy (LE) and Bluetooth mesh sub-devices have been connected to the gateway, they still appear on the device list on the app’s homepage. Sub-devices using other protocols such as Zigbee and Sub-GHz will be removed from the device list.

Pair a gateway after removing it from the app (disconnect)

Test case 1: After removing a gateway from the app, add it to its previous account and home again.

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • On the app, select the gateway from the device list and open the gateway details page. Tap Remove Device > Disconnect > Confirm.
  • After removing the gateway, check its pairing mode. Then, on the app, choose the respective pairing mode and add the gateway to its previous account and home again.
• Expected result
  • The gateway has been removed from the device list on the app.
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • The gateway is paired and correctly indicates its status.
  • After the gateway is paired, the data of the sub-device is recovered from the preserved data.
  • The custom name of the sub-device’s DP is recovered. The sub-device is online and controllable. All scenes and automations are back and work properly.

Remove a gateway from the app (disconnect and wipe data)

Test case 1: Remove a gateway from the app (disconnect and wipe data).

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • On the app, select the gateway from the device list and open the gateway details page. Tap Remove Device > Disconnect and Wipe Data > Confirm.
• Expected result
  • The gateway has been removed from the device list on the app.
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • If Bluetooth Low Energy (LE) and Bluetooth mesh sub-devices have been connected to the gateway, they still appear on the device list on the app’s homepage. Sub-devices using other protocols such as Zigbee and Sub-GHz will be removed from the device list and enter pairing mode.

Pair a gateway after removing it from the app (disconnect and wipe data)

Test case 1: After removing a gateway from the app with its data cleared, add it to its previous account and home again.

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • On the app, select the gateway from the device list and open the gateway details page. Tap Remove Device > Disconnect and Wipe Data > Confirm.
  • After removing the gateway, check its pairing mode. Then, on the app, choose the respective pairing mode and add the gateway to its previous account and home again.
• Expected result
  • The gateway has been removed from the device list on the app.
  • The gateway enters pairing mode and indicates its status based on the product specifications.
  • The gateway is paired and correctly indicates its status.
  • After the gateway is paired, the data of the sub-device is not preserved. A factory reset command is sent to the gateway, and the sub-device data is cleared from the cloud.

Sub-device management

Add a sub-device

Test case 1: Add a sub-device

• Prerequisites
  • The gateway has been paired.
  • The gateway is started.
• Steps
  • On the app, tap the + icon in the top right corner and select the target sub-device.
  • Trigger sub-device pairing.
• Expected result
  • The sub-device is paired and appears in the device list. It can receive commands and report data as expected.

Remove a sub-device

Test case 1: Remove a sub-device

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • On the device panel, tap the pencil icon in the top right corner. Choose Remove Device > Disconnect.
• Expected result
  • The device is removed from the device list and leaves the network. The Tap-to-Run and automation associated with this device cannot work.

Test case 2: Reset a sub-device locally.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Press and hold the reset button on the sub-device until it leaves the network.
  • Check the device list.
• Expected result
  • The device is still in the device list, but immediately shows offline. Its Tap-to-Run and automation data will be preserved.

Test case 3: Automatic restore after a sub-device is locally reset (prevent accidental reset)

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet. The sub-device supports protection against accidental reset.
• Steps
  • Press and hold the reset button on the sub-device until it leaves the network. Then, wait for the pairing timeout.
  • Check the device list and verify the basic functionality of the device.
• Expected result
  • The device reconnects to the previous network and shows online on the app. All its functions, groups, scenes, and automations work correctly.

Sub-device online/offline

Test case 1: Power off a mains-powered device to put it offline.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Power off the device for about N minutes.
  • View the device status on the app.
• Expected result
  • The device shows offline on the panel. You can set the N time based on your needs.

Test case 2: Power on a mains-powered device to put it online.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Power on the device that has been powered off and offline.
  • View the device status on the app.
• Expected result
  • The app will show the device online shortly.

Test case 3: Power off a low power sensor to put it offline.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Power off the device for about 12 hours.
  • View the device status on the app.
• Expected result
  • The device shows offline on the panel.

Test case 4: Power on a low power sensor to put it online.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Power on the device that has been powered off and offline.
  • View the device status on the app.
• Expected result
  • The app will show the device online shortly.

Sub-device reports and receives data

Test case 1: A sub-device reports status.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Operate the sub-device or change the status of the sub-device to trigger status reporting.
• Expected result
  • The sub-device status shown on the app panel matches the actual status.

Test case 2: A sub-device reports status over LAN.

• Prerequisites
  • The sub-device and gateway have been paired and disconnected from the internet.
• Steps
  • The app and the gateway are on the same network, while the router is disconnected from the internet.
  • Operate the sub-device or change the status of the sub-device to trigger status reporting.
• Expected result
  • The sub-device status shown on the app panel matches the actual status.

Test case 3: Send a command to a sub-device.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Send a command to a sub-device using the device panel.
• Expected result
  • The sub-device receives and acts on the command. Its status shown on the app panel matches the actual status.

Test case 4: Send a command to a sub-device over LAN.

• Prerequisites
  • The sub-device and gateway have been paired and disconnected from the internet.
• Steps
  • The app and the gateway are on the same network, while the router is disconnected from the internet.
  • Send a command to a sub-device using the device panel.
• Expected result
  • The sub-device status shown on the app panel matches the actual status.

Sub-device OTA updates

Test case 1: Update a mains-powered sub-device from the installed version to the test version.

• Prerequisites
  • The gateway has been paired.
  • The sub-device has joined the network.
  • Configure a firmware version for the sub-device on the Tuya IoT Development Platform.
• Steps
  • Configure the update deployment on the Tuya IoT Development Platform.
  • Initiate the update on the app.
• Expected result
  • The app prompts that the update is installed successfully.
  • The device status remains unchanged after the update.
  • The parameters are preserved.
  • The sub-device works properly.

Test case 2: Update a sub-device’s MCU from the installed version to the test version.

• Prerequisites
  • The sub-device and gateway have been paired and can connect to the internet.
• Steps
  • Configure the update deployment on the Tuya IoT Development Platform. Update the MCU on the sub-device that runs the generic firmware.
• Expected result
  • The OTA update is successful.

Bluetooth sub-device

Test case 1: Drag a sub-device into a gateway.

• Prerequisites
  • The gateway is online.
• Steps
  • Turn on the Bluetooth on the mobile phone and add a Bluetooth sub-device to the app.
  • Turn off the Bluetooth on the mobile phone and then drag the Bluetooth sub-device into the gateway.
• Expected result
  • The Bluetooth sub-device is paired.
  • The Bluetooth sub-device is added to the gateway.

Test case 2: Drag a sub-device out of a gateway.

• Prerequisites
  • The gateway and sub-device are online.
• Steps
  • Drag the added Bluetooth sub-device out of the gateway to the app.
  • For the Bluetooth sub-device that has been dragged into the gateway from the app or a different gateway, drag it from the gateway into the app.
• Expected result
  • The operation is successful.

Test case 3: Migrate a sub-device to another gateway.

• Prerequisites
  • The gateway and sub-device are online.
• Steps
  • Initiate migration on the app.
  • Select the sub-device to be migrated.
  • Select the target gateway.
  • Tap Cancel or OK.
• Expected result
  • You can select one or all the sub-devices.
  • You can migrate the sub-device with options including single, room, all, and custom.
  • The name and online status of the target gateway are shown.
  • Tapping Cancel stops the migration. Tapping OK starts the migration. The app prompts that X devices are migrated when the migration is done.

Test case 4: Add a gateway first and then a sub-device. The sub-device is automatically associated with the gateway (for Bluetooth mesh and Bluetooth beacon).

• Prerequisites
  • There is one gateway in the home.
• Steps
  • Add a gateway and then a sub-device. The number of added sub-devices does not exceed the limit imposed by the gateway.
  • Add a gateway and then a sub-device. The number of added sub-devices exceeds the limit imposed by the gateway.
• Expected result
  • The sub-devices are automatically associated with the gateway.
  • The automatic association does not apply. You are navigated to a multi-gateway dialog to associate the sub-device with the gateway manually.

Test case 5: Add a sub-device first and then a gateway. The sub-device is automatically associated with the gateway (for Bluetooth mesh and Bluetooth beacon).

• Prerequisites
  • There is one gateway in the home.
• Steps
  • Add a sub-device and then a gateway. The number of added sub-devices does not exceed the limit imposed by the gateway.
  • Add a sub-device and then a gateway. The number of added sub-devices exceeds the limit imposed by the gateway.
  • Add quick access to associate with sub-devices on the gateway card.
• Expected result
  • The sub-devices are automatically associated with the gateway.
  • The automatic association does not apply. You are navigated to a multi-gateway dialog to associate the sub-device with the gateway manually.
  • Add quick access to associate with sub-devices on the gateway card.

Test case 6: Disassociate a sub-device from a gateway.

• Prerequisites
  • The gateway and sub-device are online.
• Steps
  • Initiate disassociation on the app.
  • Select the target sub-device.
• Expected result
  • You can select one or all the sub-devices.
  • You can disassociate the sub-device from the gateway with options including single, room, all, and custom.

Test case 7: Get the signal strength of a mains-powered Bluetooth sub-device from the gateway panel.

• Prerequisites
  • The gateway and sub-device are online.
• Steps
  • Check the signal strength of a Bluetooth mesh sub-device.
  • Check the signal strength of a Bluetooth LE sub-device.
• Expected result
  • The app shows the current signal strength, which can be excellent, good, average, poor, very poor, and unable to obtain.
  • If the signal strength is good, average, poor, or very poor, the app prompts that the communication quality between the device and the gateway is not ideal. To optimize signal quality, try moving the device or removing any obstacles between them.
  • If the signal strength cannot be obtained, the app prompts that the low-power device should be woken up in advance. Otherwise, the signal data can be inaccurate.

Upstream network

Wi-Fi

Test case 1: Switch to the Wi-Fi network currently connected to the mobile phone.

• Prerequisites
  • The gateway has been paired.
  • The app supports network switching.
  • The firmware supports network switching.
• Steps
  • The gateway has been paired using an app that supports Wi-Fi switching. Connect your mobile phone to a different Wi-Fi network than the one connected to the gateway. Then, open the device network page.
  • On the app, tap Set Network > Device Network > Current Mobile Network and then switch to another Wi-Fi network.
• Expected result
  • You can switch to the Wi-Fi network currently connected to the mobile phone simply by entering the password.
  • After successful switching, the Wi-Fi EZ information is updated. The gateway is connected to the new Wi-Fi network after a restart. During the switching process, there are no anomalies with the gateway.

Test case 2: Add a different SSID.

• Prerequisites
  • The gateway has been paired.
  • The app supports adding alternative networks.
  • The firmware supports adding alternative networks.
• Steps
  • The gateway has been paired using an app that supports adding alternative networks. Open the device network page.
  • On the app, tap Set Network > Device Network and then add a different AP.
• Expected result
  • The alternative network is added, with the information updated accordingly. The gateway stores the alternative network. There are no anomalies with the gateway during the process.

Test case 3: Report Wi-Fi signal strength.

• Prerequisites
  • The gateway has been paired.
  • The gateway supports Wi-Fi and uses Wi-Fi for upstream communication.
• Steps
  • Open the app, tap Device Details > Device Information > Signal Strength, and check the device’s Wi-Fi signal strength.
• Expected result
  • The device reports the Wi-Fi signal strength properly, and the app correctly displays it.