After registering with Golioth and setting up a device (particle_xenon) together with a Particle Ethernet Tripler board, and then building the AQW ethernet_hub_ble example, I successfully connected to Golioth, obtained an IP and observed my device as active in the Golioth Devices Activity Dashboard.
You may want to checkout https://github.com/circuitdojo/air-quality-wing-zephyr-demo/blob/main/ble/src/ble/services/aqw.h with details on the services/characteristics used.
Also see https://github.com/circuitdojo/air-quality-wing-zephyr-demo/blob/main/ble/src/ble/services/aqw.c on how data is published from the application.
Thanks.
I’m fine with the AQW ble example and am able to view the data using the nRF Connectapp on my iPhone / iPad.
The problem is that with the AQW ethernet_hub_ble example, unlike the ble example, I’m not able to see Air Quality Wing device with nRF Connect app.
So, I expect an APP_EVENT_BLE_DATA event isn’t being generated and data from BLE isn’t sent to Golioth via the Particle Ethernet board.
I’ll review the ethernet_hub_ble code and debug.
Hmm I’ll have to check on my end. Maybe something broke when upgrading the SDK. Let me know how it goes zpm1066 if you beat me to it.
Thanks.
OK, I see what is going on.
The ethernet_hub_ble (Particle Ethernet board with a particle_xenon) looks for an Air Quality Wing BLE device that has the AQW- dust sensor attached. The ethernet_hub_ble connects to the Air Quality Wing and gets the sensor data when the APP_EVENT_BLE_DATA event occurs and then publishes the data to Golioth. Of course, if there is no AQW board, there’s no data to be sent to Golioth.
Correct?
J-Link EDU Mini V1 compiled Mar 28 2023 17:01:59 V1.0, SN=801017276
Process: JLinkExe
[00:00:00.010,681] <inf> eth_w5500: W5500 Initialized
*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.012,054] <inf> golioth_system: Initializing
[00:00:00.012,542] <inf> aqw_ethernet_hub_ble: Air Quality Wing Ethernet Hub
[00:00:00.012,542] <inf> app_network: Run DHCPv4 client
[00:00:00.013,092] <inf> sdc_hci_driver: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |....
[00:00:00.016,235] <inf> app_ble: Bluetooth initialized
[00:00:00.016,815] <inf> app_ble_scan: Scanning successfully started
[00:00:45.264,404] <inf> app_ble_scan: Scan match: [addr: C4:95:D4:C8:96:FB (random)]
[00:00:45.265,045] <inf> app_ble_scan: Scan connecting..
[00:00:45.369,201] <inf> app_ble: Connected: C4:95:D4:C8:96:FB (random)
[00:00:46.870,483] <inf> app_ble_gatt: Discovery complete!
[00:01:51.920,989] <inf> aqw_ethernet_hub_ble: Temperature: 0.0°C
[00:01:51.921,020] <wrn> date_time: Valid time not currently available
[00:01:51.921,051] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!
[00:01:51.921,081] <inf> aqw_ethernet_hub_ble: Humidity: 0.0%
[00:01:51.921,081] <wrn> date_time: Valid time not currently available
[00:01:51.921,112] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!
[00:01:51.921,142] <inf> aqw_ethernet_hub_ble: Temperature: 0.0°C
[00:01:51.921,142] <wrn> date_time: Valid time not currently available
[00:01:51.921,173] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!
[00:01:51.921,203] <inf> aqw_ethernet_hub_ble: Humidity: 0.0%
[00:01:51.921,203] <wrn> date_time: Valid time not currently available
[00:01:51.921,234] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!
[00:01:51.921,447] <wrn> golioth: Failed to make CoAP request: -115
[00:01:51.921,447] <wrn> aqw_ethernet_hub_ble: Failed to send data: -115
[00:03:58.721,008] <inf> aqw_ethernet_hub_ble: Temperature: 0.0°C
[00:03:58.721,038] <wrn> date_time: Valid time not currently available
[00:03:58.721,038] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!
[00:03:58.721,069] <inf> aqw_ethernet_hub_ble: Humidity: 0.0%
[00:03:58.721,099] <wrn> date_time: Valid time not currently available
[00:03:58.721,099] <wrn> aqw_ethernet_hub_ble: Unable to get timestamp!Yup sounds about right!
Yes, it makes sense as AQW + dust sensor will be in an enclosure, so the Particle Ethernet + Xenon would connect to the AQW via bluetooth, get the sensor data and then send it to Golioth cloud.
btw - I now have Goloith, AQW, and your demos in the nRF Connect SDK Zephyr location, so that I can build / flash and debug using the NCS for VSCode.
In addition, I have the latest vanilla Zephyr plus your zephyr SDK Tools. However, for me, having Golioth/AQW in the same NCS for VSCode Zephyr means that these projects are all available along with my other nRF projects.
I’ll post instructions for anyone else that may want to use a similar setup.
Thanks for your help.