TJF1960

@Panda88, given the hassle involved, and possibly breaking existing installations, If it were up to me, I wouldn't worry about it. Your plugin is and has been working extremely well for everything need. All devices and statuses work great in programs as is. Thinking about it too, its just as easy, if not easier to just open the yolink app to control the plugs when needed. I am sorry I opened this can of worms.

I had some issues with my plugins playing nice with UDM in the past, something similar to this. I found that I needed to use uom=78 for switch status in order for the icons to properly display. This uom must be also be carried over in the profile files as well for the switch. I took a quick look and it looks like you are using uom=25. I cant guarantee this is the issue but its worth a try maybe? @bmercierperhaps you can chime in with your thoughts? Thanks! -Tim

Yes, AC changes state perfectly. The device dashboard in UDM will turn on and off the node switch and properly indicate status changes controlled either with UDM or AC or the Yolink app. Just an issue with the icon and indicator for the plug node. When you open UDM and go to Yolink and scroll down to the icon, whatever state the node was in when you opened it is what it shows you. But it will not reflect state changes after that.

Good morning @Panda88, I am running the latest Yolink production in one slot and beta Local Hub Yolink in another. I am seeing in UDM that the icon status for the Yolink plugs does not update when the device changes states. Attached are two screen shots. First pic is of the icon (Yo Plug Tester) properly displaying the status when I opened UDM. Pressing the edge of the icon to turn the device off, does turn the device off but the icon status continues to display the device as being on. The second screenshot is showing the device as off. This occurs in both versions of beta and production versions. Thanks! -Tim

@Panda88, thanks but, After the new home is created and I am in the new home of the app, I go to Settings>Account>>Advanced Settings>User Access Credentials, correct. If that is correct, I still get the same UIAD and Secret.

Hi @Panda88, I have been having trouble with adding the local hub to my existing installation in that devices start becoming unresponsive after about 20 minutes. I have not been able to figure out why. So I created a new home for the local hub and one device that is not linked to the main home. The trouble is that the current home and new home UAID and Secret Key are the same so all of the current home devices appear on the new home as well, but only in the TSTYolinkLocal plugin, not in the Yolink App. Also, once I place a device in the Local Network of the Local Hub, it becomes unresponsive. Resetting does not help. Restarting the plug in does not help either. I am not sure what to do at this point. I presume since I am the only one seemingly have issues, it must be something I am not doing or understanding.

@Panda88Thank you. Let me ask this, do you envision merging these two plugins at some point, in the near future or do you think you will keep them separate? Also, last question, was the beta built on the latest updated production version of Yolink, or is it a rev or two behind? I really appreciate the help, Thank you. -Tim

I have production Yolink running in slot 15. I added beta Yolink to slot 25. After configuring the plugin in pg3 with the identical client/secret keys as the production version, all devices populated in the beta plugin and were an exact match to the production plugin. Both plugins seemed to run fine. After a few minutes though, the production Yolink nodes started not responding to commands. But in Yolink's app they responded fine. I am assuming that there was some conflict with the new local hub and main hub causing the issue. After I deleted beta Yolink and deleted the local hub from my app, the devices slowly started to respond to commands. Question, is this how the rest of you are testing the beta, using the same client and secret keys as the production Yolink or are you testing with a new test setup? Also, second question, I noticed that aside from the node slot, the device identifier in pg3 were identical between production and beta. For instance n_015_15432dfd413df1 in production while for beta the same node was identified as n_025_015_15432dfd413df1. Do you think I can delete production from slot 15 and install beta in the same slot and I wouldn't have to rework all my programs? -Tim

I just had a few minutes tonight and thought I would finally try getting this connected. After reading @sjenkins last post, I checked and sure enough there was an updated for the local hub. Updated that, filled out the config page for the plug-in, restarted and all is working! Weird thing is I didn't have to curl, between the info from the local hub and the existing Yolink plugin. Then I got to thinking, in order for all devices to report to the local hub and not the original hub, that may be where I need to use the curl command. Don't know yet. Ran out of time tonight. Thank you @Panda88 and @sjenkins for your persistence and forging the way! -Tim

Where are the instructions? The More Info link on the store page is inop. and there are no instructions in the plugin config page.

TSTYolinkLocal is in the beta store now. Sadly it will not install in the production version slot.

YoLinkTest is still the only title in non-production and it wont let me install over production Yolink slot. I do recall I had my fair share of issues getting some of my plugins to stick in both non and production stores too. I never did figure out the rhyme or reason. _Tim

I am only seeing Yolink test in non-production. Will the new local plugin install in the same slot as yolink production is in or will this require pointing all programs to the new node?

I received an email this morning, the Local hub is back in stock. $199. Mine will be here by the weekend.

I have experienced the same problem as @sjenkins with saving programs when using anything but port 8443. I have also experienced a couple of random, reboots. As well as random plugins failing and restarting and notices about the portal being offline. I have also had Alexa complain that the "hub" is offline when asking her to turn on ISY devices and programs. These things are not frequent and unfortunately by the time I get to log in to download logs they have already refreshed. I was hoping others were having the same issue but it looks like my experience may be a one-off.

I am experiencing similar but a bit different results. I cannot log into into AC with finder on 8080 LAN, it wont even try I can log into AC with finder on 80 LAN I get the XML Parse errors. I can log into 8443 LAN with no parse errors. I have rebooted numerous times. Other than that, the install went beautifully. Thanks UDI team! -Tim

That is just it, Where do I find the logs? I do not see anywhere in UD Mobile anything that indicates access to logs.

I have a new Samsung android phone with the latest software/fw. Installed UD mobile. Works fine. Set up geofence and enabled both buttons (UD Mobile Location Services and Experimental). Set permissions etc. but it will not send notification to ISY (eISY). It worked fine on my old phones... I need help with capturing the logs that you may need to help. I cannot figure out how to get or copy them. Any help would be appreciated. -Tim

+1 once the hubs are available.

v1.0.6 Fixed renaming nodes on the fly on 03/09/2025

Fixed renaming nodes on the fly in v1.0.6

@EricBarish, Are you running non production or production? What version? Please copy and paste your json exactly as it appears in PG3x. Are those the only two that do not change or are there others that do change but just these two do not? Edit: Also, please PM me your log from WebControl832 from PG3x. -Tim

@Panda88, logs PM'ed to you. Thanks in advance! -Tim

v1.0.5 Fixed UoM ending subset 02/18/2025

My apologies. 832 was my third plugin, 8 was the second. Since 832 operates completely different than 8 I didn't want to publish over 8 and force anyone that was happy with 8 to redo their whole setup. I am glad you got both instances up and running. -Tim