Yolink Plug Mini not staying connected

[bwade913]

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

[Panda88]

This is likely different - "code": "000201", means API from yolink is not responding - it may be a timing issue - there is a limit of how many commands that can be sent in 30 sec (if I remember correct) - maybe I need to delay this - I do have observed some of the devices reply "code": "000201"  once in a while - but I never found the root cause - maybe I need to dig for this - it is devices that offer control  where this happens 

[bwade913]

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.

[Panda88]

I can try to reach out to yolink to see if they can offer advice - there may be a more correct way of doing it - of keep track of number of call per min etc?