Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / iotblackbelt/node-red-contrib-azure-iot-device issues and pull requests

#37 - Duplicate Messages

Issue - State: open - Opened by Shiny380 about 1 year ago

#36 - Node not reconnecting after internet outage

Issue - State: open - Opened by IoTHuman over 1 year ago - 2 comments

#35 - TLS migration to new CA

Issue - State: open - Opened by defyingcaesar almost 2 years ago

#34 - Add memory-backed store-forward buffer

Pull Request - State: closed - Opened by kgn-dkau2mation almost 2 years ago

#33 - Added support for Proxy in WS

Pull Request - State: open - Opened by kurago-dev about 2 years ago

#32 - Missing error handling in initiateDevice

Issue - State: open - Opened by mochr about 2 years ago

#30 - node-red container error and restarting

Issue - State: open - Opened by luisfdo85 about 2 years ago - 8 comments
Labels: bug

#29 - Sending telemetry with properties, wrong format?

Issue - State: closed - Opened by hixfield about 2 years ago - 2 comments

#28 - Support for iothub-creation-time-utc when sending telemetry

Issue - State: closed - Opened by hixfield about 2 years ago - 8 comments

#27 - Incorrect azure-iot-device-amqp version in 0.2.4?

Issue - State: closed - Opened by dsschneidermann almost 3 years ago - 3 comments
Labels: bug

#26 - Why is SAS key visible in logging

Issue - State: closed - Opened by sandervandevelde almost 3 years ago - 2 comments
Labels: bug

#25 - New device on another flow: message "leakage" between devices?

Issue - State: closed - Opened by packnologyusa about 3 years ago - 6 comments
Labels: bug

#24 - TypeError exception with desired properties message

Issue - State: closed - Opened by packnologyusa about 3 years ago - 2 comments
Labels: bug

#23 - Setting message system properties

Issue - State: open - Opened by packnologyusa about 3 years ago - 2 comments
Labels: enhancement

#22 - Commands defined within scope of "Components" are not processed (Azure IOT Central)

Issue - State: closed - Opened by peterheldens over 3 years ago - 2 comments
Labels: No issue

#21 - Node-Red device fails provisioning using CA certificates

Issue - State: closed - Opened by adnorin over 3 years ago - 3 comments
Labels: bug

#20 - Adding env variables to override the node configuration

Pull Request - State: closed - Opened by felipe-dossantos-dev over 3 years ago - 1 comment

#19 - Transitioning from "node-red-contrib-azure-iot-hub" palette

Issue - State: closed - Opened by mgKeeKrog over 3 years ago - 4 comments

#18 - `Device provisioning failed` is shown though sending telemetry is successful

Issue - State: closed - Opened by dzeyelid over 3 years ago - 2 comments
Labels: bug

#17 - Fix the "conntype == connection string" flow. It's broken in 0.2.2

Pull Request - State: closed - Opened by ghassansalloum over 3 years ago

#15 - Documentation for "Device ID" should mention it's the "Registration ID" if using the DPS method?

Issue - State: closed - Opened by ghassansalloum over 3 years ago - 3 comments
Labels: bug, documentation

#14 - Cannot connect with connection string and without PnP and device provisioning.

Issue - State: closed - Opened by aamrcg over 3 years ago - 5 comments
Labels: bug, duplicate

#13 - [Feature] Configurable buffering concept in case of connection loss

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: wontfix

#12 - [Feature] Check connection to IoT Hub

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: enhancement

#11 - [Feature] Allow setting node configuration via incoming msg

Issue - State: open - Opened by dkby almost 4 years ago - 7 comments
Labels: enhancement

#10 - MQTT message buffering during temporary internet connection loss (duplicate messages)

Issue - State: closed - Opened by dkby almost 4 years ago - 2 comments
Labels: duplicate, enhancement

#9 - Device twin is not updated after reestablishing a temporally broken internet connection

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: bug

#8 - Invalid certificates lead to crash of node-red

Issue - State: closed - Opened by dkby almost 4 years ago - 4 comments
Labels: bug

#7 - Uncaught exception while stopping flows when offline

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: bug

#6 - Errors cannot be caught using node-red "catch" node

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: enhancement

#5 - No connection and node-red crashes when internet connection is down during and after deploy

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: bug

#4 - Connection is not re-established when internet connection temporarily breaks for more than 5 minutes

Issue - State: closed - Opened by dkby almost 4 years ago - 1 comment
Labels: bug

#3 - Proposal: Support telemetry message properties

Issue - State: closed - Opened by sandervandevelde almost 4 years ago - 3 comments

#2 - CA Certificate not read correctly

Issue - State: closed - Opened by iotblackbelt about 4 years ago - 1 comment

#1 - how to deploy the node within Node-Red

Pull Request - State: closed - Opened by sandervandevelde about 4 years ago