Dependencies update

[MichelCollard]

An update for the dependencies would probably fix a lot of problems.

I always got the message: "Error while trying to send message:Error: AMQP Transport: Could not send" on every second message in a "batch". This happened when sending multiple message while the connection was not yet established.
Updating the following packages fixed it for me:

• azure-iot-device
• azure-iot-device-amqp
• azure-iot-device-amqp-ws
• azure-iot-device-http
• azure-iot-device-mqtt

Is there a reason for the current way the dependencies are set up?

[sam-connolly]

�[91mnpm WARN deprecated azure-iot-device-amqp-ws@1.0.14: The Amqp over Websockets feature is now provided by azure-iot-device-amqp.AmqpWs
�[0m�[91mnpm WARN deprecated azure-event-hubs@0.0.8: < 0.2.12
�[0m�[91mnpm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
�[0m�[91mnpm WARN deprecated node-uuid@1.4.8: Use uuid module instead
�[0m�[91mnpm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
�[0m�[91mnpm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
�[0m�[91mnpm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
�[0m�[91mnpm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
�[0m�[91mnpm WARN deprecated�[0m�[91m hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

I'm receiving these warnings when installing the node-red-contrib-azure-iot-hub package. Is this expected?

[DavidDeeds]

Hi @MichelCollard - a newb question from me - how (where?) did you update the packages.json file in Linux that you mention in the first post? I understand the issue being the versioning <= which is not good.

And then did you run a command to update the below somehow?

azure-iot-device
azure-iot-device-amqp
azure-iot-device-amqp-ws
azure-iot-device-http
azure-iot-device-mqtt

I'm using NodeRed on Raspian Stretch and struggling to get this NodeRedIoTHub stable..
Any and all help appreciated! (I'm clearly not a linux guru but trying!) :)

[MichelCollard]

Hi @MichelCollard - a newb question from me - how (where?) did you update the packages.json file in Linux that you mention in the first post? I understand the issue being the versioning <= which is not good.

And then did you run a command to update the below somehow?

azure-iot-device
azure-iot-device-amqp
azure-iot-device-amqp-ws
azure-iot-device-http
azure-iot-device-mqtt

I'm using NodeRed on Raspian Stretch and struggling to get this NodeRedIoTHub stable..
Any and all help appreciated! (I'm clearly not a linux guru but trying!) :)

You will have to make a new package and update the package.json.
After that you can run the Install or Update command.
When you are done doing this, the package needs to be reinstalled in Node-Red.
You will be able to find most of the information in the Node-Red documentation.
Good luck!

[MichelCollard]

�[91mnpm WARN deprecated azure-iot-device-amqp-ws@1.0.14: The Amqp over Websockets feature is now provided by azure-iot-device-amqp.AmqpWs
�[0m�[91mnpm WARN deprecated azure-event-hubs@0.0.8: < 0.2.12
�[0m�[91mnpm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
�[0m�[91mnpm WARN deprecated node-uuid@1.4.8: Use uuid module instead
�[0m�[91mnpm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
�[0m�[91mnpm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
�[0m�[91mnpm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
�[0m�[91mnpm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
�[0m�[91mnpm WARN deprecated�[0m�[91m hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

I'm receiving these warnings when installing the node-red-contrib-azure-iot-hub package. Is this expected?

Sorry, I don't know. I didn't open the project since I posted this issue.
If you are able to fix it, you could always make your own fork and post a new solution.