While investing the new vs code support (so awesome!), I came across something that had proved valuable in the previous tool of choice (Device Explorer UI). There I can do:

And when monitoring, I can provide a start date in the past, allowing me to get the "last few" D2C messages. This is super helpful when dealing with slow reporting rates (say, >10mins), where you'd have to leave the window open to get the latest.

Is there a way to do this in vscode-azure-iot-toolkit? I looked for a setting, but didn't see anything obvious.

It would also be sufficient to somehow just, "get the latest message for this device and display it". As that is typically what I am wanting.

Please advise,
Elliott

install azure-iot-toolkit-1.3.0-rc3.vsix
step:

1.create IoT hub with B1 basic tier

2. create IoT Edge device failed, is it expect?
   

I've been getting popups from VS Code about the extension host "not responding" on startup every time lately, and when I look, it seems the works offender is the Azure IoT Toolkit at almost 10 seconds on my dev PC ...

• Extension Name: azure-iot-toolkit
• Extension Version: 1.4.0
• OS Version: Windows_NT x64 10.0.17763
• VSCode version: 1.28.0-insider

We have written the needed data into your clipboard. Please paste:

{
	"activationTimes": {
		"startup": true,
		"codeLoadingTime": 9649,
		"activateCallTime": 11,
		"activateResolvedTime": 0,
		"activationEvent": "*"
	}
}

Currently, it would show all subscriptions even user choose only a subset.

test case :Get device info

test step:
1.Click an IoT Hub device in tree explorer
Expect : Verify a JSON of device info in shown in Output Channel, and the JSON contains the connection string of the device

Actually : Verify nothing happens but just toggle the module list

steps:

1. right click a device and select Generate Code --Node js -- send D2C message
2. Run 'npm install azure-iot-device-mqtt' to install the required libraries
3. right click the code and can't find "Run Code" menu

Currently, the Edge related commands in IoT Toolkit extension is sorted as:

I found this order somewhat counter-intuitive, because Setup Edge usually happens first and Create Deployment happens last. This can be confusing for users. (Actually, the current order is the order with which these commands are added to the extension).

I think below order is more logical:

Bug of VS Code: microsoft/vscode#52778

Test steps:

1. create device named “testc#”
2. create invoke method from here https://iotdevtool.azurewebsites.net/device/
3. right-click the testc# device and select “Invoke Direct Method”
   

install latest toolkit 1.3.0.-rc3

step:

1. create IoT hub
2. create IoT edge device
3. In VS Code settings, set the start time for monitoring D2C message (e.g. 30)
   "azure-iot-toolkit.monitorD2CBeforeNowInMinutes": 30
   4.right click the edge device and Start monitoring D2C message
   Expect : the output should not print D2C message ,because I don't send any D2C message for this device
   Actually: the output print the D2C messages as bellow, but I don't know these message come from.

IoTHubMonitor] Start monitoring D2C message for [macedgedevice] ...
[IoTHubMonitor] Created partition receiver [3] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [2] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [1] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [0] for consumerGroup [$Default]
[IoTHubMonitor] [9:33:11 AM] Message received from [macedgedevice]:
{
"temperature": 29.069904,
"humidity": 78.810182
}
[IoTHubMonitor] [9:33:12 AM] Message received from [macedgedevice]:
{
"temperature": 29.968401,
"humidity": 68.754284
}
[IoTHubMonitor] [9:33:14 AM] Message received from [macedgedevice]:
{
"temperature": 26.369562,
"humidity": 73.736461
}

Flow:

1. Right-click on a device and select 'Generate Code'
2. Drop-down list: select language (Node.js, Python, HTTP...)
3. Drop-down list: select code type (Send D2C message, Monitor D2C message..)
4. Generate code and show in VS Code

Languages:

• Node.js
• Python
• REST API
• Java
• C#
• F#
• Go
• PHP
• Ruby

• Extension Name: azure-iot-toolkit
• Extension Version: 1.4.0
• OS Version: Windows_NT x64 10.0.17134
• VSCode version: 1.28.0

Plugin takes almost 14 seconds for startup activation

In IoT workbench, in the first step of Cloud Provision, when we create a new IoT Hub and try to create a resource group from VS Code, it automatically and quickly fails with an error “Provision cancelled”.

