NRF_ERROR_INVALID_STATE error on new characteristic

RE: NRF_ERROR_INVALID_STATE error on new characteristic

Kenneth — Mon, 20 Apr 2020 09:28:28 GMT

I could find a user guide for the nRF Connect for desktop:
https://infocenter.nordicsemi.com/topic/ug_nrfconnect_ble/UG/nRF_Connect_BLE/nRF_Connect_intro.html

You can find a description of nRF Connect mobile here:
https://github.com/NordicSemiconductor/Android-nRF-Connect/tree/master/documentation

RE: NRF_ERROR_INVALID_STATE error on new characteristic

SentinelLighting — Thu, 16 Apr 2020 15:58:17 GMT

I do have nrf Connect. Where do you go to enable notifications?

RE: NRF_ERROR_INVALID_STATE error on new characteristic

Kenneth — Thu, 16 Apr 2020 15:35:08 GMT

[quote user="SentinelLighting"]Does the Thingy app somehow 'enable' the notifications on a per characteristic basis? That would explain why I get an error.[/quote]

Could be, do you have the possibility to use nRF Connect app to manually enable the notifications?

Kenneth

RE: NRF_ERROR_INVALID_STATE error on new characteristic

SentinelLighting — Thu, 16 Apr 2020 12:04:08 GMT

The new characteristic always errors. In my testing I establish a connection between the Thingy app and my modified code. I then have it start to transmit the sound data for both the existing 'right' channel and my new 'left' sound channel. The right channel transmits fine with no errors. The new 'left' channel continuously errors. For the new characteristic I tried to 'clone' the set up and handler code from the existing one as much as possible

Does the Thingy app somehow 'enable' the notifications on a per characteristic basis? That would explain why I get an error.

RE: NRF_ERROR_INVALID_STATE error on new characteristic

Kenneth — Thu, 16 Apr 2020 07:45:05 GMT

It is common that sd_ble_gatts_hvx() return NRF_ERROR_INVALID_STATE upon power on and initial connection, e.g. because the peer need to connect, do a database discovery of the peripheral and then enable the notifications in the database. I think the question for you is whether sd_ble_gatts_hvx() always return NRF_ERROR_INVALID_STATE (even for instance after other notifications are working)?