Hi,

I ues and enjoy the Yolink plugin on my Polisy every day. Yolink sensors; temperature, open closed, etc working well.

I am trying to use a Yolink on/off fob YS3605 US to replace my aged Insteon Remotelinc 2444A2. But I cant seem to get it to work.

Background:

I added a Yolink mini on/off fob YS3614-UC (mini fob, not "regular" on off fob) This is a two button mini fob. The YS3614-UC is exposed by the Yolink plugin with four parameters: Key One, Short press, Key One Long Press, Key Two Short Press, Key Two Long Press. Configured the YS3614 so key One short press is DON, Key One long press is DOF, Key 2 short press DOF and Key 2 Long press DON. Adding the YS3614 to a to a program and using the only available "control" conditions I can turn on and off an insteon switched light.  Control key 1 is on and light turns on, control key 2 is on and light turns off. I can see the last command in the Admin console tab for each of the two keys in the fob.
Great except that the YS3614-UC has only two buttons.

The YS3605 US has four buttons, A Green and Red and B Green and Red. And is is about the same price as the YS3614-UC
They are exposed as Key One, Short press, Key One Long Press, Key Two Short Press, Key Two Long Press. Key Three Short press, Key Three long press, Key Four Short Press, Key Four Long Press.  Configured in same pattern as YS3614. Key One Short Press DON, Key Two Short Press DOF, etc.  Add it to the existing program Control on etc

The YS3605 switch one works once, to turn on the insteon light with switch one. The YS3605 switch two never works to turn orr the insteon light.  Turning off the insteon switched light by "hand" and now the YS3605 switch one creates an admin console error of inability to communicate with the insteon switched light.  Also the admin console only shows last command for key 1.  The others, key 2 key 3, key4 always say unknown, no matter how many times I push those fob buttons.

I have to use the YS3614 to turn the insteon switched light on and off.  Then the YS3605 will again turn the light on only once.

Yikes! I am confused.

Suggestions?

I would copy/paste my actual programs/settings to the forum if I knew how.

you should have 4 sub nodes where you define the operations for each press type. i have the same fob and it works 

Are you trying to use a scene to control this ?  I still believe it should work, but I have not tried it

I have used programs mostly with this one

Send me a debug log (enable debug and press the different keys are few times) 

Edited July 28Jul 28 by Panda88

Hi,

FYI - This is information - not a request for help (yet)

Was away for a while.  And perhaps with the merging of local/cloud versions of hub this issue will go away but:

I now have a bunch of fobs with the same name and I seem to be missing one fob and the fobs have generic names that make them hard to differentiate.

More details:

I have two locations - each with a standard Yolink talking hub YS1604-UC and each with a "local" Yolink hub YS1606-UC.

One location has one regular 4 button fob YS3604-UC

The second location has one regular 4 button fob YS3604-UC, one 2 button small fob YS3614-UC and one 4 button on/off fob YS3605-UC

I have the the two Yolink plugins Current Version: 1.5.14 (local and regular) running on Polisy with Polyglot V3

So far so good

However when I ask both local and regular Yolink plugins to "add all nodes" I run in to trouble

I get two nodes labeled Yolink Fob

I get one node labeled Yolink Fob Small (I think I renamed it)

And another two nodes named Yolink Fob with the name of my second location ( I think I renamed it)

Huh!

Which fobs are connected via local hub(s)?

Which fobs are connected via cloud hub(s)?

Anyway - I use and enjoy the Yolink plugin every day.

I have a feeling when the cloud and local Yolink plugins are merged, this may resolve itself.

Thanks

 

i just released another local hun node in the beta store.  i handles both local and cloud with all the devices (all devices share code now) - i would not run 2 nodes in parallel.  what is your reason for doing this?   the local also communicates with cloud (when internet is available).  

 

Thanks for the quick reply.

Happy to run only one node.

 

Just to be sure, which node should I be deleting?

What is its exact name?

you need the local one.  It is currently called TSTyolinkLocal in the beta store.  i plan to move it to production store after a little feedback.  both nodes will share a large portion of the code base

Deleted one Yolink node

Now running only

TSTYolinkLocal(11)

Current Status: Connected
Current Version: 1.5.14 / Standard [Beta]
Time Started: Sep 26, 2025, 10:00:39 AM
 

Thanks

 

You can see the connection status on the local node - It local - Local is added to the status 

In general local connection has priority over cloud (if you select hybrid mode) - meaning local connection is used if device is connected to the local network - note even if on local network the hub reports status back to cloud. I think commands from app will go through the HUB but not 100% sure