drprm1

When using the test plug-in none of the nodes seem to update in the AC.

Here is the log. I controlled the lock several times manually and from AC YoLinkTest_1-10-2025_80937_AM.zip

Lock shows up in AC but controls don’t change the lock’s state

Here you go YoLinkTest_1-9-2025_124948_PM.zip

I will at halftime 😜

Okay great! My lock is now showing up in the test node.Didn’t see what it looked like like in the AC I’ll look forward to the production update and thanks!

Installed in different slot, configured and started. Not showing connected

installed 1.3.13 and still not showing connected. Restarted several times and not connected

Still shows 1.3.12 in store? sorry, refreshed and got it.

how long before 1.3.13 shows up in nodeserver store??

Also tried deleting test node and reinstalling in new slot. After configuration it never shows connected. When I try and start it show “already running” but it’s not connected. log is empty

Updated to 1.3.12 with no joy. YoLinkTest_1-9-2025_124948_PM.zip

Stopped yolink node, installed the test node, configured it and ran it. Only three devices showed up here out of 37. Unfortunately no lock. YoLinkTest_1-9-2025_122103_PM.zip

Pardon my ignorance here but are you saying to install the test node in its own slot to see if my lock shows up?( don’t want to mess up what I already have) Thanks

Still not showing up in AC Assume you want log. Will send it in morning

Thought is was probably the poll settings. Thanks

How often are temp sensors readings updated to eisy?

Not working for me so I’ll have to wait Thanks for checking into it.

Yes I have a hub and yes I use the Yolink plugin. I have about 30 other Yolink nodes that show up in the AC…..all except my new lock. Was hoping Panda had a solution here.

Got a new smart lock from Yolink. The fingerprint deadbolt YS7616-UC. I realize it’s new and maybe not supported yet but it is classified as a smart lock which I believe is supported? Anyway I’ve done everything to try to get it to show up in AC with no success. Is it supported yet? thanks!

Yolink now has a pool temp probe. Been using a regular probe for pool for the last few years. Works much much better than wireless tags did. Yolink is solid and not expensive

I see you experimented with deleting switch then adding it back…Did you happen to hard reset it a few times to get rid of any links before adding it back. Go to programs and using find/replace make sure the switch isn’t in any programs.

Well I’m trying to get only on commands so just make a program and specify it I run then if I need to reset all

Again I haven’t seen the phantom on behavior since I removed the motion sensors from scenes.(it drove me nuts before realizing that some command was sent even though the area hadn’t been tripped) I did specify in programs that motion sensors only use the ON command. This has to be changed in AC or UD MOBILE. Realized early on that after restarting nodeserver it changes back to send on and off commands. Panda suggested using a program to change the motion sensors to sending only ON commands which I did. i got this all sorted out when most of my devices started to go offline for long periods. Sent note about this to Yolink support. They wanted to know my hub’s EUI number. I guess it was an early model because they sent me a new hub. Have a lot of Yolink devices that all work great again.

I was having exact same issues after deploying about ten Yolink motion sensors. Was having phantom ons like you but it was only sensors I had that were controllers in scenes. Took all out of scenes and used program triggers.This took care of my phantom ons…….