Hi,
no idea where to put this. I am working with the firmware provided for the IoT project and stumbled upon a bug.
The sensor was not transmitting the correct UUID for wrbl_dws_feat_char.
In user_dws_config.h line 339:
[DWS_IDX_FEAT_VAL] = {DWS_CONTROL_UUID_128, ATT_UUID_128_LEN, PERM(RD, ENABLE),
DEF_DWS_FEAT_CHAR_LEN, 0, NULL},
应该是
[DWS_IDX_FEAT_VAL] = {DWS_FEAT_UUID_128, ATT_UUID_128_LEN, PERM(RD, ENABLE),
DEF_DWS_FEAT_CHAR_LEN, 0, NULL},
问候
Johannes
Device:
Hi gme_johannes,
Thanks for let us know, but could you please clarify in which version of IoT project you are referring to? In the projects\target_apps\iot\iot_585 project of the DA14585_IOT_MULTI_SENSOR_DK_v6.160.2.1, which is the latest version the DWS_IDX_FEAT_VAL is correctly configured:
[DWS_IDX_FEAT_VAL] = {DWS_FEAT_UUID_128, ATT_UUID_128_LEN, PERM(RD, ENABLE),
DEF_DWS_FEAT_CHAR_LEN, 0, NULL},
Thanks, PM_Dialog
Hi PM,
I forgot that now there is a "new" IoT sensor.
I am talking about the old one, which (as I mentioned in the title) uses the 5.160.1.19 SDK.
问候
Johannes
Hi PM,
were you able to verify the bug?
问候,
Johannes
Hi gme_johannes,
From the discussion above it is a bug. Does the fix, when applied to 5.160.1.19 , work for you ?
Do you want us to record this as a bug, or want something else in this post?
Thanks,
TR_DIALOG
Hi TR, yes it behaves as expected when I change that line.
I only intended to make you aware of the bug, and maybe find out if there is a more recent version of the IoT SDK.
BR Johannes
Hi Johannes, thanks for the notification of the bug. There are unfortunately no update to the SDK 5 . BR JE_DIalog