3 hours ago, bmercier said:

eisy-ui plugins is no longer beta.

It is released to production under eisy-ui 1.4.4.

Thanks @bmercier , up dated and everything seems fine

Question, after every update I'm left with an error loading group and a reboot doesn't fix. Pulling the power is always required.

Is this expected behaviour?

4 hours ago, bmercier said:

eisy-ui plugins is no longer beta.

It is released to production under eisy-ui 1.4.4.

Migrated this morning. All seems good except I cannot migrate PG3 plug-ins. I've tried 4 and I get the same message on each "Error getting PG3 plugin config: Request failed with status code 503". Am I doing someting wrong?

Edited October 17Oct 17 by Mr B
Update: Got a fix from UD: Open PG3 at http://eisy.local:3000, Look under IoX Configuration | Edit Current IoX., IP has to be localhost or 127.0.0.1

23 minutes ago, mmb said:

Thanks @bmercier , up dated and everything seems fine

Question, after every update I'm left with an error loading group and a reboot doesn't fix. Pulling the power is always required.

Is this expected behaviour?

Thanks for the tip, @mmb I had to unplug as well to get the plugins operational.

1 hour ago, Bumbershoot said:

Thanks for the tip, @mmb I had to unplug as well to get the plugins operational.

My brother has an almost identical setup as me except a much smaller set of devices. I do his Eisyui updates and see the same behavior on his.

Note: Plugins are unresponsive after the update and subsequent reboot from the Eisy. I checked services and IOX was not running, so started it. That didn't help so restarted the eisyui service, still nothing. Power reboot fixed everything.

Also note, my brother ran into a recent issue that couldn't be fixed so reflash was necessary. So the Eisy should be pretty close to factory except one update. He's a little gun shy about updating to these latest updates.

Let me know if you need any information @bmercier

@Jimbo.Automates When I migrated HomeKit and Ecobee, and then looked at the nodes, the HomeKit Hub nodes all looked normal. But the node for my Ecobee thermostat had an error message, instead of usual readouts & controls. I've not yet had a chance to see what happens if I migrate only one or the other of the two plugins.

All of my other plugins migrated successfully.

UPDATE: Appears to work well when migrating HomeKit, but leaving Ecobee on PG3

UPDATE #2: Re-migrated both plugins to esiy-ui, and everything is working this time:)

Edited 19 hours ago19 hr by BJB2757
New info

@bmercier What to do here? thanks.

Elk plug in is only finding Outputs...

See sample screenshot of log.

Any advice to fix? I have restarted it twice. Will reboot eisy to see if that fixes it.

2 hours ago, dbwarner5 said:

@bmercier What to do here? thanks.

I see an update may solve this.

2 hours ago, dbwarner5 said:

Elk plug in is only finding Outputs...

See sample screenshot of log.

Any advice to fix? I have restarted it twice. Will reboot eisy to see if that fixes it.

Migrated it back to PG3X.. all the nodes are showing in the dashboard of PGX3, but only the output nodes are showing in Eisy UI... Any ideas how to get them to show back up?

Edited October 17Oct 17 by dbwarner5

41 minutes ago, dbwarner5 said:

Migrated it back to PG3X.. all the nodes are showing in the dashboard of PGX3, but only the output nodes are showing in Eisy UI... Any ideas how to get them to show back up?

Solved:

Had to go to the AC and then Plugins / Add all nodes. They are back and working normally again.

I have tried unplugging / restart, and the Add All Nodes suggestion but still getting this error message. The eisy-ui PG3 (Legacy) page is populated with all Plugins connected.

Migrate All results in them all coming over with the same error.

Edited October 17Oct 17 by Phil G
clarity

There are new firmware updates just released that address the PG3 issues

Edited October 17Oct 17 by Techman

1 hour ago, Phil G said:

I have tried unplugging / restart, and the Add All Nodes suggestion but still getting this error message. The eisy-ui PG3 (Legacy) page is populated with all Plugins connected.

Migrate All results in them all coming over with the same error.

I tried the migrate all option and it was a semi-disaster.. eisy crashing, plugins "failed", wont start, etc.. I had to move them all back to PG3X, do a restore to my Eisy and then after getting everything restabilized, I moved them one at a time. That worked. Had trouble with iAuqalink, RATDGO and ELK, so kept them for now on PG3X. A few others with known issues I also did not move; Matter, St-inventory.

