Thanks again for all you do, this little plugin is pretty integral to my system with dozens of YoLink devices.

So began using a mini remote two button YS3614-UC, getting it to trigger my Phantom blinds from outside, and ran into two issues:

1. I am getting phantom(haha) button-1 pushes, after days of blinds moving on their own I shut that down and put a program to just increment every time I got a control button push. After two days I had 14 button-1 pushes and zero button-2 pushes. odd odd odd. I sent @Panda88 a DM with the logs and a section.log with the individual bits.
   

2. For the long pushes, what is your intent on how you handle the programming. Seems status is the way, not control, as control only has the button pushes while status has a bunch more but you would still need two statuses with and and to know when a long push happens. I have tried many things but am not getting the vibe here.

Edited June 21Jun 21 by sjenkins
editing for DM

Do you have an actual keypress in the log?

I need a little more time to analyze the log - it seems the device is sending data but time not updating (which I do not check for), but I need a little more time

For 2

You can specify what even/control a short press, and long press sends for each button in the button sub node. E.g. Short press send DON and Long press sends DFOF fast off) - there are 4 options to select for each button or an option to toggle DON/DOF of DFON/DFOF for each press. You can then control on those events - note if you have the on/off remote you cannot only specify an event for the push (as it does not determine long or short press)

e.g. program for long press on key 3

s FOB1 Key3Long - [ID 0093][Parent 000E]

If

'SY Fob1 / SY Fob1 key3' is switched Off

Then

Set 's Indoor Light / s MediaRoom / s Mediaroom Front' Off

Else

- No Actions - (To add one, press 'Action')

Edited June 21Jun 21 by Panda88
added more info

i see one getState (poll), which does not seem to generate a change in ST an does not send DON

I see one .Report (actual keypress around 9:20 - it sets ST to 1 and sends DON

That is all I can see in the log (by simple searching) - If you did not press the remote @ 9:20 I do not know why it is sending a keypress

"event": "SmartRemoter.Report",

"time": 1782048005629,

"msgid": "1782048005628",

"data": {

"event": {

"keyMask": 1,

"type": "Press"

},

"battery": 3,

"version": "1404",

"devTemperature": 13,

"beep": false,

"loraP2PHash": 0,

"loraInfo": {

"devNetType": "A",

"signal": 0,

"gatewayId": "",

"gateways": 1

}

},

"deviceId": "d88b4c01000e0a19"

Thanks for the #2 help; I get it now.

The log I gave you, I got the 14 button one key presses ; the whole time the fob was on a shelf, no real pushes. Nothing from button two.

On the #2 problem, long versus short , I set up short as on(DON) and long as off(DOF) for both buttons and in manual tests that works.
On the #1 problem, button #1 is up to 20 program pushes over four days, none of them were physical pushes.

On problem 1

I can see that it happens every 4 hours (exactly) - seems to indicate it is YoLink generated (assuming you do not have a poll on a 4-hour tick) - I really wonder if it is a YoLink issue with the local hub - It sends a report that the key is pressed - even if it is not - I have not seen this with my remote (which is not local yet)

I'll contact then and ask - can you try to run it non-local and see if it still happens

Sure can, so I'm clear, just remove it from the local network on the yolink app. That would make the speaker hub pick it up. But I can still run the yolink local version of your plug-in.

I keep the program running picking up the presses.

yes it should be the case

Can you also make a log with a keypress - when on local hub - I do not have a remote to access (an not on local hub) - YoLink confirmed that the current firmware sends the last event (without the event time) on its heartbeat (4 hours), so I need to see if I can identify a different way to distinguish the heartbeat from a real event

So last night, on speaker hub it sent 3 button 1 long presses (DOF), which seems to confirm your heartbeat thesis. When I get back home from work tonight I will put it back on local hub and get you a log of a few different button pushes.

Thanks - please push few before switcing - I think you need to restart the node for it to register as local device

ok at between 16:00 & 16:33 I went through short/long of 1/2 on the speaker hub. Then I switched to local hub, reset the plugin, and went through the button sequence twice.

YolinkLocal_6-23-2026_43913_PM.zip

Sorry - I need Debug enabled :-(

ok, sorry for delay, had to attend my daughter's swim meet.

look around 21:25 for both buttons , long/short on speaker hub times two.

then a reset

then same x2 of both buttons short/long on local hub

all done with debug logs.

YolinkLocal_6-23-2026_93109_PM.zip

Edited Wednesday at 01:34 AM4 days by sjenkins

OK - I found a way to patch it - what is the easiest way to test - If I issue a version in the beta store of local, can you try to update to that and see if that works before I do a full release

I added one in the best store yolinkLocalSR - should be able to install over the existing node

Once you confirm the fix, I can make a full release

Unfortunately its treating yolinkLocalSR as a different node, not letting me install on top. Its not treating it as beta to your production local. I'm going to need to run for 24hrs to know. If you issue a beta off your production it should work. Worst case I could run two for 24hrs, not sure if there are issues with that?

for now I'm just stopping my main one and running this.

up and going, I'll let you know either tonight or tomorrow morning if I get any rogue button pushes.

Edited Wednesday at 12:20 PM4 days by sjenkins

I did release it as a beta of the production, but I can try again - maybe not change the name

just released with same name ad production in beta

Edited Wednesday at 03:07 PM4 days by Panda88

The beta with the same name was able to load on top.

I did get 4hrs on the one with different name in new slot with no rogue pushes (normal ones tested out).

I am on the beta in normal slot & will let you know tomorrow morning.

sounds good

Looks like there were four rogue button pushes on the last button I manually pushed. So in this log the last four are button 1 short rogue and the previous 6 are on purpose manual on both buttons short/long.

OMG, when I went to the beta with the same name I forgot to put logging back to debug. duh.

I will get you logs later today but since last night there were four rogue button pushes from the last purpose pushed button. So same results.

can you send log of what you have so i can see what is happening

Dm'd you logs

1.8.60 is released - fixing ghost presses for SmartRemoter remote

Thanks so much @Panda88 , works like a charm.