martin-doyle

Additional observation. This behaviour exists only if you do a "Full" deploy or stop Node-RED. It does not occur when deploy Modified Flows or Modified Nodes only.

There is a fix for the Node-RED MQTT node in preparation. See [Ensure mqtt-close message is published when closing mqtt nodes](https://github.com/node-red/node-red/commit/04a3c4bb222f1708877ddd98379be801bfc6fc72). I will check the next Node-RED release and see...

Unfortunately, Node-RED 1.3.3 does not fix this issue. Looking at the logs it seems that Node-RED closes the broker first and then the MQTT nodes. The MQTT nodes send a...

Cool. Yes please do. Thanks a lot.

Hi Steve, thank you for providing this fix. Unfortunately, it did not work on my computer with Node-RED V2.2.1. But I can confirm that version **2.2.2** works now.

Currently persistence between Node-RED restarts is only supported for MongoDB. Aedes provides a few more storage options. NeDB might be an option if persistence without an external database is required....

There is a new branch NeDB. Would you mind testing it? Martin

Unfortunately, the stability test for the NeDB persistence failed. This needs more investigation.

To be honest I did not test it since then. Did you try the NeDB branch?

OK. I will check it. It is supported by aedes now.