Cannot import rule from 2.2.7 into 2.2.8, bug to be fixed in 2.2.9

[kahn-hubitat]

I cannot import a rule from a 2.2.7 Json save file into 2.2.8. If I try in rule machine legacy I get this error.

If I try in the new rule machine 5.0 it gets farther but in final import I get this error.

And then the 5.0 rule machine is broken/unuseable with this error and Must be removed and reinstalled to work again.

[sidjohn1]

From the notes on 2.2.8 I’m fairly certain this is not a bug, but intended design.

Do not attempt to import Rule-4.1 rules into Rule Machine, only into Rule Machine Legacy. This is not supported and will throw an error. Rule 5.0 has no backwards compatibility to Rule-4.1.

New App Features in 2.2.8

Release 2.2.8 introduces a number of new features, new apps, and new app features. These include Hub Variables, a new version of Rule Machine, Rule 5.0, Button Controller 5.0, and Button Rule 5.0. Hub Variables We have added Hub Variables as a Setting for the hub. Hub Variables are quite similar to Global Variables in Rule Machine, but implemented in the hub rather than in the RM parent app. This provides for the use of Hub Variables in other apps, not just in RM. Hub Variables are very eff…

New App Features in 2.2.8

No, this really is not possible. The backup of a rule reflects the internals of the app (e.g., Rule-4.1). Under the covers, Rule 5.0 has been rewritten in many areas to make it more efficient. So while it looks mostly like Rule-4.1 on the outside, it actually is very different on the inside. An attempt to map from 4.1 to 5.0 would be a difficult to impossible task, a huge undertaking. So, that's not going to happen. Having said that, there is no reason to move an existing working rule fro…

[kahn-hubitat]

If u read.it again the first attempt is an attempt to import into.
Legacy!. Take a.closer look
.it.is.a bug

[bravenel]

Yes, it's a bug caused by the parent app name change. We are reworking how rule export/import/clone works for the 2.2.9 release, and wlll put in a fix for this problem. There is no interim work around unless the original rule still exists. If it does still exist, a new export will be importable. The import is looking for rules with the parent app named Rule Machine Legacy, which didn't exist in 2.2.7 and prior.

[rob9]

Could a person:

1. Take a current backup
2. Roll back to the previous version (possibly use an older backup from that release)
3. Import the old rule
4. Do a platform upgrade again
5. Export the rule after the upgrade
6. Restore from the backup that was just taken
7. Import the re-exported rule

It is a lot of work--but would that work if someone was desperate?

[kahn-hubitat]

Ya probably but at that point.its easier to rewrite one rule. I.was trying to dup .a rule from one location to another. Thanks.for.the responses.

[Inge_Jones]

Do you have an autonomous punctuation generator?