Hi Panda88,

 

After a power outage yesterday, my YoLink plugin is sending Fail/reconnect messages about every 10 seconds.  In addition, the plugin behavior on the dashboard is strange.  If I stop the plugin, PG says it stopped but  after a few seconds, the dashboard shows it as connected again - although log activity stops and the fail/reconnect messages stop.  Subsequent attempts to stop the plugin result in a message saying it can't be stopped because it isn't running.

Here is an excerpt from my YoLink log that shows the failure cycle:

2025-02-16 08:46:36.291 MQTT       udi_interface.interface INFO     interface:_disconnect: MQTT Unexpected disconnection. Reason code: Unspecified error. Sent by server: False. Retry in 10 seconds.
2025-02-16 08:46:39.127 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:46:43.130 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:46:46.300 MQTT       udi_interface.interface INFO     interface:_disconnect: MQTT: Reconnect successful
2025-02-16 08:46:47.131 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:46:47.348 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with Reason code: Success
2025-02-16 08:46:47.348 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:xx:xx:xx:xx_5 -  MID: 103 Result: 0
2025-02-16 08:46:47.392 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Successfully for Message ID: 103. Reason codes: ['Granted QoS 0']
2025-02-16 08:46:51.132 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:46:55.144 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:46:58.330 MQTT       udi_interface.interface INFO     interface:_disconnect: MQTT Unexpected disconnection. Reason code: Unspecified error. Sent by server: False. Retry in 10 seconds.
2025-02-16 08:46:59.145 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:03.147 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:07.153 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:08.340 MQTT       udi_interface.interface INFO     interface:_disconnect: MQTT: Reconnect successful
2025-02-16 08:47:09.389 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with Reason code: Success
2025-02-16 08:47:09.389 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:xx:xx:xx:xx_5 -  MID: 105 Result: 0
2025-02-16 08:47:09.430 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Successfully for Message ID: 105. Reason codes: ['Granted QoS 0']
2025-02-16 08:47:11.155 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:15.167 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:19.178 Thread-7 (start) udi_interface      DEBUG    udi-YoLink:addNodes: Waiting for node MotionSensor-Basement Motion Sensor to be ready
2025-02-16 08:47:20.369 MQTT       udi_interface.interface INFO     interface:_disconnect: MQTT Unexpected disconnection. Reason code: Unspecified error. Sent by server: False. Retry in 10 seconds.

Unlike my previous issues, this seems to be a local connection issue with MQQT rather than broker issues with the YoLink cloud service.  I have deleted and reinstalled the plugin with the same outcome.  

I'm on IoX 5.9.1, PG3 3.3.18

Any idea what's going on here?

Thanks in advance.

 

-Xathros

I have seen the same.   I believe is it related to the eIsy    i did a reboot /power cy le and IT went away.   I am travelling but will check for updates to the mqtt package to see if there could be some fixes there