And if so, how?
I have a full C-5 implementation is almost hands-off at this point. (Not that I don't tinker with new stuff, but what works, works well.) I'm trying to decide how to integrate my still-in-the-box C-7 into the setup.
Regardless of how I do that, I have some fear (and I will concede the point of paranoia if raised 
) that my existing rules will get messed up. So, outside of backups -and I have those-, do you keep screenshots, text notes, etc. of how your hub(s) is setup?
I currently keep screen shots of my complicated rules, but when 2.2.4 is ready for release, you will be able to backup rules so this will not be needed.
That was one of the main reasons (there were a few others) that I moved all of my logic to node-red. The way I set it up it automatically gets backed up, and I won't ever lose it.
Soon you will be able to export/import RM rules, though, so once that is released in 2.2.4 that would be something you want to do periodically!
I found writing the rule in a text editor made entering a complex rule much easier. This is especially true then I make a wrong RM path and need to re-start from the beginning.
It also allows me to add notes where needed.
When I'm done I have my documentation. Of course its not the same as an export/import capability in that you would have to reenter the rule manually but it is easy to copy and modify.
BTW I'm not 100% sure the export/import function will extend to the C5.
Example:
I don’t believe that’s a feature that would depend on hub version in any significant way such that C7 would get it but C3/4/5 wouldn’t.
At least I hope not...
It will work on non C-7 hubs.
Off topic: Would you mind sharing how you automatically backup the flows? I am running Node-Red on a RPi4 (using Homebridge image) and so far, have been manually exporting the flows...
Simple - enable projects in node-red and have a private repository in github to save them to. In the latest versions of node-red projects can automatically backup with versioning to github on every download.
@JasonJoel
This is good to know and something I will look into.
Tbh- I had never heard of projects or such feature existed. Very handy! Cheers
Ah! I’ve been thinking about trying that out. Now I have a reason😁
Oh, and obviously you can manually EXPORT all of your flows at any time too, in case you don't want to enable projects. But that is a manual process.
@rakeshg, @bdydrp, and anyone else who's interested ....
When I first created my node-red github repository, I found this instructional video on YouTube to be very useful:
In the past after major changes I have gone to my /data folder and saved the flows file!
But this will save me from having to remember!
Thanks @aaiyar
Will check this out tonight!
Cheers
Nothing wrong with that either!
They've added import/export of Motion rules to the 2.2.4 beta as well now, and I'd think that Simple Automations would be on the list for the future as well. Assuming they add SA at some point, that will allow a pretty comprehensive backup of automations for folks using the built-in apps.
I wish they would enable the import/export features for community apps, as well as the ability to clone automations so you can reuse an existing automation to make a new one, as you can in RM.
Download the Hubitat app
