CV06iR Smart Watch data on DSGW-040

Technical Support DSGW-040
1

Hi, I have 4 CV06iR Smart Watch devices from DUSUN that are automatically configured to send readings via the DSGW-040. The CV06iR Smart Watch Spec-V2.1.pdf document shows a default example flow for this device. However, none of the devices I have are sending data. You can see in my log traces that the BLE scanner is detecting but is unable to connect to these devices.

AWS IOT is showing the device scans and the failures to connect.

Screenshot 2023-10-10 at 2.37.13 PM
Screenshot 2023-10-10 at 2.37.13 PM615×502 67.8 KB

Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] uproto_handler_ubus_event: -----------------[ubus msg]: handler ....-----------------
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] aws_gw_dev_code_get: load device code ok, dev code:aws_device_code
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] _rpt_attr: through out to w:len:269 [{"from": "BLE", "mac": "30:ae:7b:e5:fa:6c", "to": "GATEWAY", "data": {"attribute": "BLE_connect_status", "value": {"mac": "F7:34:FB:31:D5:42", "connect_id": 1}, "mac": "F7:34:FB:31:D5:42"}, "deviceCode": "aws_device_code", "type": "reportAttribute", "time": 1696965172}]
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] mqtt_aws_publish:
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] _rpt_attr: ret:0
Tue Oct 10 19:12:52 2023 local0.warn /usr/bin/mqtt-gw: [warning] mqtt_gw_dev_code_get: load device code failed, open file:/etc/dusun/device_code failed
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] _rpt_attr: through out to m:len:254 [{"from": "BLE", "mac": "30:ae:7b:e5:fa:6c", "to": "GATEWAY", "data": {"attribute": "BLE_connect_status", "value": {"mac": "F7:34:FB:31:D5:42", "connect_id": 1}, "mac": "F7:34:FB:31:D5:42"}, "deviceCode": "", "type": "reportAttribute", "time": 1696965172}]
Tue Oct 10 19:12:52 2023 local0.debug /usr/bin/mqtt-gw: [debug] mqtt_gw_send_message: -- 1
Tue Oct 10 19:12:52 2023 local0.debug /usr/bin/mqtt-gw: [debug] mqtt_gw_send_message: -- 2
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] _rpt_attr: ret:4
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/mqtt-gw: [info] uproto_handler_ubus_event: -----------------[ubus msg]: handler over-----------------
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/bul: [info] gk_rsp_evt_handler: /sl/msg/sl_bt_evt_connection_phy_status_id
Tue Oct 10 19:12:52 2023 local0.debug /usr/bin/bul: [debug] $this: pop mac:F7:34:FB:31:D5:42
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/bul: [info] gk_rsp_evt_handler: /sl/msg/sl_bt_evt_connection_tx_power_id
Tue Oct 10 19:12:52 2023 local0.info /usr/bin/bul: [info] gk_rsp_evt_handler: /sl/msg/sl_bt_evt_connection_remote_used_features_id
Tue Oct 10 19:12:53 2023 local0.info /usr/bin/bul: [info] $this: ********devcnt:30, delt:2 ms
Tue Oct 10 19:12:54 2023 local0.debug /usr/bin/bul: [debug] scan_hold_beacon_handler: CONNECTTED DEVICE BEACON ING....
Tue Oct 10 19:12:54 2023 local0.info /usr/bin/mqtt-gw: [info] uproto_handler_ubus_event: -----------------[ubus msg]: handler ....-----------------
Tue Oct 10 19:12:54 2023 local0.info /usr/bin/mqtt-gw: [info] aws_gw_dev_code_get: load device code ok, dev code:aws_device_code```

Can you assist with the commands to communicate with these BLE devices?
2

Hi, are those medical devices you have brought from us? And can I check it with your gateway’s firmware? It is a great way to have an online meeting to quickly solve the issues.

3

Yes, these watches are your devices. The gateway device is: Firmware Version V4.8.308.4145708_z4G_e5351ea

The watch is: DSSW-010, 9-A-1-0012 80,Smart Watch

4

I have upgraded to the latest firmware and now the ble scan no longer even shows the watches in the scan.

V4.8.322.4589312_z4G_04011_b7130bf

Ok some questions on the watch detection…

  1. how can I configure the interval that the statics are read and sent from the hub via mqtt?

I have current set cron to restart the beacond service every 2 minutes to test.

  1. can I turn off the constant scanning? SHouldn’t this be triggered by an event in the subscribed topic?

  2. Why are all of the readings blank except for the bmp value below? Shouldn’t the body temperature and spO2 readings be included? How do I trigger them since Dusun has the SDK for this?

Here is an example reading from the watch:

{
  "mac": "30:ae:7b:e5:fa:6c",
  "from": "BLE",
  "time": 1697127302,
  "to": "GATEWAY",
  "deviceCode": "aws_device_code",
  "type": "reportAttribute",
  "data": {
    "attribute": "WATCH_bloodpress_oximeter",
    "mac": "CC:12:D5:BF:5F:7C",
    "value": {
      "spo2": 0,
      "bmp": 81,
      "diastolic": 0,
      "systolic": 0
    }
  }
}
5
  1. The interval setting is not from the gateway, it depends on the devices
  2. Switch to bluetooth Luci page, change the scan frequency to 0 and it will no more scanning. You can use /etc/init.d/bul stop to turn off BLE.
6

Can you advise on #3 above? Why are the other readings blank?

7

The blank is because the “diastolic”: 0,“systolic”: 0 are not supported right now, the temperature will provided through a JSON command, it will be send through chat