• ignoreFocusOut when sending d2c message
• Valid that input should be number when generating SAS token

install azure-iot-toolkit-1.3.0-rc3.vsix
step:
1.create IoT hub with B1 basic tier
2. azure Iot hub: create device

3.verify the result

4.https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-upgrade

5.refresh , it will display no moudles, is it expect?

Currently, such parameter is not supported.
User need to pick up subscription every time.

Api provided by Azure function extension:

const functionAppId: string = await vscode.commands.executeCommand('azureFunctions.createFunctionApp', '00000000-0000-0000-0000-000000000000');

VS Code bug: microsoft/vscode#52803

The new IoT Hub Basic tier does not support monitoring, C2D messaging, device management, device twin and Edge (see IoT Hub pricing). We need to check the compatibility with it.

Module CRUD

Here is how it looks like on macOS, which is not quite expected as the font is serif instead of sans serif:

1. Define payload
2. Define interval
3. Define iterations
4. Start simulation (Show status in status bar: Simulating (5/80))
5. Stop simulation (Consider adding 'Stop Simulation' button in status bar, or just ⬛ Simulating (5/80))

Refer to

• https://github.com/Microsoft/vscode-extension-samples/blob/master/progress-sample/src/extension.ts
• https://docs.microsoft.com/en-us/cli/azure/ext/azure-cli-iot-ext/iot/device?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-device-simulate

Reference from https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-monitor-cli#create-a-deployment

--target-condition - Enter a target condition to determine which devices will be targeted with this deployment. The condition is based on device twin tags or device twin desired properties and should match the expression format. For example, tags.environment='test' or properties.desired.devicemodel='4000x'.

Repro step:

1. Start monitoring D2C messages
2. Click "Send D2C message to IoT Hub" for a device
3. Press Enter directly after input window popup

Expected behavior:
I will see the message printed in output window

Actual behavior:
I can only see one message: Sending message to [IoT Hub]. No D2C message printed in output window.

Currently we don't have auto refresh feature in the treeview because this feature will consume API quota.
We can introduce extension settings to disable/enable the refresh rate and the time interval to mitigate this issue.

Steps to reproduce:

1. Open command palette to execute a command which needs a device as the input such as "Copy Device Connection String".
2. If something wrong happens when the device list is being loaded (such as disconnecting from Internet), the spinner will not be dismissed until you press the ESC button.

The expected behavior is that when there is an error, the spinner should be dismissed automatically and an error message should be shown.

• Monitor D2C
• Device - Manage Device Twin
• Service - Manage Device Twin

Users can now choose the Basic tiers (B1, B2, and B3) when creating IoT Hub, besides the Free and Standard tiers which we currently support. See IoT Hub pricing.

In the long term, we might need to come up with a solution to dynamically load all available pricing tiers.

Repo step:
Open new window of vscode, select iothub, then select subscription.
sometimes, the list of iothub is not listed. It happens more often if you just open a new VS code.

Note: the problem happened randomly. In most cases, it works fine.

https://github.com/Microsoft/vscode-azure-iot-toolkit/wikit

Upstream issue: Azure/iotedge#39

Provide the API to list and create consumer group for IoT Hub.

Desired behavior:

Configure and monitor IoT devices at scale, refer to https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-auto-device-config-cli

Toolkit : 1.3.0

1. select an IoT hub, verify the IoT Hub devices will display well
   here time : 2018-9-12

2. change the time to 2018-9-11

3. click refresh button on toolkit

verify Failed to list IoT Hub devices

From https://github.com/Microsoft/vscode-azure-iot-toolkit/pull/144/files#r212856105

• Perl
• Groovy
• Lua
• C

From https://sandervandevelde.wordpress.com/2018/08/07/azure-iot-client-sdk-now-supports-iot-device-modules/

I thought Start Monitoring D2C Message wasn't working since I knew my device was sending messages, and I could see they were being seen by a stream analytics job which listens to the hub, but the extension wasn't printing anything. It wasn't until I disabled the route that the extension showed me the messages. Is there a way to make it work for all D2C messages rather than only unmatched/unrouted ones?