FAQ

Issue List

Product Development Issues

1. No matching category is available when creating a product.

   a. Public cloud developers can contact platform support to submit a category request.

   b. Private cloud users can add the needed category on the Cloud Management Platform, then create the product.

2. A custom function does not take effect on the device.

   Confirm that the device firmware implements the custom function and uses the same data-point definition as the product.

3. Voice configuration errors.

   Incorrect mapping type configuration between the Ubases IoT platform and the third-party voice platform.

4. Cannot complete or continue product development.

   a. Check whether function points are configured.

   b. Check whether a module or custom firmware is selected.

   c. Check whether a control panel has been selected.

Device Debugging Issues

1. Device hotspot not discovered.

   a. The device has not entered device-provisioning mode and is not advertising an AP or BLE service. The device may already be provisioned, whether online or offline. Solution: Use the supported AT command, reset/delete-device procedure, or another documented method to put the module into device-provisioning mode. b. The device appears to have entered device-provisioning mode, but the AP or BLE advertisement is not enabled. Solution: Check the firmware logic and logs to confirm that the device actually entered device-provisioning mode and started the required advertisement.

2. Provisioning failed. a. The router password is incorrect, causing device provisioning to time out. b. The device credentials do not match the manufactured product, so server authentication and the MQTT connection fail. c. Domain/port issues when connecting to the cloud. That is, MQTT failed to connect. d. The product was not created in the same cloud environment that the App is logged into.

3. Device failed to connect to MQTT. a. Triplets do not match the product that was manufactured; server authentication failed. That is, MQTT failed to connect. b. Domain/port issues when connecting to the cloud. That is, MQTT failed to connect.

4. Device did not report properties. a. When the device does not report properties, the MCU program may not handle reporting, or the module may have dropped the reported packet while processing (module firmware bug). b. When the device does not report properties, it may also be an MCU reporting logic issue. c. When the device does not report properties, the packet may have been lost during MCU-to-module communication, so the module cannot report the data.

5. Device did not execute correctly after receiving a command. a. When the module has received the command and forwards it to the MCU, the packet may be lost and the MCU never receives it. b. When the module has received the command and forwards it to the MCU, the MCU receives it but the MCU developer has not handled the corresponding Thing Model command (the feature may not exist).

6. Forced upgrade failed. a. The module did not receive correct protocol data. b. Upgrade version number issues. These failure causes can be located via error codes reported by the module.

Deployment Issues

Android build machine deployment issues:

1. After downloading the SDK with sdkmanager, SDK files cannot be found.

   Solution: When using sdkmanager, add the --sdk_root=path parameter to specify the SDK download location.

2. After starting the iot-app-build-service, no build messages are received.

   Solution: Check whether configurations in conf/.env and iot-app-build-service.yml are correct, and whether the addrs service address is correct.

3. During packaging, Git repeatedly asks for a username and password. Solution: Configure the operating system’s secure Git credential manager or use an SSH key. The command git config --global credential.helper store from the original procedure stores credentials unencrypted and is not recommended for production build machines.

Issues that may occur during iOS build machine deployment:

1. npm error: npm ERR! request to https://registry.npmjs.org/amfe-flexible failed, reason: unable to get local issuer certificate.

   Solution: Install the correct corporate or public CA certificate and configure npm’s cafile setting if required. The command npm config set strict-ssl false disables TLS certificate verification and should be used only as a temporary diagnostic step in an isolated environment, never as a permanent production fix.

2. Certificate not found during packaging. Solution: a. Double-click a mobileprovision file. b. Open Terminal from the GUI and run security list-keychains | xargs security list-keychains -s. c. Open Keychain Access and delete all keychains under “Custom Keychains”.

3. Unexpired certificates show as untrusted in Keychain. Solution: Follow https://www.jianshu.com/p/d1d82ffed554, then restart the computer.

Troubleshooting Methods

1. Reproduce the issue.

   Check whether the issue only occurs in specific conditions or regularly; identify reproduction conditions and steps.

2. Locate and analyze the issue.

   On web pages, check the console for errors and locate issues from error messages.

   Log investigation: troubleshoot using backend service logs, device logs, and server logs.

   Follow suggested FAQ workflows to locate the issue.

3. Resolve the issue.

   Based on the located issue, find a solution.

   a. Use help docs to understand the module’s features and implementation.

   b. Check FAQs for a matching solution.

   c. If it is a cloud platform issue, contact Ubases IoT support to report it.