title | description | services | documentationcenter | author | manager | tags | keywords | ROBOTS | ms.assetid | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SensorTag device & Azure IoT Gateway - Troubleshooting | Microsoft Docs |
Troubleshooting page for Intel NUC gateway |
iot-hub |
shizn |
timlt |
iot issues, internet of things problems |
NOINDEX |
5f742c38-0e33-465a-9a0d-1e41e8d17187 |
iot-hub |
c |
article |
na |
na |
3/21/2017 |
xshi |
To troubleshoot SensorTag connectivity issues, use the SensorTag app.
To troubleshoot boot issues, refer to troubleshooting No Boot Issues on Intel NUC.
To troubleshoot operating system issues, refer to troubleshooting Operating System Issues on Intel NUC.
To troubleshoot other issues, refer to Blink Codes and Beep Codes for Intel NUC.
If you encounter problems in running gulp tasks, you can add the --verbose
option for debugging. Try to terminate current gulp tasks by using Ctrl + C
, and then run the following command in your console window to see debug messages. You might see detailed error messages in your console output.
gulp --verbose
For help in troubleshooting common problems with the discover-sensortag
command, check the wiki page.
Try to update your npm package by running the following command:
npm install -g npm
If the problem still exists, leave your comments at the end of this article or create a GitHub issue in our sample repository.
Below instructions are meant for debugging node.js scripts used in this tutorial.
Run the sample application in debug mode by running the following command:
gulp run --debug
When the debug engine is ready, you should see Debugger listening on port 5858
in the console output.
-
Open the Debug panel on the left side.
-
Click the green Start Debugging (F5) button. Visual Studio Code opens a
launch.json
file. -
Update the
launch.json
file with the following content. Replace[device hostname or IP address]
with the actual device IP address or host name.{ "version": "0.2.0", "configurations": [ { "name": "Attach", "type": "node", "request": "attach", "port": 5858, "address": "[device hostname or IP address]", "restart": false, "sourceMaps": false, "outDir": null, "localRoot": "${workspaceRoot}", "remoteRoot": "~/ble_sample" } ] }
Click the green Start Debugging (F5) button to start debugging.
Read JavaScript in VS Code to learn more about the debugger.
The Azure command-line interface (Azure CLI) is a preview build. To seek solutions, you can use the Preview Install Guide.
If you encounter any bugs with the tool, file an issue in the Issues section of the GitHub repo.
For help in troubleshooting common problems, check the readme.
If you meet "Could not find a version that satisfies the requirement", please run the following command to upgrade pip to lastest version.
python -m pip install --upgrade pip
When you're installing pip, a permission error is thrown when older packages are installed with su permissions. This situation occurs because a previous installation of Python using brew (macOS) is not uninstalled completely. Some pip packages from a previous installation were created by root, which causes the permission error. The solution is to remove those packages installed by root. Use the following steps to complete this task:
- Go to
/usr/local/lib/python2.7/site-packages
- List packages created by root:
ls -l | grep root
- Uninstall packages from step 2:
sudo rm -rf {package name}
- Reinstall Python.
If you've successfully provisioned your Azure IoT hub with the Azure CLI, and you need a tool to manage the devices that are connecting to your IoT hub, try the following tools.
Device Explorer runs on your Windows local machine and connects to your IoT hub in Azure. It communicates with the following IoT Hub endpoints:
- Device identity management to provision and manage devices registered with your IoT hub.
- Receive device-to-cloud so you can monitor messages sent from your device to your IoT hub.
- Send cloud-to-device so you can send messages to your devices from your IoT hub.
Configure your IoT hub connection string within this tool to use all its capabilities.
iothub-explorer is a sample multiplatform CLI tool to manage device clients. You can use the tool to manage the devices in the identity registry, monitor device-to-cloud messages, and send cloud-to-device commands.
To install the latest (prerelease) version of the iothub-explorer tool, run the following command:
npm install -g iothub-explorer@latest
To get additional help about all the iothub-explorer commands and their parameters, run the following command:
iothub-explorer help
A full CLI experience helps you create and manage all your Azure resources. You might also want to use the Azure portal to help provision, manage, and debug your Azure resources.
Microsoft Azure Storage Explorer (preview) is a standalone app from Microsoft that you can use to work with Azure Storage data on Windows, macOS, and Linux. By using this tool, you can connect to your table and see the data in it. You can use this tool to troubleshoot your Azure Storage issues.