bwade913

The Yolink NS v8.88 has been released containing a fix for the multiple command send issue which prevented Yolink remote buttons from being used to trigger toggle programs. Thanks @panda88! With the fix I'm able to successfully control eight toggle programs with a four button Yolink remote using either short or long key presses. It's similar to my first post in this thread except for these changes: 1. I configure each Yolink remote button to have a short key press send a DON, and a long key press send a DFON. 2. For the programs, I use control rather than status, I have the short press toggle program trigger on ON, and the long press toggle program trigger on Fast ON. So far it seems to work very reliably.

Looking at this again, I think the best way to implement this is to use a single variable expressed as a contact sensor. You can do On/Off routines triggered by Closed/Open states, without the issue of the motion detector waiting for "no motion detected" to timeout. It's working well for me set up this way, there is about a 1-2 second lag on both on/off for the light controlled by the variable.

@tmorse305I got this working today with the virtual toggle switch. It looks like I didn't really need to create a virtual toggle because I could have changed the variable state based on one of the other actual devices in the scene. The virtual toggle would be needed if I was trying to create a scene with only devices unknown to UD. For anyone trying to follow along, here are the steps. 1. Create a state variable, that is set/unset by programs when a member of the scene (virtual or actual) is turned on/off. 2. In the Alexa section of ISY Portal, create an Alexa device based on the variable using the category "motion detector". 3. In the Alexa app, create two routines for turning the targeted device on/off, based on the state of the virtual motion detector. While this can be done with one variable/virtual motion detector, there is a delay turning off, because the smallest interval for "no motion detected" is one minute. It would be better to use two variables and virtual motion detectors catching on/off states so that the trigger for both states uses "motion detected".

@tmorse Thanks for this. It didn't occur to me to use one virtual button in the scene and a separate one outside the scene to turn it off. Regarding the Virtual NS, I saw that but couldn't make much sense of it. I can see now that it could be very useful. I'm actually a big fan of toggle solutions, so this is good information for me. I'm also playing around with Flic buttons and Yolink remotes as triggers for toggle programs.

The Virtual Buttons NS can control any device that supports Alexa integration. I was able to virtually add a smart light bulb to scene by writing programs that use the virtual buttons, and are triggered when when an actual member of the scene changes status to on or off. I've written a post with an example of how to do that.

I have a smart light bulb from a company named Wiz. It doesn't have a dedicated node server that can control it, it's what I refer to as a feral device, but it does have an app that can be used to integrate it as an Alexa controlled device. The Virtual Buttons NS can be used to control any Alexa integrated device using a UD program, but it wasn't obvious at first how to control the feral device through a scene. My solution is to trigger the program with the status of another device in the scene in question. This program detects the scene turning on due to the light switch "Office Main" turning on to its usual 50% level. It calls the program "Desk Lamp On" which is the feral smart bulb. The "Desk Lamp On" program uses a virtual button from the NS to trigger an Alexa Routine. The variable $DeskLamp is set just to track status for a separate toggle program. The Alexa Routine turns on the light in response to the virtual button. There are corresponding programs and a routine for turning off the light.

I'm also seeing this with the Yolink NS. Deleting and reinstalling is the only way to update that NS, and now that's blocked.

Hi @Panda88, thanks! I've attached a debug log for a replicated toggle command. I used different devices this time. The remote button is d88b4c010005f131 and it's controlling a scene with the switch 8b4c01000574cb. I pressed the button at 12:24, the switch toggled on, then at 12:25 it toggled back off again. Yolink_NS_Debug_Log_Command_Resend_Issue.log

Hi @Panda88, I've been experimenting with new Don/Doff and Toggle features available for the Yolink four key remote and have noticed that each command is sent twice. For the Don and Dof commands, this isn't normally very noticeable, but was in my case because I was triggering toggle programs (not your toggle feature) and so my target alway toggled back to the original state. Your toggle feature has the same problem, if added to a scene, the scene always toggle back to the original state. I've attached two activity logs that demonstrate this for a Don command, and a Toggle command. Each is the result of a single remote button key press, where the button is controlling a scene. The remote button is n005_c01000534key0. The devices n005_8b4c0100056aae and n005_8b4c0100056ca0 are two Yolink On/Off switches in the scene controlled by the remote button press. Event_Log_Don_Test.txt Event_Log_Toggle_Test.txt

