@Terrence7, when reading movements from accelerometer, you modify the puck's advertisement, and go back to normal advertisement a while later. Periodically, on another puck or on Pi you check who 'is out there' by scanning for advertisements and filter the one you are interested in. You always keep the last one for comparison with the present one to determine when the movement started respectively has stopped. The change - either begin or ended - you publish to the IoT Azure Hub. Whether you can do all in graphical editor - blockly - or or not, I don't know. But doing it in JS may even be simpler.
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.
@Terrence7, when reading movements from accelerometer, you modify the puck's advertisement, and go back to normal advertisement a while later. Periodically, on another puck or on Pi you check who 'is out there' by scanning for advertisements and filter the one you are interested in. You always keep the last one for comparison with the present one to determine when the movement started respectively has stopped. The change - either begin or ended - you publish to the IoT Azure Hub. Whether you can do all in graphical editor - blockly - or or not, I don't know. But doing it in JS may even be simpler.