TJF1960 Posted Monday at 09:10 PM Posted Monday at 09:10 PM 50 minutes ago, sjenkins said: @Panda88 just did the update to ISY 6.0 ; most started up ok but Yolink local will not show connected , nor update any of the devices. I sparked up the regular remote Yolink I keep in another PG3 slot, it started up just fine, showed connected, and started populating devices. I looked at the plugin logs and got nothing. the main logs looked like they sparked just fine, no errors. I did a re-install (which the upgrade does as well). No joy. Any others having issues after upgrade? I have not done the 6.0 upgrade yet, and probably will not for a few days to a week, my system is finally back together and working the way I want it to, I want to enjoy it for a bit Quote
sjenkins Posted Monday at 09:19 PM Posted Monday at 09:19 PM I had everything working perfectly ; felt wrong, so I did the update on the first day 1 Quote
Panda88 Posted Tuesday at 12:35 AM Posted Tuesday at 12:35 AM Found a problem with my installer - try again now 2 Quote
sjenkins Posted Tuesday at 11:22 AM Posted Tuesday at 11:22 AM 10 hours ago, Panda88 said: Found a problem with my installer - try again now up and going again, thanks! 1 Quote
TJF1960 Posted Tuesday at 07:25 PM Posted Tuesday at 07:25 PM On 9/29/2025 at 11:31 AM, Panda88 said: Connection state can be suspended in case you generate too much traffic - It is still connected so state on-line - just suspended - The reason it takes so long to start up with a lot of devices is I am trying not to generate too much traffic (PG3x is multi-threaded so it basically starts all at the same time causing connection to be suspended) - It can still happen as I cannot 100% figure out how YoLink counts the time - but it does recover eventually - once up and running there is usually no issues It is also partly from the need to move ST to be the actionable parameter - in some cases ST was on-line before - so I had to create a field to use in programs that previously relied on this ST field I agree it is a little confusing, but I had to make this choice to make it somewhat backwards compatible and support UDImoble I am also enjoying being able to view the status of switches and temp sensors in UDM without having to open each node to see whether it is on or off or what the temp is...I may never look at the Yolink app again! I know it was a pain, but Thank You for including this in the last build. It is awesome! Everything is performing perfectly, now two days into the new beta! -Tim Quote
dwengrovitz Posted Tuesday at 09:04 PM Posted Tuesday at 09:04 PM 1 hour ago, TJF1960 said: I am also enjoying being able to view the status of switches and temp sensors in UDM without having to open each node to see whether it is on or off or what the temp is...I may never look at the Yolink app again! I also like the ability to see this without having to dive deeper into the UI. One odd thing I noticed is that the current state of my Speaker Hubs always show as "Not Connected", even if the individual devices seem to be reporting changes. I'm running IoX v6.0.0, with PG3x v3.3.22, and Yolink Plugin V1.5.15. Quote
Panda88 Posted Tuesday at 11:28 PM Posted Tuesday at 11:28 PM I'll take a look to see if there is a bug - the hub is a special case that needs special handling - especially the speaker hubs Quote
Panda88 Posted Wednesday at 04:09 PM Posted Wednesday at 04:09 PM There was a bug in speakerhub - did not update the ST - 1.5.16 should fix it 1 Quote
dwengrovitz Posted Thursday at 01:30 AM Posted Thursday at 01:30 AM 9 hours ago, Panda88 said: There was a bug in speakerhub - did not update the ST - 1.5.16 should fix it Speakerhubs now show as Connected - thanks! Quote
sjenkins Posted Thursday at 01:32 AM Posted Thursday at 01:32 AM (edited) Just did the install of 1.6.0 & its crashing log files attached. In addition once you start the node, both local and regular, it seems you cannot hit the stop button and get it to stop. Tells you its not running. Is this a result of the initializing status. Means I had to delete the node to get it to stop. update: not just the local hub plugin ; the regular plugin is crashing and restarting as well. TSTYolinkLocal_10-1-2025_92945_PM.zip Edited Thursday at 01:42 AM by sjenkins Quote
Panda88 Posted Thursday at 05:00 AM Posted Thursday at 05:00 AM It is MQTT related - may be 6.0 related - I'll try to figure out if something changed in 6.0 I have seen this before and sometimes a reboot/power cycle fixes it Quote
sjenkins Posted Thursday at 11:33 AM Posted Thursday at 11:33 AM (edited) 7 hours ago, Panda88 said: It is MQTT related - may be 6.0 related - I'll try to figure out if something changed in 6.0 I have seen this before and sometimes a reboot/power cycle fixes it With reboot, both plugins said v1.5.16 was ready (1.6.0 had installed for both). Updated and started, all was well. Version on both plugins now say 1.6.0 again ; store is 1.5.16 Thanks Edited Thursday at 12:02 PM by sjenkins Quote
Panda88 Posted Thursday at 03:52 PM Posted Thursday at 03:52 PM There is still a bug in the release - it is supposed to be 1.5.16 1.6.0 is very close to release - includes improved retry but it is not officially released I guess I need to understand my release tool better - I am not releasing from main (allowing me to test main before releasing) I installed 1.5.16 back to the release but 1.6.x is coming soon -= will likely switch to 6.0 before doing that release but need to finish something else first Quote
sjenkins Posted Thursday at 11:23 PM Posted Thursday at 11:23 PM Ya it wants me to update again to 1.5.16 but showing 1.6.0 ; working fine now so ignoring. Quote
Panda88 Posted Friday at 12:05 AM Posted Friday at 12:05 AM Can you send me the install log - I cannot see how it can still get the new version On the other had, I am happy the 1.6.0 works - I am seeing the same and plan to release soon - but wanted to upgrade to 6.0 to make sure it works there as well - I have not had the time for the upgrade yet Quote
sjenkins Posted Friday at 12:42 AM Posted Friday at 12:42 AM (edited) Sorry I wasn't clear. I don't think I am running 1.6.0 I think the timing was such: 1. I had 1.5.15 and the update came down for 1.6.0 2. crashed, did not work 3. later it came asking to update 1.5.16, did the install and all is good, initally said it was 1.5.16 but then the pg3 display says its 1.6.0 (I don't think it is) 4. it is now claiming to want to install 1.5.16 again I did nose around in the files but I don't know where you specify version. install.log Edited Friday at 12:47 AM by sjenkins Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.