Well, I said that, because I did not get an answer under the other topic, but now, I was actually able to force MQTT nodes to reconnect with _unsubscribe message.
Although not reliably enough yet, i.e. sometimes MQTT nodes enter the disconnect state permanently, sometimes they do reconnect.
I'm doing this by trial and error.
And after I force a reconnect, I can get retained MQTT messages into a Node-RED flow, even on request with the digitaloak-mqtt node.
It worked as described above, but it seems it was a combination of misconfiguration and a bug. Started another topic specifically about that behaviour.