Installed the latest update but haven't tried to re-migrate those three yet as I rely on them too much to deal with this weekend.

1 hour ago, dbwarner5 said:

I tried the migrate all option and it was a semi-disaster.. eisy crashing, plugins "failed", wont start, etc.. I had to move them all back to PG3X, do a restore to my Eisy and then after getting everything restabilized, I moved them one at a time. That worked. Had trouble with iAuqalink, RATDGO and ELK, so kept them for now on PG3X. A few others with known issues I also did not move; Matter, St-inventory.

Installed the latest update but haven't tried to re-migrate those three yet as I rely on them too much to deal with this weekend.

@dbwarner5 , to be clear, you had to restore IoX from a backup? Did you do that in A/C or eisy-ui or does it even matter? Thanks for the tip.

1 hour ago, Techman said:

There are new firmware updates just released that address the PG3 issues

I did Upgrade Packages early this morning and then this trouble seemed to start. Not positive though because I only did the big upgrade to eisy-ui late yesterday and still not too familiar with it. You have to love how simple it is now to review package versions and perform upgrades. Boot Environment feature is pretty cool, too. Worth the pains to get to this point in my opinion. Well done, UDI.

On 10/15/2026 at 7:50 PM, Javi said:

If all plugins are migrated, disable pg3 in menu>settings.

Thanks @Javi , I disabled PG3 and did a followup check on EisyUI Services and PG3X is still running.

Are there legacy PG3 bits that are still needed requiring the service to continue to run?

My PG3 (Legacy) Dashboard randomly does this. Refresh doesn't fix it, but Logout and back in brings it back.

Edited October 17Oct 17 by Phil G

f

a

21 hours ago, Phil G said:

@dbwarner5 , to be clear, you had to restore IoX from a backup? Did you do that in A/C or eisy-ui or does it even matter? Thanks for the tip.

did the restore from Eisy UI.

Trying to further the migration from pgx3.

iAqualink is showing as running under the Plugin screen, but under NODES, it shows error loading.

I ended up under System / Services, restarting UDX. That allowed iAqualink to then show as Connected as a node server, but none of the nodes appeared. The next step was to select the node server under Nodes and then hit Discover and my nodes came in.

Next, ALL my programs that used these nodes are showing as NOT loaded. Yet, all the lines are ok. I have to go into each one, change something, SAVE it, then reopen it, change it back and resave it and then it works.

One weird things is the programs all load up as Disabled, and also have to be Enabled again.

PIA for 20+ programs.

Why this one was troublesome, idk.

Edited October 18Oct 18 by dbwarner5

@bmercier there still seems to be some interesting things happening to my EisyUI running the latest updates..

Randomly it rebooted this morning while I was attempting to check PG3.

2026-10-18 08:12:49 [error] shutdown: Error stopping plugin 1: timeout of 3000ms exceeded

2026-10-18 08:12:52 [error] shutdown: Error stopping plugin 2: timeout of 3000ms exceeded

2026-10-18 08:12:55 [error] shutdown: Error stopping plugin 3: timeout of 3000ms exceeded

2026-10-18 08:13:00 [error] ioxStartup: IoX is not responding: connect ECONNREFUSED /tmp/ns2isy182652

But it is still Beta I suppose.

@bmercier , I updated to the current versions last night and that update worked with no issues. I then migrated 4 of my 6 plugins.

They are: Notifications, ELK, AmbientWeather, and HueEmulator.

They all seemed to be working last night except that the logs were not updating past some of the initial lines and most of those were warnings. I cycled the power on eisy this morning and the logs updated on all 4 migrated plugins. But only AmbientWeather is showing current updates in the log. The logs from the other 3 produce about 30 lines and then stop. Most of the lines are warnings. I'm attaching those for your reference.

Again, they seem to be working, so I haven't logged a ticket, but wanted to make you aware of the issue. I'm available to run some tests if that would help.

The update process as well as the migration procedure is nicely done.

Mark

ELK-log-2026-10-20T16-32-22.650Z.zip HueEmulator-log-2026-10-20T16-30-28.136Z.zip Notification-log-2026-10-20T16-32-54.659Z.zip