Unfortunately, this toggle program isn't working as well as I thought. The Yolink remote seems to be resending the command, causing the toggle to flip back to the original state. This happens at varying intervals from a few seconds up to a minute. So, it is still possible to assign two functions to one button, but a toggle function was a poor choice for an example. A better example would be choosing between two AV configurations with one button. A short press choosing one setup program, and a long press choosing another.

I have a four button Yolink remote that I use to control eight different devices/scenes using short/long key presses to run different toggle programs. Today, I modified my programs to use the new Control mode with Don/Doff commands. It was a bit confusing at first but I got it to work, so I thought I'd document it for others that might want to try it. In my example, I'm using a short key press on button three to toggle a lamp in my AV room, and a long key press to toggle a ceiling light. I set button three of the Yolink remote to send Don for a short key press, and Doff for a long key press: I have master/slave programs to run the toggle programs based on the key presses. AV Lamp master is actuated by a short key press: The master program calls the slave program: Ceiling light master program is actuated by a long key press: The master program calls the slave program:

In the case where auto-updating fails, is there a way to force the update without having to delete/reinstall the PM? There’s a fair amount of work involved with reinstall.

3.1.22 on an Eisy.

I have updated the Yolink NS twice since I first installed, and both times it has displayed the new version on startup for several seconds, then displayed the old version. Today I upgraded to ver 8.41 and it reverted back to 8.2. If I delete the NS and reinstall, I get the new version, so that's my solution. I don't know much about NS updates, but aren't they supposed to happen automatically with a restart?

Thanks! I was getting the sense that it was time dependent, but my testing didn't really pan out. It's more reliable when I pause between switches, but I've still seen it happen with just two on/off commands a minute apart.

Hi @Panda88, I am having a similar problem with Yolink Plug Mini devices. They are staying connected to the Yolink hub, but are temporarily losing contact with the NS. When connected, they respond to the first Admin Console command (scene on/off), but then often, but not always, fail to respond to the next command, and status goes to "not connected" in the Admin Console. If I then switch them with the Yolink app, they immediately reconnect to the NS and status goes to "connected" in the Admin Console. Here is the NS log for when I turned the scene on and then off. Both switches in the scene responded to the on command, but when I turned the scene off, the device 8b4c0100056ca0 responded, but 8b4c0100056aae did not. Then 8b4c0100056aae reconnected when I switched it from the Yolink app. 2023-02-20 11:08:14,931 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056ca0 :: ST to 1 UOM 25 2023-02-20 11:08:15,069 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056ca0 :: GV0 to 0 UOM 25 2023-02-20 11:08:15,169 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056ca0 :: GV3 to 0.0 UOM 30 2023-02-20 11:08:15,268 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056ca0 :: GV4 to 0.0 UOM 33 2023-02-20 11:08:18,271 Thread-2585 udi_interface ERROR yoLink_init_V3:process_message: Non-000000 code Can't connect to Device : {"code": "000201", "time": 1676916498253, "msgid": "1676916494137", "method": "Outlet.setState", "data": {}, "targetDevice": "d88b4c0100056aae", "desc": "Can't connect to Device"} 2023-02-20 11:08:18,271 Thread-2585 udi_interface INFO udiYoOutletV2:updateStatus: udiYoOutlet updateStatus 2023-02-20 11:08:18,272 Thread-2585 udi_interface ERROR yolink_mqtt_classV3:updateCallbackStatus: Outlet: Can't connect to Device 2023-02-20 11:08:18,272 Thread-2585 udi_interface INFO udiYoOutletV2:updateData: udiYoOutlet updateData 2023-02-20 11:08:18,303 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: GV0 to 99 UOM 25 2023-02-20 11:08:18,441 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: GV1 to 0 UOM 57 2023-02-20 11:08:18,539 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: GV2 to 0 UOM 57 2023-02-20 11:08:18,640 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: GV3 to -1 UOM 30 2023-02-20 11:08:18,741 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: GV4 to -1 UOM 33 2023-02-20 11:08:18,841 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0100056aae :: ST to 0 UOM 25

