RE: Issue in requiring notifications of the Nordic Thingy:52

WimVerbeek — Mon, 15 Feb 2021 13:06:11 GMT

I apologize, the issue is caused by a coding error in the javascript I used. That javacode was not correct for the Mendix version I used.

RE: Issue in requiring notifications of the Nordic Thingy:52

WimVerbeek — Mon, 15 Feb 2021 12:54:54 GMT

After receiving the nRF52, I activated the firmware update using the Nordic Thingy app, to v2.2.0). Message was 'completed'. So, except for updating the firmware, I didn't change anything of the device.

I use some Javascript (appstore content, so not created by me) in a dev-tool Mendix for connecting to the device, and the connection with the device is successfull. But in retrieving the notifications the message 'characteristic is not defined' is generated. I presume that's a message from the device itself?

The javascript uses the

window.gattServer

getPrimaryService(optionalServiceUUID)
'ef680200-9b35-4933-9b10-52ffa9740042'

getCharacteristic(characteristicUUID)
'ef680201-9b35-4933-9b10-52ffa9740042'

In the Nordic documentation I see:
"To turn on sensor reading, enable notifications from the desired characteristic by writing 0x0001 to the Client Characteristic Configuration Descriptor (CCCD) for that characteristic."
Is this what causes this behaviour?

I used a demo on the Mendix website, where they used the Thingy without problems.
(https://www.youtube.com/watch?v=_83HFXKeRSw , start about 7 minutes in the video) 

RE: Issue in requiring notifications of the Nordic Thingy:52

Sigurd — Mon, 15 Feb 2021 12:16:49 GMT

Hi,

What changes did you do, and where? Did you do any changes to the firmware code that is running on the nRF52?

[quote user=""]characteristic is not defined.[/quote]

When and where do you see this message?