зеркало из
1
0
Форкнуть 0
Cross-platform UI for interacting with devices attached to Azure IoT Hub
Перейти к файлу
Ryan K 85a45f8c8b
Update jest-trx-results-processor dependency (#658)
Co-authored-by: Ryan Kelly <ryan@UPX-M2.local>
2024-04-04 09:57:57 -07:00
.config Release pipeline updates and package upgrades (#502) 2022-05-03 08:35:07 -07:00
.github update rjsf/fluent-ui (#624) 2023-05-16 13:31:26 -07:00
doc/screenRecords Pnp summer refresh (#335) 2020-07-21 13:12:33 -07:00
icon update app icons (#65) 2019-08-12 12:34:29 -07:00
images Phone as a Device support for QR code (#480) 2021-11-09 15:09:03 -08:00
pipelines update rjsf/fluent-ui (#624) 2023-05-16 13:31:26 -07:00
public Local dmr (#612) 2023-02-24 14:48:25 -08:00
scripts Pnp summer refresh (#335) 2020-07-21 13:12:33 -07:00
src add aria label for password textfield (#648) 2024-02-16 11:25:58 -08:00
.artifactignore Release pipeline updates and package upgrades (#502) 2022-05-03 08:35:07 -07:00
.gitignore Rkessler/investigate auth (#392) 2021-02-16 14:15:11 -08:00
CODE_OF_CONDUCT.md Initial commit 2019-07-22 14:23:43 -07:00
CONTRIBUTING.md Add contributing information per CELA 2019-07-23 13:45:42 -07:00
LICENSE Initial commit 2019-07-22 14:23:44 -07:00
README.md Remove choco (#577) 2022-11-11 15:11:45 -08:00
SECURITY.md Add security policy file 2022-05-23 12:09:55 -07:00
images.d.ts Initial code migration 2019-07-23 09:51:08 -07:00
jestSetup.ts fix test issues try 2 2022-07-15 14:29:32 -07:00
jestTrxProcessor.ts Initial code migration 2019-07-23 09:51:08 -07:00
package-lock.json Update jest-trx-results-processor dependency (#658) 2024-04-04 09:57:57 -07:00
package.json Update jest-trx-results-processor dependency (#658) 2024-04-04 09:57:57 -07:00
scss-stub.js Initial code migration 2019-07-23 09:51:08 -07:00
tsconfig-jest.json Reflow and other accessibility updates (#448) 2021-07-08 09:38:38 -07:00
tsconfig.json replace request and fix qs (#590) 2022-12-05 14:46:23 -08:00
tslint.json Reflow and other accessibility updates (#448) 2021-07-08 09:38:38 -07:00
webpack.common.ts Interal vs External Telemetry (#521) 2022-08-02 17:32:53 -07:00
webpack.dev.ts Webpack, Electron update and vulnerability fixes (#499) 2022-04-06 16:45:06 -07:00
webpack.electron.ts Webpack, Electron update and vulnerability fixes (#499) 2022-04-06 16:45:06 -07:00

README.md

Azure IoT Explorer (preview)

CI Pipeline Build Status

Release Pipeline Build Status

Table of Contents

Getting Azure IoT Explorer

You can either download a pre-built version or build it yourself.

Download a pre-built version

Go to the Releases tab, download the installer corresponding to your platform and install.

Run it locally and build it yourself

  1. Open a Node capable command prompt
  2. Clone the repo: git clone https://github.com/Azure/azure-iot-explorer.git
  3. Run: npm install
  4. Run: npm start
    • A new tab in your default browser will be opened automatically pointing to the locally running site.
  5. [optional] Stop step 4 then run: npm run build and then run: npm run electron.
    • The electron app will spin up using the bits generated in the dist folder.

If you'd like to package the app yourself, please refer to the FAQ.

Features

Configure an IoT Hub connection

  • Upon opening the application, choose an authentication method and connect to an Azure IoT hub.
  • If you picked Connect via IoT Hub connection string, you can add multiple strings, view, update or delete them anytime by returning to Home.
  • If you picked Connect via Azure Active Directory, you will be redirected to login in through AAD, from where you will be able to pick a subscription, and then pick an IoT hub.
  • You can switch back and forth between these two authentication methods.
login

Device CRUD

  • Click New to create a new device.
  • Select device(s) and click Delete to delete device(s). Multiple devices can be selected by clicking while dragging the mouse.
  • Devices can by queried by typing the first few characters of a device name in the query box.
create_device

Device functionalities

device_details

Plug and Play

If you are looking for a UI tool to get a flavor of Plug and Play, look no futher. Follow this Microsoft Docs to get started.

  • Once your device has gone through discovery, IoT Plug and Play components page would be available on device details view.
  • The model ID would be shown.
  • Follow our guidance to set up how we can retrieve model definitions. If it is already setup, We will inform you where are we resolving your model definitions from.
  • A table would show the list of components implemented by the device and the corresponding interfaces the components conform to.
  • You can go back to Home (either from device or by directly clicking the breadcrumb) to change how we resolve model definitions. Note this is a global setting which would affect across the hub.
pnp_discovery
  • Click the name of any component, and switch between interface, properties, commands and telemetry to start interacting with the PnP device.
pnp_interaction_property pnp_interaction_telemetry

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

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.