stevehoyt

I had the issue too. Am running on an iMac. I cleared my cache and reloaded the installer. The problem was still there. After about 2 days it went away and is bac k to normal.

I have been running Kasa for many months. FYI here are my parameters

FYI I have 26 YOlink devices all running from a single hub in the center of my 2 story house. At least 5 are about 250 feet away from the hub. No issues.

I have used the yolink for almost 2 years now. I second what @dwengravitz said. Great Product

@photogeek54 As I assume you know by now, Benoit found the issue that related to the version number and has fixed it temporarily. When you make the change he requested, could you also make a change for me. I understand the part about having to add the custom parameter for the Api key. Could you have the custom parameter come up with the key word api_key filled in. That way I only have to add the key itself. It took me a couple tries to figure out that it had to be api_key. Not knowing that it needed the underscore, for us non programming folks, might help make it easier. Thanks

@bpwwer @photogeek54 bpwwer thanks for the analysis. I logged in and out of PG3X, rebooted the polisy. Also tried manually logging into the portal to check my license....license was/is good. I can get into the portal manually and rebooting/logging out did not help. I will open a ticket Thanks Steve

@photogeek54@Javi Yes it was the non production version. I get the message "Successfully checked for purchased node servers" ,but then the popup to install it, never comes up. I have tried other node servers and don't have the issue. I looked in the PG3 log and it appears I am getting a "failed to get license error". I have attached the log below. Please note the error around 6:32 am. this morning Maybe my license has gone bad? Is there some way for me to bypass this step and do a manual install? pg3_3-3-2024_63623_AM.zip

@photogeek54 Hi I have been running this for some time v 1.1.04. I recently had a battery die and had to have it replaced. Multiple batteries showed up so I thought a good way to clean things up would be to delete the plug in and reinstall it from the non production store. I can't get it to install. I click the install button and nothing happens. Any ideas on what to do? Thanks

Sorry if I offended you Paul. I have no problem with yolink support or ISY they are both great. My intention was that if more people reported as I had that they could resolve the issue quicker as the issue seems to have many facets to it. I have heard from them and know how to fix it now.

Check out my post further down titled " "connect to broker timeout". Apparently they are throttling/ rejecting our connection requests. I have had problems all this month with the yolink API. I stopped getting updates through the Yolink nodeserver. Looking at the Yolink nodeserver logs I was getting the error "Connection to broker timedout" @Panda88 and Michaels team did a great job trouble shooting the issue and found that the nodeserver is being rejected by Yolink. Just recently many of my motion sensors stopped reporting their status via the Home Assistant interface. Check your HA logs. I am seeing "yolink MQTT client disconnected" thousands of times So the bottom line is, something has drastically changed with their API access over the past month. I have sent 2 emails to them and am still having the problem. I am going to escalate it to yolink again today. I think we all need to send our issues to their support people. I have heard, as others have posted here, that a new yolink hub is on the way that is going to have local API access. Hopefully that will solve these issues.

I have had 30+ devices running on Yolink for almost a year now. I placed my hub in the center of the devices. They are spread out up to 250 feet in all directions around it. Also the ISY Yolink plugin/nodeserver is rock solid and support great. It sounds like you may not even have an ISY in the mixture. So as said above maybe the yolink site might be a better place to go. In any case here is a bit of info on their sampling parameters

Done check your messsages and let me know if you did not get the info @Panda88

@Panda88 UDI just logged in and took a look....The current best guess is that the payload being sent back is too large to get transferred before a timeout. They are investigating. I will let you know what I hear. This all started around the time I added 2 new sensors to my yolink. That may explain it.

I have been running the YoLink nodeserver for months without issues. A couple days ago, I noticed that the values are no longer being sent to the ISY. They are fine in the YoLink app I checked the nodeserver log and am seeing this error. See below. Many messages in the pg3x logs too but no idea what they mean. The developer mentioned he had seen it too and also on other node servers and that rebooting Polisy fixed it. I have rebooted my polisy and ISY multiple times and upgraded all modules to no avail. Also I have reinstalled all node servers. Has anyone else seen it? Does anyone know where I should look to figure out what is causing it. I am thinking perhaps I need to write a UDI ticket. Thanks

i have updated everything, rebooted everything multiple times and it is still happening. @Panda88 should I submit a ticket to UDI support?

I have been running this nodeserver for months without issues. A couple days ago I noticed that the values are no longer being sent to the ISY. They are fine in the YoLink app I checked the nodeserver log and am seeing this error. See below. I have rebooted my polisy and ISY and upgraded all modules to no avail. Does anyone know where I should look to figure out what is causing it. Thanks @Panda88

Yes he was working with the devolper and me on the issue. It is my understanding that the state now is the best we can expect.

I have been having the same problem with another pluginfor a number of months ...Here is the response I got from the developer. When something happens at the same time every day, it is usually something external to the plug-in that's causing that disruption. I.E. router reboot, dhcp server restart, etc. The reality is that those types of events effect your entire network, but it may just be the UDI system that notices them and reports it as an issue. The plug-in's are working correctly. They log the network error and then re-establish the connection and continue working as if nothing had happened. The only reason you even know that this happened is because we make use of the MQTT broker's built in facility to notify PG3 when a client (plug-in) connects and disconnects. We do that so that PG3 can send out notifications and set the plug-in status appropriately.

FYI @bpwwer it has been awhile since I posted about this... The problem seems to have largely gone away. I maybe, but not always, get 1 or 2 errors a day. The odd thing is that I get one like clock work at midnight every night.

Same here all programs disabled with DST change. I had to manually enable all of them. Polisy PG3X v 3.2.8 IOX 5.7.0

@bpwwer Check with benouit I just had a couple errors with I believe the new software installed. I sent him all the log files

Just to make sure that I get this correct. @bmercier The time zone is currently set to SF CA. The time in the AC is correct and the PG3x is 2 hours behind. Are you suggesting that to get them in sync, I change the time zone in the AC? If I do, should I change it to another city in the same time zone or to a different time zone and then back again to the correct one. It is not a big deal I can also just wait until I boot the Polisy again and see if it fixes itself. Thanks

Since I am the one seeing the errors every few hours, I just updated per your instructions. All appeared to go fine, though I could not find the message confirming the new version. I will let you know if the errors stop. @bmercier I did notice something odd in looking through the PG3x logs for the message. All the PG3 log messages have an incorrect time. It is 2 hours behind the actual time. I checked my Admin console for IOX and it is correct. Any idea why this might be and how I could set the time to the correct value Thanks

@bpwwer Saw your post to benoit about a new version. The error is happening a lot today for some reason. I am seeing it about every 5 to 10 minutes today. Let me know when it is in the non production area and I will install. Steve

@bpwwer I had a whole bunch of errors yesterday. Have you had a chance to connect and did you see them Ignore the ones around 2AM and 4AM. My eero routers updated and restarted causing them