@bpwwer , @Javi

After migrating Ryse Plugin from pg3x to eisy, the following issues were observed:

1. Several fields in eisy-ui have no labels. They are: Position, Position State, Power Type, Power Level.

2. The label Online changed to Status. With a value of True, I don't think the updated text for the label is sufficient to identify what it is.

3. The label Shade Speed is now Speed.

4. The value for Position State in pg3x was as an example Stationary. Once updated, the value became 0?

5. Only some of Properties labels are displaying in UD Mobile. Properties that display are Speed & Status. The remaining Properties are displayed as: GV0, GV1, GV2, & GV3. I have synchronized UD Mobile, rebooted eisy and synchronized again with no change.

Edited Friday at 04:31 PM4 days by DennisC
added missing information.

Looks like eisy plugins isn't seeing the NLS file. That's what defines all the strings for label names and maps the numeric values to strings.

I take it a restart of the plugin doesn't fix it? If it doesn't then either the migration didn't fully migrate all files or eisy plugins thinks there's something wrong in the file and doesn't load it. @bmercier @Javi

If happening in both UDM after sync and eisy-ui the profiles were not updated.

There is a bug in profile updates so I would wait until the next eisy-ui release to test. Also requires the current staging of IoX for fix in profile events.

Yes, I did a restart of the plugin and a reboot to eisy, it was the first things I tried.

To me, there is a bigger issue with the migration. All of UD Mobile's Favorites are lost. I just made another post about this.

If the profiles were lost the very possible, same recommendation to wait until next release.

I may have spoke to soon. One of the plugins I migrated was Yolink and after migrating it back, I am not getting values.

When I look in eisy.local, on pg3x tab, it appears to be running. However, when I go to the node, I see internal server error.

I tried restarting the plugin but it didn't help. I am a little hesitant, but should I try rebooting eisy?

Eisy-ui told me all nodes were migrated and asked m if I wanted to remove my PG3 nodes.

When I replied YES, all nodes ceased to function and ALL NODES WERE REMOVED from my polisy. None would function from eisy-ui.

When I reinstalled RYSE, and others, nodes were generically installed again but no programs function.

I have been busy renaming nodes and update jerking programs to use them again. Basically starting from scratch except dead programs still exist but do not activate any restored node.

BTW: after saving each program (after a useless edit) eisy-ui complained about not saving the update each time I attempted to exit (it was). I had to click "Discard" each time to proceed.

Edited Friday at 06:08 PM4 days by larryllix

30 minutes ago, larryllix said:

Eisy-ui told me all nodes were migrated and asked m if I wanted to remove my PG3 nodes.

When I replied YES, all nodes ceased to function and ALL NODES WERE REMOVED from my polisy. None would function from eisy-ui.

When I reinstalled RYSE, and others, nodes were generically installed again but no programs function.

I have been busy renaming nodes and update jerking programs to use them again. Basically starting from scratch except dead programs still exist but do not activate any restored node.

BTW: after saving each program (after a useless edit) eisy-ui complained about not saving the update each time I attempted to exit (it was). I had to click "Discard" each time to proceed.

If on the latest staging /rest/programs/reload or reboot after nodes are recreated. This will reload all programs, but also stop anything currently running, may require browser refresh.

The issue is after a node is deleted it is not longer loaded. This is not something that happens often unless nodes are removed then re-added, when not loaded the do not work until reloaded.

To close out issue with Yolink, restarting or reinstalling the plugin didn't work. I finally rebooted eisy and that did work, so Yolink is running.

Still have an issue with Ryse Shades, I can not get the Properties labels back. The plugin has been moved back to pg3, has been restarted several times, and I tried reinstalling the plugin. The Properties labels are still displaying as shown in my screenshots in my first post.

@Javi @bpwwer , anyway to get the Properties labels to show as before the migration in eisy-ui or UD Mobile? Will they restore after this is addressed by the next update?

If it does not work in PG3, then there is likely an issue with the plugin or configuration and something no longer exists. If the plugin is working but node addresses have changed then, likely not, but you can synchronize, do NOT clear cache then change any favorites to the new node IDs, both will now exist in the app.

2 minutes ago, Javi said:

If it does not work in PG3, then there is likely an issue with the plugin or configuration and something no longer exists. If the plugin is working but node addresses have changed then, likely not, but you can synchronize, do NOT clear cache then change any favorites to the new node IDs, both will now exist in the app.

I have tried restarting the plugin, reinstalling the plugin, and finally restarting eisy.

The plugin is working and there have been no changes to node addresses. I have also synchronized UD Mobile, but UD Mobile is still not showing Properties names.

