Rule Machine Version Migrations

📐 Rule Machine® All things Rule Machine
1

@bravenel I know this has been brought up in the past and it was deemed impossible or very challenging to migrate between say RM4.0 and RM5.0, However, it occurred to me that there might be a way to do this.

Would it be possible for a migration tool to perform a high-level conversion via the Psuedo code rather than the underlying JSON?

So taking the below example (admittedly a fairly simple one), could an official Hubitat migration tool re-use the visualization portion of each RM version to convert the JSON to the high-level Psuedo code, and then use that to convert the logic to the current RM version?

Screen Shot 2021-08-03 at 10.47.10 am
Screen Shot 2021-08-03 at 10.47.10 am907×413 37.7 KB

I realise converting all RM Rule's won't be possible (eg RM3 is apparently a very different beast) and some logic scenarios will not migrate at all (eg rules using old global variables), but this would be super useful for moving RM4.x Rules to RM5.x. RM4.0 is a bit of a dog performance-wise (editing big rules is really slow) and it would be nice to have a migration path to the high performing, more capable versions of RM.

Thoughts?

2

This would be an app with the same order of magnitude of complexity as Rule 5.0 itself, perhaps more. Hardly something we would want to do, given that there is little need to move rules from one version to another (if it works now, why move it?). In fact, it's probably impossible as there is no detail about devices, variables, etc, no context.

3 Likes
3

No worries, I was just curious. :+1:

4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.