azure-iot-sdk-csharp | connecting devices to Microsoft Azure IoT services | Azure library

by Azure C# Version: 2023-05-01 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | azure-iot-sdk-csharp Summary

azure-iot-sdk-csharp is a C# library typically used in Cloud, Azure applications. azure-iot-sdk-csharp has no bugs, it has no vulnerabilities and it has low support. However azure-iot-sdk-csharp has a Non-SPDX License. You can download it from GitHub.

A C# SDK for connecting devices to Microsoft Azure IoT services

Support

Quality

Security

License

Reuse

Support

azure-iot-sdk-csharp has a low active ecosystem.

It has 434 star(s) with 493 fork(s). There are 95 watchers for this library.

It had no major release in the last 12 months.

There are 9 open issues and 907 have been closed. On average issues are closed in 64 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of azure-iot-sdk-csharp is 2023-05-01

Quality

azure-iot-sdk-csharp has 0 bugs and 0 code smells.

Security

azure-iot-sdk-csharp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

azure-iot-sdk-csharp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

azure-iot-sdk-csharp has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

azure-iot-sdk-csharp releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of azure-iot-sdk-csharp

Get all kandi verified functions for this library.

azure-iot-sdk-csharp Key Features

No Key Features are available at this moment for azure-iot-sdk-csharp.

azure-iot-sdk-csharp Examples and Code Snippets

No Code Snippets are available at this moment for azure-iot-sdk-csharp.

Community Discussions

Trending Discussions on azure-iot-sdk-csharp

Azure DeviceClient does not shut down dotnetty threads on program exit

DeviceClient SetMethodDefaultHandlerAsync not invoked timely

QUESTION

Azure DeviceClient does not shut down dotnetty threads on program exit

Asked 2022-Jan-25 at 22:08

When using Microsoft.Azure.Devices.Client.DeviceClient .net framework 4.8 closing out the application leaves multiple Threads running. Specifically DotNetty.Common.dll! DotNetty.Common.Concurrency.SingleThreadEventExecutor.PollTask

Versions 1.34.0 & 1.35.0 of Microsoft.Azure.Devices have this same problem. Are we using DeviceClient improperly? Is it a async thing im not understanding? Am i missing a call to shut it down properly?

From examples online, i shouldn't have to do anything special and it should close it self out. However it still hangs, currently this is a close implementation. I have yet to make a stand alone, so i havent duplicated this problem with only DeviceClient Code running

When the program exits, is_running gets set, and the program closes down other threads. Eventually we call Environment.Exit(0);

This should be all the relevant code

...

ANSWER

Answered 2022-Jan-25 at 22:08

https://github.com/Azure/azure-sdk-for-net/issues/24550 https://github.com/Azure/azure-iot-sdk-csharp/issues/2194

Not a configuration issue, a 'dot netty' bug was hanging. The fix, get a newer azure version Microsoft.Azure.Devices > 1.35.0

Source https://stackoverflow.com/questions/69485035

QUESTION

DeviceClient SetMethodDefaultHandlerAsync not invoked timely

Asked 2020-Aug-31 at 09:12

Describe the bug

DeviceClient SetMethodDefaultHandlerAsync handler is not triggered on internet disconnection instantly. It triggers after 15 to 20 minutes. Below are the logs

IoT Hub connection status Changed Status: Connected Reason: Connection_Ok Time: 3:09:15 PM +02 IoT Hub connection status Changed Status: Disconnected_Retrying Reason: Communication_Error Time: 3:26:29 PM +02

I disconnected the internet at 3:10:00 PM +02 and communication error was thrown after 16 minutes. I have created a sample code which reproduces the issue

Steps to reproduce

...

ANSWER

Answered 2020-Aug-31 at 08:08

As per the outcome of discussion in github: https://github.com/Azure/azure-iot-sdk-csharp/issues/1409

The SDK is relying on the OS TCP stack to inform that the disconnect has happened, and the OS can take a couple of retries before relaying this information. This might be what is causing the connection status change handler to get invoked with a 15min delay on Linux.

For Mqtt, the client does send a ping request every 75 seconds, but does not seem to be monitoring the ping response being received from the broker.

PS: This is not occurring when using Windows 10 OS

Update

Added a fix for the mqtt layer, where the sdk now monitors for a ping response and disconnects if the delay between sending a ping request and receiving a response is >30secs (this value is currently not configurable).

For the amqp implementation, the amqp library encapsulates this ping request-response logic from us; all that the device sdk does is set the IdleTimeout.

Source https://stackoverflow.com/questions/62509807

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install azure-iot-sdk-csharp

Due to security considerations, build logs are not publicly available.

Support

Have a feature request for SDKs? Please post it on User Voice to help us prioritize.Have a technical question? Ask on Stack Overflow with tag “azure-iot-hub”.Need Support? Every customer with an active Azure subscription has access to support with guaranteed response time. Consider submitting a ticket and get assistance from Microsoft support team.Found a bug? Please help us fix it by thoroughly documenting it and filing an issue on GitHub (C, Java, .NET, Node.js, Python).

Find more information at: