TJF1960

That is a great question, I have not been able to schedule a time with my family for shutting down internet in my house, but as I think about it, it would only interrupt for 20 minutes or so I would think. Maybe I can test this weekend before everyone is up and around. @sjenkinsHave you been able to test and confirm the local hub delivers locally when the internet is interrupted? Or anyone else for that matter? Thanks! -Tim

Awesome, fingers crossed!

My two cents from reading your post. If all you did was swap PLMs, and you did not do a remove or restore plm then I think you should immediately do an IoX backup and PGx backup. Running a topology report (admin console>Tools>Generate Topology) will be beneficial as well. Note, hot swapping plm is not great but at this point, leave the new plm attached and get your backups first. Then power down, swap plm back to the old one and reboot. Then do some troubleshooting. -Tim

Not the answer I was hoping for, lol. Thanks Larry!

Hi @Jimbo.Automates, I have been using your ecobee plugin for little over a month now. Thank you for developing it! Question I have is that it appears longPoll is when it queries the ecobee server for updates. Is 180 seconds set in stone or can we, say, drop it to 60 seconds without issue? Does shortPoll have any function? Also I noticed that initiating a query from the plugin does not update the node values, is it supposed to? Last question, I have not been able to figure out if there is any type heartbeat that I can use to monitor connection of the tstat thru the plug in that changes state every minute or couple of minutes? Thanks again! -Tim

@Panda88, It is working well for me as well. On this test setup I am running a temp sensor, motion and plug switch. Thank you for all the help and support in getting it running! -Tim

@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