A Python SDK for connecting devices to Microsoft Azure IoT services
MIT License
Bot releases are visible (Hide)
Published by olivakar about 4 years ago
Published by olivakar about 4 years ago
Published by olivakar over 4 years ago
Published by BertKleewein over 4 years ago
This includes architectural and testing changes that should not be visible to clients. The purpose of this change is to increase stability maintainability.
Update code samples for clarity
Enhancement to enable creation of PnP compatible devices.
Bug fix: removed dependence of certificate creation script on openssl.
This allows clients to specify the token renewal interal when using symmetric key authentication.
This fixes a was a race condition which would cause the client to stop functioning if the client was communicating with IoT Hub when a SAS renewal event took place, which happens every 50 minutes by default.
This fixes some overly-aggressive reconnect logic which would cause the client to reconnect with IoTHub after the disconnect
method was called. Depending on the behavior of the customer's code, this could cause multiple client instances to be active and to contend for resources (including the single network connection that is allowed by the hub). More details are on the common pitfalls page
Enables Device Twin array support
The common pitfalls page has information on some known issues and common problems.
Published by olivakar over 4 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by cartertinney over 4 years ago
.invoke_device_method()
and .invoke_device_module_method()
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by cartertinney over 4 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
Published by cartertinney over 4 years ago
NOTE WELL: This LIMITED AVAILABILITY RELEASE is only compatible with the following Azure regions: East US, South Central US, and West US 2
This is a LIMITED AVAILABILITY RELEASE and is not being distributed via the Python Package Index (PyPI).
Instead, please install by downloading the attached .whl file under the "assets" header of this release. Once you have downloaded the release file (azure_iot_hub-2.2.0_limited-py2.py3-none-any.whl
), open command line and navigate to the folder with the downloaded file. Run pip install ./azure_iot_hub-2.2.0_limited-py2.py3-none-any.whl
to install this version of the Azure IoT Hub Library.
A future mainline release of the Azure IoT Hub Library will include these features once support for VNETs is widely available on all Azure regions.
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by olivakar over 4 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by olivakar over 4 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by cartertinney almost 5 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by cartertinney almost 5 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
Published by cartertinney almost 5 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
Published by cartertinney about 5 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
Published by cartertinney about 5 years ago
https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-hub/samples
Published by cartertinney about 5 years ago
requests
libraryhttps://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples
Published by pierreca almost 6 years ago
Published by pierreca almost 6 years ago
Published by pierreca almost 6 years ago
We are snapping to the latest LTS (Long-Term Support) version of the C SDK and therefore declaring our 1.4.x series of update the LTS branch.
We will be publishing new features under the 1.5.x denomination in the future.
This is also a good time to let everybody know that we've seen and heard the feedback loud and clear about the many pains caused by having to wrap the C SDK using Boost (and the ensuing platform incompatibilities). At that point we've started a complete re-write of the SDK in pure, cross platform python.
As soon as we have a partial-feature SDK preview ready we will communicate this in the readme and start redirecting new users to the preview of the v2 SDK.
Published by pierreca about 6 years ago
Fixes: