ttn-azure-workshop's Introduction

The Things Network & Azure IoT in unison

Microsoft TechDays 2016 - Workshop IoT

This workshop is all about you, getting your hands on some amazing pieces of technology. First, you will be introduced to The Things Network (the first ever, community-powered, global IoT network). Start building a solution that collects sensor information using a device with an enormous wireless range potential at extremely low power consumption. Next, you will learn how this network can integrate with Azure to ingest data on a massive scale and take action on incoming events. You will build some hardware, write (or copy) a couple of lines of code, configure a few things and end up with a fully working solution. The workshop content is highly curated to offer developers, of all sorts and backgrounds, an accelerated experience in the field of IoT. On top of that, there will be a team of experts present to help out and have an inspiring conversation with.

Technologies covered are: Arduino, LoRaWAN, TTN Technology, Azure IoT Hub, Azure Event Hubs, Azure Stream Analytics and Azure Functions

Team of experts

During the workshop the following experts will be present to guide you through the workshop:

Valery Jacobs, Technical Evangelist at Microsoft
Johan Stokking; Architect & Co-founder at The Things Network
Sander van de Velde; Microsoft Consultant at Atos
Jan Willem Groenenberg; Microsoft Consultant at Atos

Workshop schedule at Microsoft TechDays 2016

StartTime	EndTime	Room
04/10/2016 11:45	04/10/2016 13:45	G108
04/10/2016 14:15	04/10/2016 16:15	G108
05/10/2016 08:15	05/10/2016 10:15	G108
05/10/2016 10:30	05/10/2016 12:30	G108

Let's dive into the workshop

The workshop consists of three parts. The first two parts will guide you through the essentials we want you to get your hands on. The third part is optional/extra if you have time left.

ttn-azure-workshop's People

Contributors

Stargazers

Watchers

ttn-azure-workshop's Issues

Visualize progress of steps throughout the workshop

Add configuring keys in device and sending real data

Remove Node.js installation instructions

Remove TTN account create instructions

Fix ttn-azure-iothub package

Instructions should be npm install --save ttn-azure-iothub@preview (note the tag)

Add connecting device and reading sensors

ttn.Client is not a constructor

Hi!

Thank you for this tutorial, its exactly what I want to do.
Actually I fail on point "Start the bridge"

The PowerShell Log is this:

D:\Projekte\bla\bla\Source\iot_server\node_modules\ttn-azure-iothub\index.js:32
this.ttnClient = new ttn.Client(region, appId, accessKey);
^
TypeError: ttn.Client is not a constructor
at new Bridge (D:\Projekte\bla\bla\Source\iot_server\node_modules\ttn-azure-iothub\index.js:32:22)
at Object. (D:\Projekte\bla\bla\Source\iot_server\server.js:15:16)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Function.Module.runMain (module.js:665:10)
at startup (bootstrap_node.js:201:16)
at bootstrap_node.js:626:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\lukas\AppData\Roaming\npm-cache_logs\2017-09-14T12_37_32_150Z-debug.log
PS D:\Projekte\bla\bla\Source\iot_server>

The Log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;D:\Projekte\bla\bla\Source\iot_server\node_modules.bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Common Files\Intel\Shared Files\cpp\bin\Intel64;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Java\jdk1.8.0_101\bin;C:\Program Files (x86)\PuTTY;C:\Program Files (x86)\systools;C:\WINDOWS\CCM;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files\Git\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\MongoDB\Server\3.4\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\Skype\Phone;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs;C:\Users\lukas\AppData\Local\Microsoft\WindowsApps;;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\lukas\AppData\Roaming\npm
9 verbose lifecycle [email protected]start: CWD: D:\Projekte\bla\bla\Source\iot_server
10 silly lifecycle [email protected]start: Args: [ '/d /s /c', 'node server.js' ]
11 silly lifecycle [email protected]start: Returned: code: 1 signal: null
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: node server.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:289:16)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at EventEmitter.emit (events.js:213:7)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at ChildProcess.emit (events.js:213:7)
13 verbose stack at maybeClose (internal/child_process.js:927:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid [email protected]
15 verbose cwd D:\Projekte\bla\bla\Source\iot_server
16 verbose Windows_NT 10.0.14393
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v8.5.0
19 verbose npm v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: node server.js
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]