Notification message not setting value in database

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.

2 posts / 0 new

Last post

Fri, 2018-03-09 19:05

mkelwood

Offline

Last seen:1 month 3 weeks ago

加入:2017-05-19的人们

Notification message not setting value in database

The CUSTS1_VAL_NTF_REQ message as documented in custs1_task.h:

/// Set/update characteristic value and trigger a notification
CUSTS1_VAL_NTF_REQ,

suggests that the handler for this message will actually set the value in the ATT database. This was the case with SDK 5 but appears to NOT be the case for SDK 6. In order to actually set the new value in the database, I need to set the value directly (using attmdb_att_set_value() or custs1_att_set_value()) before sending the notification message, or send a CUSTS1_VAL_SET_REQ to the custs1 task.

I would guess this is a bug. Is the SDK 6 intent to not set/update the characteristic value in the CUSTS1_VAL_NTF_REQ handler? If this is true, then the comment in the CUSTS1 message enum is misleading.

Device:

DA14585

Mon, 2018-03-12 16:18

MT_dialog

Offline

Last seen:2 months 1 week ago

加入:2015-06-08 11:34

Hi mkelwood,

Yes, you are right on this, thanks for indicating, i will let the SDK team know.

Thanks MT_dialog