TJF1960

I am not sure if this will help but I created an All Off scene with all devices and all kpl buttons buttons for just such a case.

Thank you.

Yes I am on the latest. Thanks, I think I will open a ticket. -Tim

@DennisC, thank you for the heads up. I am not sure that is what is going on though. I can open any of my 20ish plugins in system>plugins except for the one. Once I try to open that one is when I get the error above. -Tim

Good morning! On UDM, current version on android (I couldn't find the version number), IoX 6.0.4 and PGx 3.4.11 If I go to Settings>Plugins>YolinkLocal, the 4 dots just keep spinning, after about a minute I get this popup: After this I cannot access any plugins for maybe 5 minutes. Once I go back in, if I click on any plugins before trying to access YolinkLocal, I can gain access to any but not YolinkLocal. I looked for a way to download any logs in UDM but didn't find any. What should be my next step? -Tim

Mine too! I noticed yesterday morning it was running fine. I rebooted eISY yesterday afternoon and vue did started working right away after it initialize! I haven't tried again though, didn't want to push my luck..

Things have been working pretty darn well with the Yolink local hub. Since installing it I have never tested the local function. Well, we suffered an internet outage Saturday and yesterday. None of my devices reported while service was down. What I did find weird is that thru the admin console I turned a few of the plugs on and or off, just testing to see if it was working. None responded. But after the internet was restored, some of those plug then responded by turning on or off. Weird right? So, I would like to check myself to make sure I have the hub and app configured properly. In the app, I selected the local hub. At the bottom of the local hub page, I select Local network. Then select Devices. Then I select + and add each device I want to report during an internet outage or power outage, correct? Or another way to put it Local Hub>Local Network>Devices>+ then add devices. After adding all the devices, pressing the set button on each device to seal the deal. In the plugin (YolinkLocal) I add the keys along with Hybrid and the lan ip address for the hub. Like I say, its been working the way I expected just fine with internet. Does this all sound correct?

Well, so much for my luck. I postponed rebooting eisy so I wouldn't lose vue. We lost internet for most of the day yesterday. When it was restored, vue was throwing the same error as the op. I am down now also. So its not only a reboot but also a loss of internet that will kill it. I am not complaining, just putting it out there. -Tim

I am sorry you both are going thru this. But thank you for posting. I was planning on doing some work to eIsy later today which would require a reboot but I will now wait for the update. Thanks again! -Tim

@Techman Are you saying that I can have another tempest in my area that I can tap into to feed the plugin for the time being? I did find a station close by but I am not sure how to retrieve their data with my plugin. I found their station id in the url but I don't have their token. The plug in says "Failed to get station units.

My Tempest battery when bad. It is going to be a while before I can get a replacement. I thought I understood that if I chose remote that I would receive rainfall amounts? But I am not receiving any. Did I misunderstand? Is there a plugin that I can use for short term that will provide rainfall for my area. I though and purchased NOAA plugin, but it doesn't provide percip.

I happened to reboot yesterday after deleting and installing a few insteon devices. I did not hit update iox. When eIsy came back up and I opened the A.C. I was notified that I was running a version of launcher that was out of date. After doing the java thing and downloading launcher is when I discovered I was in 6.0.3

Hey guys! I don't mean to butt in however I thought I would mention another possible contender for energy monitoring. Emporia Vue. They make small smart plugs like Yolink but I have found them to be much more responsive, and they report quickly to the Vue plug-in. They are pretty inexpensive like Yolink and are also made just as well, in my opinion. The Vue are all I use anymore for device energy monitoring. I do like that all Yolinks report to the hub and you only use one IP address whereas Vue requires each to have an IP address. Here is a link to a 4-pack for $35, but you can buy them Singley to. Emporia Energy Monitoring Smart Plug, WiFi Smart Outlet Plug Works with Alexa and Google Home - 15a WiFi Outlet with Timer, Mobile App, Home Energy Monitor, Scheduling - 2.4ghz WiFi Only (4 Pack) - Amazon.com -Tim

Hi @Panda88, I know you are busy working the rest of the kinks out, and I really appreciate your dedication! The following is definitely not an emergency situation but it is something I would like to fix eventually. Since I switched from the stock hub to the local hub I have noticed that sometimes there is a delay from the time motion is detected to when the plugin reports it. It varies. Anywhere from a few seconds to maybe 20 seconds at worst. This began with your first non-production plugin and has continued thru to yesterdays updated production plugin Same set up with same number of temp sensors, switches and water leak sensors. Never experienced it at all with the old hub. Started with the new hub and new plugin. I was able to finally figure out that the Yolink app received the motion detected signal almost immediately but sometimes that delay occurs for the plugin to detect. It is so random that I don't even know how to go about troubleshooting any further. I think my next step is to pull one of the motion detectors and put it at my bench for further testing. Finally, to my question, what would you recommend I do or test for when I do this. Thanks again, _Tim

Ditto, fixed mine as well. Thanks @Panda88!

@Javi, could this error also cause the inability to open Settings>Plugins>Yolinklocal?

I reinstalled about an hour ago, did a hard reboot to eisy. No change. It must be UDM them. Thanks, -Tim

Lucky man you are then! Thank you for taking the time to respond, I appreciate it. Its really not a big deal, unless for some reason I am away and need to restart the plugin. But there are worst things in life. Thanks @Panda88 for all of your laboring and hard work. I appreciate it very much. -Tim

Interesting! Thank you for checking @oberkc. This is the only plugin out of like 20 that does this. It started with the first or second non-production YolinkLocal. I guess this indicates something on my end, but what? Weird. Question, when you resync UDM do you get the message to let the dev know about ST name for the nodeserver? That also started with one of the non-production versions as well. One last detail, if I go to settings plugins and select this plugin, wait 20 seconds or so then close the app, reopen the app and go to settings>plugins I get an error message of: "Could not get pg3 auth PG3 (Plugin Software) is not online. Then at the end it says :Developer Tip: This issue may be caused by PG3's Portal Connection mismatch. 500"

@Panda88 ,I noticed last night that YolinkLocal was not triggering programs. I went to UDM, Settings>Plugins and selected YolinkLocal and the little wheel kept spinning, never would stop. I had forgotten about this, it has been this way since I think non-production days. If I back out and select another plugin it wont open either. So I closed it down. Opened it back up and selected a few different plugins and they all would open properly. I once again selected YolinkLocal and it would not open. I am not sure if this is just a me thing or it just hasn't been noticed and reported before. Also, as of the last update, yesterday, when I resync UDM it still does complain that slot 15 (YolinkLocal for me) is not setting or hasnt set ST name. or something like that. So I don't know if the two are linked or not. Thanks! -Tim

How do you delete the favorites main page or home page? Or, how do you add or delete nodes from the home or favorites page? Thanks! Updated eISY yesterday to the latest version.

@Panda88 Lol, thank goodness, no. Back in the day, early on I was using this program as a heartbeat for the plugin so I selected the lowest temp possible. But now I see, at some point, you added Last Poll Time for the plugin which I have now switched over to use as the heartbeat (thank You). But when that program fired and alerted me the heartbeat was down is when I discovered that the temp nodes in programs were wacky. Thanks! -Tim

Hi @Panda88 , I think there is an issue with temp sensors suddenly on my system. This worked in previous versions. This is an old program I set up. I was checking to see why the program was not running. The program used to have temp of around -40F but not the program displays, well take a look at the pics. The second picture shows the actual values but at the top it doesnt. I looked in the logs and found some errors but they appear to be plugs that are disconnected right now. I tried restarting the plugin but it did not change. Thanks! Tim YolinkLocal_11-1-2025_15729_PM.zip

Thank you for looking into it for me.I I will keep an eye o other plugins. Thanks again, Tim

Heollo @bpwwer, Not sure where to turn as I seemed to be having problems with both Vue and YolinkLocal. I installed 6.0 a last weekend. Since then Vue works for about 3 days then doesn’t update values or control switches. A reboot fixes it for another few days. This morning, I had PGx open in Eisy_ui and in the bottom right side a red warning kept popping up, something about Slot 13 (Vue) was...I am sorry I don’t remember exactly what it was but it seemed to indicate Vue was using too many resources to quickly, is how I interpreted it.. Alternately another warning about slot 15 (YolinkLocal) was struggling as well. Unfortunately, I didn’t capture when vue became unresponsive, but I think I did capture today's events. I reboot and so far so good. I will also add that whatever is going on seems to have affected other plug ins today, devices turning on and off by program were taking way to long. I am on 6.0.0_04 With everything up to date as of yesterday. I have PM’ed you the logs from today. Thank you! -Tim