Packt+ | Advance your knowledge in tech

You're reading from Building Bots with Microsoft Bot Framework Creating intelligent conversational interfaces

Product type Paperback

Published in May 2017

Publisher Packt

ISBN-13 9781786463104

Length 424 pages

Edition 1st Edition

Languages

Tools

Azure

Concepts

Chatbots

Author (1):

Gaddam

View More author details

Table of Contents (16) Chapters

Title Page

Credits

About the Author

About the Reviewer

www.PacktPub.com

Customer Feedback

Preface

1. Setting up Microsoft Bot Framework Dev Environment FREE CHAPTER

2. Developing Your First Bot Using the Connector and Builder SDK

3. Developing WeatherBot Using Dialogs and LUIS

4. Natural Speech and Intent Processing Bot Using Microsoft Cognitive Services

5. Developing Bots Using LUIS Prompt Dialogs with State and Nearby Bot Using Custom APIs

6. Developing an IVR Bot for a Bank Using Advanced Microsoft Bot Framework Technologies

7. Intelligent Bots with Microsoft Bot Framework and Service Fabric

8. Developing Intelligent Facial Expression Identification Bot for IoT Using Azure and Power BI

9. Publishing a Bot to Skype, Slack, Facebook, and the GroupMe Channel

Device identity and registry with IoT Hub

The main purpose of device identity registration is to allow access to the device-facing endpoints. For each device, it creates resources in Azure IoT Hub, which enables device-to-cloud messages and also cloud-to-device messages, if needed.

You can do this in different ways. Here, I will explain a technique using Device Explorer.

Using Device Explorer

You can use this tool to manage devices connected to your IoT Hub. For example, you can register a device with your IoT hub, monitor messages from your devices, and send messages to your devices. Device Explorer runs on your local machine and connects to your IoT hub in Azure. Following are the steps for using Device Explorer:

Download and install Device Explorer from https://github.com/Azure/azure-iot-sdks/releases.
Assuming that you already have IoT Hub in Azure--if not, check out the getting started link mentioned at the start of this chapter--you need an IoT Hub connection string, to get it, log in to...