I found this thread after upgrading from a pre 1.3. version of NR to 2.2 a few days ago:
Error stopping node: Close timed out - MQTT nodes
https://discourse.nodered.org/t/error-stopping-node-close-timed-out-mqtt-nodes/52830/10
Unfortunately I can't reply to the thread as it is closed, however @Colin can you please advise why you wrote this comment?
"Generally, in my opinion, it is better to use Mosquitto. It is very easy to install and configure."
The background of my question:
- I have been using aedes broker for a limited amount of devices for sometime now and it works perfectly.
- I upgraded to v2.2. a few days ago and the timeout issue occurred, which I have now found out is a common issue
- I am ok to workaround the issue, even though it leads to a 20-30 second delay to the clients finishing their subscription with the broker on a restart
- I have recently setup a master/slave NR setup, whereby the Master NR instance has the Aedes broker installed (node-red contrib) and the slaves are connecting to it
- The plan is for 1x Master and 8x Slaves to be setup to support about 205 physical zwave devices
- Each of the slave NR instances have a zwave controller installed (nr-zwave-js - node-red-contrib-zwave-js (node) - Node-RED) and the zwave devices are being added to those slaves
- So far from testing across a setup of 1x Master and 3x Slaves, Aedes is working perfectly sending and receiving zwave messages from the Slave NR instances to the Master NR instance, however after reading your comment I am suspecting that I may/will run into issues as I transfer more devices across to the Slave NR instances
My nest step is to see how to setup a MQTT broker outside of NR, but I'd like to understand why I am doing it before I potentially run into issues with my current setup.