After a year, I'm still struggling to document rules and changes in a concise logical way. Anyone found a "good" way to keep them for reference?
Rules can be exported, individually or collectively, as JSON formatted files, downloaded and stored offline. The downloaded files can be shared and/or imported.
The only thing I am uncertain of in the preceding sentence is whether the format is JSON or not.
A database backup is recommended before exporting or importing rules.
Edit - just realized my post referred to “storing” roles and not documenting them. For the latter, I have used a combination of the built-in notes section, and log actions.
3 Likes
I guess it's just the "lab rat" in us, have to have proper documentation. JSON is a bit difficult to translate. I was just seeing if I had missed a easy way to keep a notebook of rules I have. Looking at cranking up a C7 next year and was hoping I had a reference at hand. Happy New Year!
1 Like
And you! And you're 100% correct about the lab rat bit!
1 Like
I have been documenting HA flows in an iPad /Mac App Simple Mind Pro.
But now I moving over to HE I am looking at using Node Red.
Not got into it yet, but my understanding is that as you create the rule you have it automatically documented, and stored separately.
Once I have finished migrating everything and replicated baseline functionality then I will spin up an old Pi 3 and try using node red for the more complex models.
1 Like
Not really interested in a different system, but it's good to know that there are other options. I'm sure somewhere in the HE office they document things and could write, or help the Community a template. Thanks!
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
