Have switched plugins from PG3 to eisy ui plugins beta. My version is 1.8.60 and when I try to upgrade to latest version in the eisy ui store, I get message below and upgrade fails.

can you send me a log and I can take a look

Here is the plugin and eisy ui log

YoLink-log-2026-10-07T20-02-32.314Z.zip

There are no errors in the Yolink log - Maybe try to reboot the system or reinstall the nodes - there are other nodes with errors as well

OK.. Rebooted eisy and restarted the plugin. Still get the same error. Interestingly, all of the Yolink devices seem to be working fine. Should I delete the plugin and add back in plugins beta, or add back in PG3 , then migrate?

I saw there just was a new release of the UI - maybe try that before anything else

I would try to delete and reinstall - I believe they are really the same

Solved. Turns out that the plugin did not like updating via portal, but did update on local network.

I'm having a similar issue after my migration to eisy. I was only running 3 PG3x nodes, and two of them migrated no problem. I cannot get the yolink nodeserver to migrate or install new as a plug-in. I've attached my logs below.

eisy-logs-2026-11-05T01-08-48.zip

can you PM me the yolink log

I upgraded the plugin to 1.8.66 and it's just going haywire, notifications every few seconds alternating between YoLink failed and connected. I had migrated it to eisy Plugins well before upgrading and everything was fine till I upgraded. I returned the plugin to PG3 and it's still happening. I tried restarting reinstalling, no help.

YoLink_11-4-2026_92949_PM.zip

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.

Edited Thursday at 02:50 PM2 days by oberkc

I had the same thing happenign yesterday - It looks to me like two version of the node was running - I rebooted and it went away

Still, I did find a bug relating to speakerhub, that I am trying to fix

Thanks everyone for the advice. Rebooting PG3 didn't work, but rebooting eisy did. In the process, though, my nodes got scattered out of the YoLink folder I created.

@Panda88 Grateful for your work on this plugin