Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / lcarli/NodeRedIoTHub issues and pull requests
#47 - Add ContentType and ContentEncoding
Pull Request -
State: open - Opened by ttrichar 4 months ago
#46 - Question: Pass IoT hub Identity via config
Issue -
State: open - Opened by ChangeTheCode 7 months ago
#45 - TypeError: Cannot read properties of undefined (reading 'fromConnectionString')
Issue -
State: open - Opened by beasteers about 1 year ago
#44 - simple security patch
Pull Request -
State: closed - Opened by MarianRaphael almost 2 years ago
#43 - Usage with data array and timestamps
Issue -
State: open - Opened by fludki over 2 years ago
#42 - node-red-contrib-azure-iot-hub deconnections
Issue -
State: open - Opened by ghost over 3 years ago
- 1 comment
#41 - Security of the IoT-Hub-Node
Issue -
State: open - Opened by itscooljo over 4 years ago
#40 - Connectivity Status of Azure IoT Hub Nodes
Issue -
State: open - Opened by kaushalkumarjoshi over 4 years ago
#39 - npm ERR! No valid versions available for node-red-contrib-azure-iot-edge
Issue -
State: closed - Opened by kpm-at-hfi over 4 years ago
#38 - IoT Hub Receiver gives missing property keyName
Issue -
State: open - Opened by Narragansett over 5 years ago
- 1 comment
#37 - Consumer Group support
Issue -
State: open - Opened by maurert over 5 years ago
#36 - Iot-hub receive stops working around 40 seconds after re-deploy
Issue -
State: open - Opened by maurert over 5 years ago
#35 - Multiple Azure IoT Hub nodes refuse connection
Issue -
State: open - Opened by janoschjg over 5 years ago
- 1 comment
#34 - Update package.json
Pull Request -
State: closed - Opened by MichelCollard over 5 years ago
#33 - Selected protocol not being used
Issue -
State: closed - Opened by jebreur over 5 years ago
#32 - Dependencies update
Issue -
State: open - Opened by MichelCollard over 5 years ago
- 4 comments
#31 - undefined key causes Node-RED crash
Issue -
State: open - Opened by rcarmo almost 6 years ago
- 1 comment
#30 - Cannot populate Node with data via msg object
Issue -
State: open - Opened by mfisher75 almost 6 years ago
#29 - Nodes don't "remember" keys and hostname data
Issue -
State: open - Opened by mfisher75 almost 6 years ago
#28 - Azure IoT Hub Node TypeError: Cannot read property 'removeAllListeners' of undefined
Issue -
State: open - Opened by mfisher75 almost 6 years ago
#27 - Exception from Node Red that terminates the flow
Issue -
State: open - Opened by mfisher75 about 6 years ago
#26 - Node outputs as string instead of object
Issue -
State: open - Opened by L-P-G about 6 years ago
- 1 comment
#25 - Error connecting to Azure from Simatic IoT with Linux Yocto
Issue -
State: open - Opened by Nemo1710 over 6 years ago
- 1 comment
#24 - [armv7] Error while trying to send message:Unauthorized
Issue -
State: closed - Opened by daniel6096 over 6 years ago
- 1 comment
#23 - TypeError: this.mqttprovider.connect is not a function
Issue -
State: open - Opened by DanielT2408 over 6 years ago
- 8 comments
#22 - Routing Device Messages with IoTHub to different Endpoints
Issue -
State: open - Opened by DanielT2408 over 6 years ago
- 2 comments
#21 - Flows stopped due to missimg node types
Issue -
State: closed - Opened by rhoddan over 6 years ago
- 3 comments
#20 - Incremented version to 0.4.0 signifying feature changes
Pull Request -
State: closed - Opened by rasavant-ms over 6 years ago
#19 - Updated README.md file with new node information
Pull Request -
State: closed - Opened by rasavant-ms over 6 years ago
#18 - Handling of errors on message publishing
Issue -
State: open - Opened by vitaliyonoshko almost 7 years ago
#17 - Added node for retrieving Device Twin data
Pull Request -
State: closed - Opened by kasarol almost 7 years ago
#16 - TypeError: node.log is not a function (Node-RED in Azure)
Issue -
State: open - Opened by topese almost 7 years ago
- 2 comments
#15 - Iothubreceiver
Pull Request -
State: closed - Opened by kasarol almost 7 years ago
- 1 comment
#14 - Connection String Error
Issue -
State: closed - Opened by ProgrammingPescador almost 7 years ago
- 3 comments
#13 - Waiting for missing types to be registered: - azureiothub
Issue -
State: closed - Opened by sandrisj about 7 years ago
- 2 comments
#12 - C2D Received data
Issue -
State: closed - Opened by Gadnief about 7 years ago
- 2 comments
#11 - "azureiothub" node does not export "Hostname"
Issue -
State: closed - Opened by maniwilliams over 7 years ago
- 2 comments
#10 - "TypeError: transportCtor is not a constructor"
Issue -
State: closed - Opened by SjorsHijgenaar over 7 years ago
- 9 comments
#9 - Reconnect on connection losses
Pull Request -
State: closed - Opened by sandro-k over 7 years ago
#8 - node.log is not a function
Issue -
State: closed - Opened by mariocytr over 7 years ago
- 2 comments
#7 - Small fix for logging and the protocol property never being used
Pull Request -
State: closed - Opened by pferland-multitech over 7 years ago
#6 - Wrong data sent to IoT Hub
Issue -
State: closed - Opened by beneuto over 7 years ago
- 3 comments
#5 - Connection String Error
Issue -
State: closed - Opened by retom over 7 years ago
- 2 comments
#4 - missing type
Issue -
State: closed - Opened by lucarv almost 8 years ago
- 1 comment
#3 - SyntaxError: Unexpected token [
Issue -
State: closed - Opened by roqvist almost 8 years ago
- 2 comments
#2 - Fix for node reference issue
Pull Request -
State: closed - Opened by jongio about 8 years ago
#1 - Beefing up the README with examples and sample code.
Pull Request -
State: closed - Opened by jongio about 8 years ago