I only have three plugins. I have migrated one already with success after a short lived problem with emails using the plugin values.

Now that eisy Plugins are no longer in BETA, I decided to migrate my VUE plugin. The VUE plugin has about 20 nodes and I have given each node a custom name.

When I migrated the plugin from PG3x to eisy, the custom names were altered.

For example, if the node name was "Label Prefix | Label Description" it migrated as "Label Description Label Prefix".

Because I didn't know what else may have been altered, I decided to migrate it back to PG3x. Unfortunately, the messed up node names now persisted after the reverse migration.

Again, not know what was happening, I decided my only option was to do a full restore of my most recent backup, which corrected everything.

This doesn't seem like the result we should expect with any plugin, so decided I should report this here.

Rob

On 10/18/2026 at 9:07 AM, RRalston said:

I only have three plugins. I have migrated one already with success after a short lived problem with emails using the plugin values.

Now that eisy Plugins are no longer in BETA, I decided to migrate my VUE plugin. The VUE plugin has about 20 nodes and I have given each node a custom name.

When I migrated the plugin from PG3x to eisy, the custom names were altered.

For example, if the node name was "Label Prefix | Label Description" it migrated as "Label Description Label Prefix".

Because I didn't know what else may have been altered, I decided to migrate it back to PG3x. Unfortunately, the messed up node names now persisted after the reverse migration.

Again, not know what was happening, I decided my only option was to do a full restore of my most recent backup, which corrected everything.

This doesn't seem like the result we should expect with any plugin, so decided I should report this here.

Rob

The plugin is reinstalled in eisy-ui.

As part of the process, nodes are removed from IoX, and they are recreated by the plugin.

This means their names are reset to their default names.

I'll see if there would be a way to preserve the name.

@RRalston Please upgrade PG3x to 3.4.28 and try again. This is published to the beta repo.

This should preserve the names, scene membership, etc.

The node is no longer removed from IoX when migrating.

@bmercier Oh yeah. That is much better! Thank you for the quick resolution.

Rob