Please see a screenshot of the mentioned loop.
The marked link out nodes feed the reset messages into the loop. There are currently two messages trapped in the loop (there should only be one message in the loop at a time). This happens occasionally after a re-deploy. Initially, I did not want to share this loop because it won't work without the connected hardware (if somebody wants to test). That’s why I created the example flows in the initial post. Hopefully the screenshot helps to understand what I am trying to achieve.
Again, my goal is to come up with a set of nodes which allow a robust reset and restart of the loop.
