roho

Thanks for reviewing the debug log -- that was very helpful. I was able to pull a comprehensive list of all my YoLink devices out of the debug log and noticed that the discovery process worked through the list in alphabetical order, stopping after the 31st device was discovered. The rest of the devices were in the list, but discovery stopped at 31. Consistently. On a whim I deleted the fourth device in the list (from both YoLink & the list of nodes in the plugin) to see if the plugin would pick up the next node or maybe something different. It was something different. The next time I ran discovery it found all of my nodes. No idea why. I've since added the deleted node back to the system and everything seems to be working properly. I'm glad to have the YoLink plugin working again, but am disappointed that I was not able to find out what the problem was. Problems that go away by themselves tend to come back by themselves. In any event, thank for your prompt attention to my question -- it is greatly appreciated. Ron

Thx for the suggestion. The Flowsmart is actually pretty hard to gain physical access to -- it is in a crawlspace and takes a while to reach. I'm not sure how long it takes to drop back into a deep sleep, but it may do so between the time that I press the button and when I get back to the computer to restart the plugin. As an alternative, I checked the Flowsmart status via the YoLink smartphone app and then restarted the plugin. Presumably the Flowsmart is awake and online when it is talking to the app and hopefully stays awake long enough for the discovery process to run. In doing this the Flowsmart was still not discovered nor were the 40+ other "missing" YoLink devices in the environment. While I'd obviously like to get the Flowsmart integrated into my overall home automation system, the real pain point right now are the other 40+ devices that have gone missing. Are there any hints in the debug log that might suggest why they aren't discovered? If something points to the FlowSmart somehow breaking the overall discovery process then I'll delete it from the YoLink environment and re-run discovery, but that is moderately difficult to do. While I'm quite willing to do this, it would be nice to have some specific log messages suggesting that this would be helpful. Again, thanks for your help with this. The YoLink plugin has been incredibly useful and I've come to rely on it quite heavily, so I appreciate your assistance in getting it back on line.

I recently added a FlowSmart All-in-One (YS5018-UC) and am having problems with node discovery on the YoLink plugin. I don't know if the two are related, but I have 70+ YoLink devices and the FlowSmart refused to be discovered. I've since deleted and reinstalled the plugin (many times) and it only discovers 31 devices. Never any more. Here's some of the details: PG3x Version: 3.4.19 IoX Version: 6.0.5 YoLink Version: 1.8.60 I did a fresh install and captured a debug log of the discovery (attached to this post), but I'm not familiar enough w/ the app to spot where things went wrong. Any suggestions on where to look for problems or what to do next would be appreciated. Thanks Ron 2026-08-04.debug.log

I've been watching/waiting for Yolink to come out with their local API and it looks like it might actually be here. Here's a link to their "Steps to working with Local API". This appears to have been posted just a couple days ago (Feb 12, 2025), so I doubt that anyone has done a production implementation just yet. Still, it looks like we're getting closer.