[Free trial of Pingtouge Bluetooth Mesh Gateway Development Kit] + Gateway module and sub-device cloud platform and problem solving supplement

damiaa

[Free trial of Pingtouge Bluetooth Mesh Gateway Development Kit] + Gateway module and sub-device cloud platform and problem solving supplement [Copy link]

[Free trial of Pingtouge Bluetooth Mesh Gateway Development Kit] + Gateway module cloud platform and problem solving supplement

I have been testing this thing for the past two weeks. I encountered some problems and summarized them to avoid mistakes made by others.

1. The initial SDK 1.0 of the gateway and the SDK released on October 31 on Pingtouge OCC can run until the mobile phone can use cloud intelligence to search and join. This is certain .

2. When setting up the app in the device settings of the Life Cloud Platform, you must select the free public version app. Otherwise, Cloud Intelligence will not be able to search.

3. The equipment of the Life Cloud Platform must be completed until it is released. It seems that debugging is also possible. Please pay attention here.

4. If the device of the Life Cloud Platform is not connected to the gateway or device, it will show as unactivated. After joining, it will show as activated. After joining, when you power on, you can see that it is online. And when you power on, the log will be printed. There are also events and so on.

You can check to see if your gateway is connected to the cloud. If there is no response, then you need to work harder.

5. When connecting the five-tuple elements of the Life Cloud Platform to OCC, please note that there are two that are easily confused: productssecret and devicesecret. It is easy to be deceived. The gateway has five parameters and the device has four parameters.

6. I don’t know how to configure the fota and physical model in occ, so I ignored it.

7. When compiling the gateway program, there is an aft_build.sh file copied to: ... \gateway_released_sdk\solutions\ble_mesh_gateway_demo\script. I forgot about it when I deleted it and started over.

I copied it to boardsgateway_released_sdk\boards\IoTGW_CB800. Because there is also such a file in it. I am confused. I fell into the trap .

8. W800 Upgrade Tools should be used after 1.37. The latest version 1.48 can be used. The old 1.0 version cannot erase the program's kp, but can burn the kp for the first burn. Don't use it!!! Huge pit.

I got stuck on this issue. The first time I burned it in, the gateway connected. The second time I burned it, it was still the kp of the first time. At that time, I didn't know whether the kp was still the first time, I just knew that the latter one could not connect to the gateway. I was suspicious everywhere. Later, it was the technical support who gave me guidance.

9. The gateway board has two ports, one is J2 which prints a lot of logs when powered on, and the other is J1 which prints very little. The AT command is input from J1. You can't mix them . It's best to use OCC Gateway Config Tool to switch to the send command of device management to send. Of course, serial port software such as putty can also be used.

10. Sub-device joining test: Refer to the quick reference manual to enter the command in the at command input port of the gateway, and then wait for a while to scan and join in the life Internet of Things. The input command is as follows

AT+MESHAT=1 /* Enable AT. Usually used when starting to enter AT commands, otherwise the following commands may not be executed*/

/* Configure gateway */

AT+MESHPROVCONFIG=1,FF

AT+MESHPROVAUTOPROV

AT+MESHPROVEN=1

/* Scan nodes */

AT+MESHPROVSHOWDEV=1 /* Scan nodes. Note that the node information you want to bind will be scanned here, and you can copy it when you use it later */

AT+MESHPROVSHOWDEV=0 /* Stop scanning nodes after scanning nodes. No need to keep scanning */

/* Bind a node and copy the node information scanned previously */

AT+MESHADDDEV=00:E0:4C:00:00:03,00,9402820d00e04c000003b106000000000,00,01 /* The mac address and uuid information here need to be copied from the scanned information * /

/* Configure the node */

AT+MESHAUTOCONFIG=0x0002 /*After executing the above command, there will be a response: such as reply +MESHAPPKEYADD:0002, 0 0002 is the actual unicast addr of the device . Unicast addr is the device in the binding

After confirming, reply + MESHAPPKEYADD:0002 , the first parameter in 0 */ Don’t make a mistake.

11. One more thing, if you make a mistake in input, remember to restore the factory settings . Method: Refer to the BLE_MESH_AT_MODULE manual for instructions

1) Gateway: Use AT command: AT+RST or re-burn the W800 program. It is best to remove the sub-device from the network when restoring. Check the operation command below and then remove it.

AT+MESHGETNODEINFO=0xxxxx Get node information 0xxxxx is the node unicast address

AT+ MESHRST=0xxxxx remove node

2) Reset the slave device 5 times (2 to 3 seconds each time) or re-burn the program.

3) After the gateway is added, you can see that the device and sub-device are online on Alibaba Life Network, and the gateway has a sub-device. The device and sub-device can also be added to the cloud smart app. The app can control the sub-device lights, and the light switches can also be seen changing synchronously on the cloud.

I would like to thank Alibaba for its technical support.

soso

The highlighted part is the emphasized part and it is clear.

damiaa

I tried it at night and added lighting equipment.