Payload data from Thingy 52

RE: Payload data from Thingy 52

b3Tomas — Wed, 03 Oct 2018 13:20:01 GMT

Hi Martin,

Thanks.Now I see the text :To turn on sensor reading, enable notifications from the desired characteristic by writing 0x0001 to the Client Characteristic Configuration Descriptor (CCCD) for that characteristic.

Node-Red listen to events, I will figure out how to turn on sensor notifications.

Regards

Tomas

RE: Payload data from Thingy 52

MartinBL — Wed, 03 Oct 2018 12:39:43 GMT

How much do you know about BLE? A characteristic may or may not be readable. If you look in the "Type" fields in the tables in my link you will see that all the characteristics included in your message are of a Readable type. Other characteristics, like the Temperature characteristic, are not readable, but support Notification instead. This means that the server will send you a "notification" whenever new data is available (assuming notification is turned on).

I know nothing about Node-RED, but you probably have to figure out how to turn on notification on the relevant characteristics and then how to listen for such notifications.

RE: Payload data from Thingy 52

b3Tomas — Wed, 03 Oct 2018 12:16:50 GMT

Hi Martin,

Thanks for you reply. I know the json part, and with the list of characteristics I can go on.
From what I can see, I only get the "config data" and not any sensor data.

If i wanted for example the temprature value, I would find under

ef6802019b3549339b1052ffa9740042, but that element is not there.

How do I get this element in my message payload?

Regards

Tomas

RE: Payload data from Thingy 52

MartinBL — Wed, 03 Oct 2018 11:07:23 GMT

That message is in JSON format. If you copy-paste it into this JSON formatter tool you can see it a little more clearly.

The values in bold are UUIDs and you can compare them with the list of characteristics here.