Nordic Thingy:52 node.js/Raspberry Pi demos

Our brilliant apps engineers continue to play around with our newly-launched Nordic Thingy:52. This time, Joakim has prepared a few Javascript demos using node.js and a Raspberry Pi.

The Thingy connects to the Raspberry Pi with Bluetooth and uses it as an internet gateway. The Raspberry Pi runs the node.js scripts. The provided examples, which you can download below the video, include:

  • An example where all environmental sensor data is pushed to an online Firebase database.
  • An IFTTT example, where data form the Thingy triggers actions online.
  • An internet radio streaming example, where internet radio is streamed to the Nordic Thingy:52 and played back through the internal speaker.

The node.js scripts are multi-platform of course, and everything can be downloaded from this GitHub repository:

https://github.com/NordicSemiconductor/Nordic-Thingy52-Nodejs

Visit this page to learn more about the Nordic Thingy:52: http://www.nordicsemi.com/eng/Products/Nordic-Thingy-52

Feel free to comment or ask questions below!

Thanks; The Nordic People

Parents
  • Cool stuff. I'm on RPi/Debian. After I've run a few demos, Thingy.discover() no longer succeeds. I notice that a bunch of kworker jobs have accumulated:

    root      1347  0.1  0.0      0     0 ?        S    19:45   0:00 [kworker/0:0]
    root      1348  0.0  0.0      0     0 ?        S    19:45   0:00 [kworker/1:0]
    root      1371  0.0  0.0      0     0 ?        S    19:45   0:00 [kworker/3:0]
    root      1414  0.0  0.0      0     0 ?        S<   19:46   0:00 [kworker/u9:1]
    root      1436  0.0  0.0      0     0 ?        S    19:46   0:00 [kworker/u8:3]
    root      1477  0.1  0.0      0     0 ?        S    19:50   0:00 [kworker/0:2]
    root      1478  0.0  0.0      0     0 ?        S    19:50   0:00 [kworker/1:1]
    root      1480  0.0  0.0      0     0 ?        S    19:50   0:00 [kworker/3:2]
    

    After I kill them off, Thingy.dicover() once again works. Is this an error on my part? Should I file it as an issue under github.com/.../issues Or is this a known problem?

Comment
  • Cool stuff. I'm on RPi/Debian. After I've run a few demos, Thingy.discover() no longer succeeds. I notice that a bunch of kworker jobs have accumulated:

    root      1347  0.1  0.0      0     0 ?        S    19:45   0:00 [kworker/0:0]
    root      1348  0.0  0.0      0     0 ?        S    19:45   0:00 [kworker/1:0]
    root      1371  0.0  0.0      0     0 ?        S    19:45   0:00 [kworker/3:0]
    root      1414  0.0  0.0      0     0 ?        S<   19:46   0:00 [kworker/u9:1]
    root      1436  0.0  0.0      0     0 ?        S    19:46   0:00 [kworker/u8:3]
    root      1477  0.1  0.0      0     0 ?        S    19:50   0:00 [kworker/0:2]
    root      1478  0.0  0.0      0     0 ?        S    19:50   0:00 [kworker/1:1]
    root      1480  0.0  0.0      0     0 ?        S    19:50   0:00 [kworker/3:2]
    

    After I kill them off, Thingy.dicover() once again works. Is this an error on my part? Should I file it as an issue under github.com/.../issues Or is this a known problem?

Children
No Data