However, when I went in to check the plugin, I noticed on the nodes tab that the name field in the table for the node is blank. The driver column has the expected values GV0, GV1, ect.

I need to figure out how to get that column to populate. I just tried restart plugin and reinstall plugin but it did not help. eisy was rebooted a few minutes before that.

35 minutes ago, DennisC said:

However, when I went in to check the plugin, I noticed on the nodes tab that the name field in the table for the node is blank. The driver column has the expected values GV0, GV1, ect.

The plugin doesn't support populating that field so it should be blank.

I just migrated the plugin and everything seems fine. But I am running on the latest releases from staging. I've restarted the plugin, reinstalled the plugin and it continues to show all the proper labels.

16 minutes ago, bpwwer said:

The plugin doesn't support populating that field so it should be blank.

I just migrated the plugin and everything seems fine. But I am running on the latest releases from staging. I've restarted the plugin, reinstalled the plugin and it continues to show all the proper labels.

Well, then that is not my problem.

After migrating back to pg3, I lost the names as shown in my screenshot.

I have Ryse running at a second location and it does have the names properly showing. That's in my second screenshot.

I have restarted the plugin, reinstalled the plugin, and rebooted eisy. I am also running staging and updated today.

I am at a loss as to what to try next.

I understand and it's frustrating. I've been working with @Javi on another plugin that had issues migrating. It took a while to track that one down and as a result, there have been a couple of fixes.

You don't mention any versions or even if your on the latest production/beta/staging release so the assumption is most people are on the production branch which is why he recommended that wait for the fixes in staging to make it into production and retest. I was confirming that the plugin seemed to migrate fine using the staging branch.

The fact that the labels are missing after migrating back to PG3 is most likely another symptom of the same issue. When the plugin starts, it sends the profiles files (which is where the labels are defined) to IoX. There's some process to synchronize those with eisy-ui. That's were the problem is and that's also what the fixes @Javi mentioned address. With the admin console, the sync happened when the admin console was started.

There's not really anything you can do other than wait for the fixes. It's possible that something will trigger the sync and the labels will just suddenly show up.

51 minutes ago, bpwwer said:

I understand and it's frustrating. I've been working with @Javi on another plugin that had issues migrating. It took a while to track that one down and as a result, there have been a couple of fixes.

You don't mention any versions or even if your on the latest production/beta/staging release so the assumption is most people are on the production branch which is why he recommended that wait for the fixes in staging to make it into production and retest. I was confirming that the plugin seemed to migrate fine using the staging branch.

The fact that the labels are missing after migrating back to PG3 is most likely another symptom of the same issue. When the plugin starts, it sends the profiles files (which is where the labels are defined) to IoX. There's some process to synchronize those with eisy-ui. That's were the problem is and that's also what the fixes @Javi mentioned address. With the admin console, the sync happened when the admin console was started.

There's not really anything you can do other than wait for the fixes. It's possible that something will trigger the sync and the labels will just suddenly show up.

I'm on staging:

eisy-ui = 1.4.8

Iox = 6.1.2_14

PG3x = 3.4.28

Thanks for the update.

So maybe it's a similar, but different issue.

The only way I know of to check eisy-ui is to look at http://eisy.local/api/profiles Unfortunately this is a big XML file. The browser should allow the option to show it formatted and then you have to search for ryse in there. You should find something like this:

"nodedefs": [
              {
                "id": "shade",
                "nls": "shade",
                "icon": "Output",
                "name": "RYSE SmartShade",
                "properties": [
                  {
                    "id": "ST",
                    "editor": "bool",
                    "name": "Online"
                  },
                  {
                    "id": "GV0",
                    "editor": "shade_position",
                    "name": "Position"
                  },
                  {
                    "id": "GV1",
                    "editor": "shade_state",
                    "name": "Position State"
                  },
                  {
                    "id": "GV2",
                    "editor": "power_type",
                    "name": "Power Type"
                  },
                  {
                    "id": "GV3",
                    "editor": "power_level",
                    "name": "Power Level"
                  },
                  {
                    "id": "SPEED",
                    "editor": "shade_speed",
                    "name": "Shade Speed"
                  }
                ],

The name field under GV1, GV2, etc. is the label. If it's there, eisy-ui should be showing it, if it's not, the eisy-ui isn't syncing properly (most likely). You can also check http://eisy.local/rest/profiles. This one should be the same, but comes directly from IoX instead of from eisy-ui. If IoX is correct and eisy-ui isn't, is definitely is a sync problem.

Searching for ryse turned up nothing, so I searched for shade instead. It looks to me like the "name" name field is missing from several of the problematic nodes.

I appreciate you taking the time with this.

The others; speed and status are generic names that IoX assigns internally for those driver types so they're really missing too.