Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all devices load when IoT Hub has many devices #537

Open
rtheil opened this issue Nov 16, 2021 · 6 comments
Open

Not all devices load when IoT Hub has many devices #537

rtheil opened this issue Nov 16, 2021 · 6 comments

Comments

@rtheil
Copy link

rtheil commented Nov 16, 2021

Our production IoT Hub has many hundreds of devices in it. In the rare instance when we must push a deployment to a single edge device, we use this plugin to do so. The problem is that the list of devices doesn't contain all the devices in the hub. We use both edge and non-edge devices. Now we've reached a point where many devices do not show up, and we are unable to publish to a single device. Even using command palette we can't just type the name of the device to publish to because it's not in the list.

@AleksandrLiakhavetsEPAM
Copy link

Did you resolve this issue?

@rtheil
Copy link
Author

rtheil commented Jan 6, 2023

@AleksandrLiakhavetsEPAM No. I've resorted to manually pushing deployments to devices using the azure command prompt.

@Delapouite
Copy link

Delapouite commented May 5, 2023

Related to this old issue in the previous extension : microsoft/vscode-azure-iot-tools#20

The underlying problem appears to be the limit of 1000 devices.

I agree that in many situation you want to target a specific device and you already know its id.

Therefore, instead of having to browse through a huge list, the UI could offer a way to just type the id of the device and they do whatever you need to perform with it.

@rtheil
Copy link
Author

rtheil commented May 5, 2023

I gave up. I use the az command now and have written a powershell script that does all the work for me. This extension is completely useless,

@rido-min
Copy link
Member

rido-min commented May 5, 2023

The main goal of this extension is to provide an easy way to interact with hub devices while developing your solution, and it is not intended to be used in production with thousands of devices.

You should be able to use az iot to interact with specific devices, including edge.

@rtheil
Copy link
Author

rtheil commented May 5, 2023

It's understandable that it's not a tool meant for production use, but we're beyond that now. We have 1153 devices in our development IoT hub, which was not the case when I originally opened this issue. This tool basically uses the az command to push a deployment to a device. It's just strange to justify the limit based on the idea that it's not meant for production. All this needs is the ability to just enter the deviceId outside of the list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants