I'm trying to make a little game with the puck, and the first part of my plan is to advertise the puck as a heart_rate monitor (service: 0x180D).
When I check the puck after a deploy with the Android nRF Connect app, it doesn't list heart_rate as a service.
When I compare to my Pebble, I can see it explicitly listed under flags & services.
The odd thing is I can advertise as a temperature gauge - but it's entirely possible I'm making mistakes.
This is my code:
NRF.setAdvertising({
0x180D: [ 99 ],
0x1809: [ 30 ],
},
{
name: "Puck <3", // The name of the device
showName: true, // include full name, or nothing
discoverable: true, // general discoverable, or limited - default is limited
interval: 600, // Advertising interval in msec, between 20 and 10000
});
Temperate correctly shows as 30c (in nRF connect), but the heart_rate is missing.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I'm trying to make a little game with the puck, and the first part of my plan is to advertise the puck as a heart_rate monitor (service: 0x180D).
When I check the puck after a deploy with the Android nRF Connect app, it doesn't list heart_rate as a service.
When I compare to my Pebble, I can see it explicitly listed under flags & services.
The odd thing is I can advertise as a temperature gauge - but it's entirely possible I'm making mistakes.
This is my code:
Temperate correctly shows as 30c (in nRF connect), but the heart_rate is missing.
Any ideas/help?
Thanks!