Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Yolink Local API

Featured Replies

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 ;)

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

Found a problem with my installer - try again now 

10 hours ago, Panda88 said:

Found a problem with my installer - try again now 

up and going again, thanks!

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

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.

Image 9-30-25 at 4.43 PM.png

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

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

 

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!

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 by sjenkins

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 

 

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 by sjenkins

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 

Ya it wants me to update again to 1.5.16 but showing 1.6.0 ; working fine now so ignoring.

 

Screenshot 2025-10-02 at 7.23.30 PM.png

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

 

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 by sjenkins

Nothing obvious in install.log :-(

  • 2 weeks later...

Just removed the TST from the name in the non-production store - getting ready to move to main store - Can someone check if it allows update/upgrade of the TST version - This is a super version of the yolink server supporting both cloud and local operation (but also more complicated to setup)

I hope to have 1.6.x working soon - better retry mechanism but I wanted to get all of this done before releasing 1.6.x (to keep variables to a minimum)

I also have the new shufoff valves on my list to do - I did purchase them and hope it should be simple

Also ordered the new ON/OFF Fob - want to see if it is truly ON OFF only or is it the same as the 2 key FOB limited in the App 

@Panda88, I am not able to update. It acts as if it is a new plugin, only option to install is to a different slot.

Capture11.JPG

Capture10.JPG

Thanks

I'll contact UDI and see if there is a solution 

 

Just to be clear - you have a license but it cannot upgrade?

Can you make a backup remove the TST and install the new in the same slot and restore - does that work?

Yes, I have a license and it would not allow me to upgrade.

I will backup/delete and install the new one in the same slot and restore. Will let you know.

Thanks!

Thanks - It seems there is a bug in PG3x handling name changes

If it works, I'll release to production store and get going on releasing next version with improved error (offline) handling

Edited by Panda88

Worked perfect!

Deleted, installed and once it was done indexing I rebooted the eIsy.

I didn't have much time to test programs but the ones I tested which control yolink devices worked perfect.

Thank you!

-Tim

Yolonk Local hub! I love this over the cloud based api. It did take me a while to figure some of this out and I do not have alot of their sensors and devices yet. I was able to create a web page (currently I just am hosting this on my personal cloud drive it is not being served up via web server yet)

I've been able to use ajax for most of the api calls and I do have a sql database to keep track of my devices that I use to allow me to position the devices I am overlaying on a photo I took of my house with a drone. The harder part I was working on this week was the MQTT bridge to websocket so I could use just straight javascript for real time updates to my overlays. It says in the doc that port 8003 and 8004 are good for the websocket mqtt connection but they are not open on at least my local hub. Anyway here are some photos of my web page. If anyone wants to do something like this I might be able to help you out. This was such a struggle for me because I could barely find any info on the api with javascript. youlink is really good about answering my emails.

webpage.jpg

webpage2.jpg

bridge.jpg

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.