Yolink Local API

[TJF1960]

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

[sjenkins]

I had everything working perfectly ; felt wrong, so I did the update on the first day   

[Panda88]

Found a problem with my installer - try again now 

[sjenkins]

10 hours ago, Panda88 said:

Found a problem with my installer - try again now 

up and going again, thanks!

[TJF1960]

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

[dwengrovitz]

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.

[Panda88]

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

[Panda88]

There was a bug in speakerhub - did not update the ST - 1.5.16 should fix it 

 

[dwengrovitz]

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!

[sjenkins]

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 6 hours ago by sjenkins

[Panda88]

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