зеркало из
1
0
Форкнуть 0
A Node.js SDK for connecting devices to Microsoft Azure IoT services
Перейти к файлу
Pierre Cauchois d1a58daabd fix(e2e:methods): reuse test device across device methods tests 2018-04-13 11:36:42 -07:00
.github Update readmes and templates with support information and other main readme improvements 2018-03-16 11:00:32 -07:00
build Move symlinks into local directory for easier cleanup use of multiple clones on a single machine 2018-04-11 14:28:11 -07:00
common Bump package versions for release 2018-4-5 2018-04-05 16:21:41 -07:00
device Bump package versions for release 2018-4-5 2018-04-05 16:21:41 -07:00
doc Add e2e tests to the node-test docs 2017-06-14 16:14:00 -07:00
e2etests fix(e2e:methods): reuse test device across device methods tests 2018-04-13 11:36:42 -07:00
jenkins improve builds, step 1: separate e2e tests 2017-10-23 19:31:47 -07:00
longhaultests add a debug statements for the end of tests, and links setup script 2018-03-27 16:47:04 -07:00
network_e2e Docker-based network connection tests for windows 2017-04-11 13:17:38 -07:00
provisioning disable AmqpWs for DPS Group enrollment e2e test 2018-04-09 11:03:03 -07:00
security Bump package versions for release 2018-3-9 2018-03-09 16:36:40 -08:00
service Bump package versions for release 2018-4-5 2018-04-05 16:21:41 -07:00
ts-e2e Increase/Clean up e2e timeouts. need to be at least 60 seconds for device creation. 2018-03-29 19:34:12 -07:00
.gitattributes Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
.gitignore Move symlinks into local directory for easier cleanup use of multiple clones on a single machine 2018-04-11 14:28:11 -07:00
.jshintignore [Node.js] Add code coverage reporting 2016-02-22 13:12:20 -08:00
.jshintrc Improve Node.js build 2015-10-20 13:15:29 -07:00
CODE_OF_CONDUCT.md Add code of conduct file 2017-10-17 15:43:27 -07:00
LICENSE Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
feature_matrix.md Update readmes and templates with support information and other main readme improvements 2018-03-16 11:00:32 -07:00
lts_branches.png Update LTS document 2017-07-07 17:20:05 -07:00
readme.md Update readmes and templates with support information and other main readme improvements 2018-03-16 11:00:32 -07:00
thirdpartynotice.txt Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
tslint.json azure-iot-common port to TypeScript 2017-05-02 18:33:01 -07:00

readme.md

Microsoft Azure IoT SDK for Node.js

This repository contains the following SDKs:

  • Azure IoT Hub Device SDK: to connect devices to Azure IoT Hub. API Reference
  • Azure IoT Hub Service SDK: enables developing back-end applications making use of Azure IoT Hub. API Reference
  • Azure IoT Hub Provisioning Device SDK: to connect devices to the Azure IoT Hub Provisioning Service. API Reference
  • Azure IoT Hub Provisioning Service SDK: enables developing back-end applications making use of the Azure IoT Provisioning Service. API Reference

Developing applications for Azure IoT

Visit Azure IoT Dev Center to learn more about developing applications for Azure IoT.

How to use the Azure IoT SDKs for Node.js

Devices and data sources in an IoT solution can range from a simple network-connected sensor to a powerful, standalone computing device. Devices may have limited processing capability, memory, communication bandwidth, and communication protocol support. The IoT device SDKs enable you to implement client applications for a wide variety of devices.

The SDK team publishes the SDKs as npm packages:

  • Working with the SDKs code: if you are working with the SDK's code to modify it or to contribute changes, then you can clone the repository and build the libraries following these instructions.

Need Support?

  • Have a feature request for SDKs? Please post it on User Voice to help us prioritize
  • Have a technical question? Ask on Stack Overflow with tag "azure-iot-hub"
  • Need Support? Every customer with an active Azure subscription has access to support with guaranteed response time. Consider submitting a ticket and get assistance from Microsoft support team
  • Found a bug? Please help us fix it by thoroughly documenting it and filing an issue.

Key features and roadmap

Here's a feature matrix that will help you understand what feature is supported with which protocol.

Samples

In the repository, you will find a set of simple samples that will help you get started:

Platforms compatibility

The Azure IoT SDK for Node.js should work with versions of Node.js as old as v0.10.x. this being said, a lot of dependencies are slowly dropping support for these older versions and we really have no control over that.

It is recommended to update to at least Node.js v4.x.x.

Contribution, feedback and issues

If you encounter any bugs, have suggestions for new features or if you would like to become an active contributor to this project please follow the instructions provided in the contribution guidelines.

Looking for SDKs for other languages/platforms?

Read more

Long Term Support

The project offers a Long Term Support (LTS) version to allow users that do not need the latest features to be shielded from unwanted changes.

A new LTS version will be created every 6 months. The lifetime of an LTS branch is currently planned for one year. LTS branches receive all bug fixes that fall in one of these categories:

  • security bugfixes
  • critical bugfixes (crashes, memory leaks, etc.)

No new features or improvements will be picked up in an LTS branch.

LTS branches are named lts_mm_yyyy, where mm and yyyy are the month and year when the branch was created. An example of such a branch is lts_07_2017.

Schedule1

Below is a table showing the mapping of the LTS branches to the package versions released

NPM Package Github Branch LTS Status LTS Start Date Maintenance End Date Removed Date
1.3.x lts_02_2018 Active 2018-02-16 2018-08-16 2019-02-16
  • 1 All scheduled dates are subject to change by the Azure IoT SDK team.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.