oberkc

It makes me wonder about the purpose of the "delete" option and whether the new EISY-plugin is actually working.

Sorry to hear this. So that you know, I have again migrated (some of my) plugins to "plugin", but have not yet deleted them from PG3. After a few hours, everything is still working. I will keep you informed.

A few days ago, I migrated most of my plugins from "legacy" PG3 to the EISY Plugins. Most worked well with a couple requiring extra steps to get working. Since they were now working in the new EISY plugin, I chose to delete from PG3. Soon thereafter, all of the nodes associated with the various plugins were gone. Ultimately, I was able to restore a recent backup and the PG3 was repopulated with the configuration prior to migration, and all the programs and scenes containing the plugin nodes were restored. Has anyone else experienced this problem? Was this problem associated with my decision to delete the migrated plugins from PG3? Has anyone else deleted migrated plugins from PG3? Other thoughts?

I believe that is done by creating" an empty" widget and then using that empty widget to create the spaces you desire.

I will add that mine local plugin quit working when I migrated to the EISY "Plugin" from PG3. I migrated back to PG3 and it is remains non-functional, with all node and controller fields blank. I have restarted the PG3 node server and rebooted the EISY. Still no luck. Update: I rebooted the PG3 node server again and it seems to be back online.

Yes. I am confused, then. The registration page shows 10 - 11am (presumed and confirmed PST). The Email response shows 10 - 11 EST.

I have had similar experience with the single thread device with which I am experimenting. I also have similar experience with matter-over-wifi devices. I have never satisfied myself that I know the root cause. For now, I am not adding any more matter devices.

I assume all posted times, including at the registration page, are PST

I have not experienced this problem. My plugins always restart and work fine after power outages or other unexpected reboots. A while ago, I recall a few plugins that may not have worked after a power outage, but I percieved this was the result of a plugin restarting faster than the associated hub (hue plugin restarted faster than did the hue hub, for example). I have not noticed such problems recently, however.

Are your ue devices integrated via the hue hub? If so, I thought one could create a group in the hue app, which would show up as its own single node in the EISY. I am wondering aloud if this single node could be controlled as you wish.

Twice a year this topic arises. Give it an extra day and (if your experience matches mine) it will fix itself.

I understand. A few years ago, I believe there was confusion between how insteon defined scenes versus how UD defined them. But...when one is wondering where the scenes are shown and created/edited, it seemed worth mentioning.

Also, "scenes" are now "groups".

Yours looks a lot different than mine:

Well, I tried migrating one (Caseta) plugin. It showed up in the EISY-plugin and told me to hit the black button on the back of the caseta hub (I did). The nodes did not show up. All old caseta nodes are gone, and no new nodes showed up. I did a Quick Look at the log and it showed a bunch of lines with error messages. I went back to PG3x and had to recreate all the former scene and folder memberships. I am inclined to wait a bit longer in the hope that these types of problems will be resolved.