Edited Tuesday at 05:34 PM4 days by mbking

On 10/20/2026 at 1:43 PM, mbking said:

@bmercier , I updated to the current versions last night and that update worked with no issues. I then migrated 4 of my 6 plugins.

They are: Notifications, ELK, AmbientWeather, and HueEmulator.

They all seemed to be working last night except that the logs were not updating past some of the initial lines and most of those were warnings. I cycled the power on eisy this morning and the logs updated on all 4 migrated plugins. But only AmbientWeather is showing current updates in the log. The logs from the other 3 produce about 30 lines and then stop. Most of the lines are warnings. I'm attaching those for your reference.

Again, they seem to be working, so I haven't logged a ticket, but wanted to make you aware of the issue. I'm available to run some tests if that would help.

The update process as well as the migration procedure is nicely done.

Mark

ELK-log-2026-10-20T16-32-22.650Z.zip HueEmulator-log-2026-10-20T16-30-28.136Z.zip Notification-log-2026-10-20T16-32-54.659Z.zip

What is the log level on these plugins?

17 hours ago, bmercier said:

What is the log level on these plugins?

@bmercier , I set them to Debug. I do have an update though. Before I captured these logs, I had shutdown eisy, pulled power. and then restarted eisy in hopes this might correct the issues I was having with some of the migrated plugins. I did this instead of restarting each plugin. Shortly before your reply, I decided to try restarting each plugin and that began giving me mostly clean logs. I thought restarting eisy would be equivalent to restarting each plugin individually, but apparently, there are differences and this got things working as they should. I do have a problem with the last plugin I tried to move, VenstarCT. It doesn't work after migration, but I'm going to try some of the recommendations I see in the forum before elevating it to support. Thanks for getting back to me.

Mark

After reading this thread, I updated to the latest EISY version, 1.4.6

I decided to try the plugin migration. I migrated one plug in at a time. (I only have 8)

Notification migrated and seems to work

Wemo migrated and appeared to be operational but I could no longer connect or control Wemo devices.

NOAA would not migrate and produced this error:

Bluetooth migrated and appeared to be working, but I lost connection to my Home Pod and old Cync devices that use Bluetooth.

Kasa migrated and appeared to be working, but lost connection to Kasa & Tapo devices.

iox-matter can't migrate, not in production store.

Tried EISY reboot, tried EISY power off and restart. No change

Migrated inoperative plugins back to PG3 and devices are functional again.

@bmercier My Roku plugin is failing on the integrated plugins but works fine on PG3.

The plugin discovers Roku devices on the network and creates the nodedef and NLS file based on what it finds. It then installs those files (using the installprofile() nodeserver api).

When installed into the integrated plugins, it installs fine, it discovers both devices fine, it creates the profile files fine and it appears to install them fine. However when viewing the nodes, one of the nodes will report "internal server error" instead of displaying the node information. The eisy-ui log shows this:

2026-10-23 09:47:05 [debug] web: HTTP Request from ::ffff:192.168.92.100 - GET /api/groups/nodeRoles/n023_29806
2026-10-23 09:47:05 [error] web: Error processing /groups/nodeRoles/n023_29806: NodeDef roku_44 not found in family 10 instance 23
2026-10-23 09:47:05 [debug] web: HTTP Request from ::ffff:192.168.92.100 - GET /api/profile/node/n023_29806/cmds/accepts
2026-10-23 09:47:05 [http] web: GET /api/groups/nodeRoles/n023_29806 : 200 : 4ms 
2026-10-23 09:47:05 [error] web: Error processing /profile/node/n023_29806/cmds/accepts: NodeDef roku_44 not found in family 10 instance 23
2026-10-23 09:47:05 [http] web: GET /api/profile/node/n023_29806/cmds/accepts : 200 : 2ms 

When I go and look at /var/isy/FILES/CONF/DEF/f10/i23/nodedef/nodedes.xml it shows both nodes; roku_45 and roku_44 in the file (same for the NSL file)

The flow in the plugin is:

discover devices
for each device found
  get device info
  write profile
  install profile
  addNode()
 

So it is doing the installProfile() twice. I think the node that's failing with the internal server error is the first node discovered.

I'm not sure what's needed to debug this farther.