bt_gatt_notify returning -ENOTCONN

RE: bt_gatt_notify returning -ENOTCONN

ujur007 — Fri, 24 Mar 2023 09:10:49 GMT

I have them already, but the issue is also there with Zephyr installed within the nRF SDK folder. I copied and flashed the same application.

github.com/.../55853

RE: bt_gatt_notify returning -ENOTCONN

Amanda Hsieh — Mon, 20 Mar 2023 15:31:47 GMT

Hi,

Please contact Zephyr Discord for vanilla zephyr support.

-Amanda H.

RE: bt_gatt_notify returning -ENOTCONN

ujur007 — Fri, 17 Mar 2023 17:58:40 GMT

Was there any update to this issue? I am facing the same problem with Zephyr installation.

note: I am not using Zephyr inside /ncs folder.

One question is also that the HRS service notification is working then how can it be that custom notification has a issue?

RE: bt_gatt_notify returning -ENOTCONN

Amanda Hsieh — Fri, 09 Sep 2022 11:14:53 GMT

Hi,

Please use Zephyr provided by NCS. We only support nRF Connect SDK in our integration layer and we can't really help if the customer wants to use the vanilla Zephyr. All the development was with nRF Connect SDK in mind, and we cannot guarantee it will work without code changes in a different context.

If you still have an issue with NCS, please create a new support case and describe the problem with the NCS version. I will be out of the office for two weeks and would not reply to this case.

Regards,
Amanda

RE: bt_gatt_notify returning -ENOTCONN

CacO3 — Thu, 01 Sep 2022 14:47:02 GMT

I have the same issue using Zephyr 3.1, would be great if Nordic could provide some input!

RE: bt_gatt_notify returning -ENOTCONN

yayembedded — Mon, 22 Nov 2021 15:08:34 GMT

Hi Amanda,

Thanks for the function signatures, but I am not sure how that will help me.

I forgot to mention there is no problem reading and writing to the characteristic in question. Only notifications for this characteristic have an issue.

I can keep all my code the same, but change which characteristic I use to notify and there is no issue.

RE: bt_gatt_notify returning -ENOTCONN

Amanda Hsieh — Mon, 22 Nov 2021 12:49:25 GMT

Hi,

Have a look bt_gatt_notify (structbt_conn*conn, conststruct bt_gatt_attr*attr, constvoid*data, uint16_tlen)

Notify attribute value change.

Send notification of attribute value change, if connection is NULL notify all peer that have notification enabled via CCC otherwise do a direct notification only the given connection.

The attribute object on the parameters can be the so called Characteristic Declaration, which is usually declared with BT_GATT_CHARACTERISTIC followed by BT_GATT_CCC, or the Characteristic Value Declaration which is automatically created after the Characteristic Declaration when using BT_GATT_CHARACTERISTIC.

Parameters

conn – Connection object.
attr – Characteristic or Characteristic Value attribute.
data – Pointer to Attribute data.
len – Attribute value length.

Returns

0 in case of success or negative value in case of error.

struct bt_gatt_attr
#include <gatt.h>

GATT Attribute structure.

Public Members

conststructbt_uuid*uuid: Attribute UUID

ssize_t(*read)(structbt_conn*conn, conststructbt_gatt_attr*attr, void*buf, uint16_tlen, uint16_toffset)

Attribute read callback.

The callback can also be used locally to read the contents of the attribute in which case no connection will be set.

Parameters

conn – The connection that is requesting to read
attr – The attribute that’s being read
buf – Buffer to place the read result in
len – Length of data to read
offset – Offset to start reading from

Returns

Number fo bytes read, or in case of an error BT_GATT_ERR() with a specific ATT error code.

Regards,
Amanda