Hi @Panda88, I've written a simple program to perform an on/off toggle when a Yolink Fob button is pushed. I'm having an issue where the statement "If 'Mini YRemote' ComboPress is Key1 - Short" only catches the button press, if I have previously selected another button, so there is a new transition to "Key1 - Short". In other words, the program won't be triggered by consecutive presses of the same button. Is there something you can do like have key press status time out so that transitions do occur for subsequent key presses of the same button? BTW, a similar toggle works for a Flic button that calls the same slave program.

I have one of the Yolink four button fob remotes now and it is working well. I am using programs to turn scenes on and off with key presses, short for on and long for off. So far so good. A toggle option would be nice, then we could get eight functions out of the four buttons. I suppose a program could be made to do a toggle meanwhile.

@johnstonf yes you will need the Yolink hub. The node server gets the device configurations from the hub and makes them available in the admin console. All of the Yolink devices I've tried so far (leak sensor, motion sensor, switches) have been very reliable. The Yolink NS developer is in the process of adding support for a Yolink remote, the four button "fob" product. Yolink makes an eight button remote that will never be supported by the NS, because it does not link to the hub, it only links to other Yolink device with a direct device to device link.

OK, thanks. I have one of the smart fobs on the way and will try that.

Hello @Panda88, I have a question about configuring the Yolink remote with the NS. Since it is never linked to the hub, how does the NS learn about it? There is no QR code on the one I have, or any mention of what the device key is. I can link it to my other Yolink devices, but that doesn't cause it to show in the Admin Console. Is there some way to link it to the hub that Yolink hasn't documented?

@Panda88 That was fast! I know you just ordered a remote last week. I've been very happy with the Yolink node server, and the Yolink devices I've purchased so far. I'll be getting a remote too.

Good to hear. Those setting differences are mentioned in the Wiki in the section about passing parameters to IFTTT.

I just got this notification program for Yolink Leak Sensors working so that a notification message is sent to a Slack channel with information about which sensor(s) was/were triggered. I wanted to use a single Network Resource, to pass information about which of the four leak sensors triggered, so it needed to pass four variables. I ran into some hurdles, so I'm writing this example up to guide other noobs through the process. I have one program for each sensor, that sets a variable specific to that sensor. It sets the variable if the sensor is reporting "Wet" and then resets it if the sensor goes back to "Dry". If it's wet, it runs the resource. The resource "Water_Sensor" then passes all four variables as "value1" per the wiki. There are three values that can be passed to IFTTT. I used only one, since I'm fine eventually printing it all as a single string. Note the variable syntax: ${var.<valueType>.<valueID>} var is a string indicating a variable. Don't substitute your variable name, like I tried to do. valueType is set to "1" because these are integer variables. A state variable would need a 2 here. valueID is set to the number in the first column in the admin console variable page that corresponds to your variable. My variables are 2,3,4,5 because I've only used one variable before this. I used the event name Water_Sensor and have an IFTTT applet of the same name. To get your IFTTT "key", go to the following page and select "Documentation". https://ifttt.com/maker_webhooks There is a a mistake in the Wiki, first noted on this forum five years ago where it says to in IFTTT, create a recipe using "maker", where you really need to use "webhooks" for the This section. Using webhooks, there are two options, one that supports JsonPayloads and the other "Receive a web request" which supports the value1, value2, value3 string passing that we are using. In the screen cap below, I am showing what it looks like when "Add ingredient" is selected to insert the variable strings. Besides "value1" I used "EventName" and "OccurredAt" to capture the name and date stamp. Here's what the notification message looks like in Slack. My wife pointed out that I misspelled Laundry. BTW, I'd be interested if anyone can explain what JsonPayload would be useful for and whether UD supports it.

Thanks! The Yolink remote is interesting to me too.