Xathros

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 did. Seems my Unifi controller sees it as a new device after the upgrade. Had to reset the reservation. No big deal, just unexpected. -Xath

Upgrade completed with no problem. Only issue I encountered is the eisy got a different dhcp IP assignment after upgrade. Entire process took about 15 minutes. -Xathros

Hi @Panda88 All was working great till this morning. UDM notifications indicated that the Yolink poly along with other polys disconnected and reconnected overnight. I suspect that's the point where it began failing. I have verified my UAID and Secret key. Neither have changed. All the Yolink stuff is still working within the Yolink app. I'll PM my full log. Thanks. -Xathros

Hello all, Seem to be having some issues this morning with Yolink. The Yolink app is working just fine but the poly fails to get current statuses. Log show the following repeating every 4-5 seconds: 2024-05-07 08:55:49,723 Thread-7 udi_interface INFO yoLink_init_V3:connect_to_broker: Connecting to broker... 2024-05-07 08:55:49,723 Thread-7 udi_interface DEBUG yoLink_init_V3:request_new_token: yoAccess Token exists : True 2024-05-07 08:55:49,723 Thread-7 udi_interface INFO yoLink_init_V3:connect_to_broker: Retrieving YoLink API info 2024-05-07 08:55:49,723 Thread-7 udi_interface DEBUG yoLink_init_V3:retrieve_device_list: retrieve_device_list 2024-05-07 08:55:50,160 Thread-7 udi_interface DEBUG yoLink_init_V3:retrieve_device_list: device_list : [{'deviceId': 'd88b4c0100074ca9', 'deviceUDID': '2957d90d375544aea49991785390e155', 'name': 'Barn Motion Sensor', 'token': '8A47DACB92276044A076C5CFD8D7018D', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c02000ca3e4', 'deviceUDID': '2fc6f498d94d4a699f9fbe38d12ec50e', 'name': 'Basement Door Sensor', 'token': '122D727B7F4E92B4E92A858A23F6A511', 'type': 'DoorSensor', 'parentDeviceId': None, 'modelName': 'YS7704-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c01000757db', 'deviceUDID': 'aa818c60c8cf4be7aa7e6fbdfd8e1d0e', 'name': 'Basement Motion Sensor', 'token': 'A60A9E9F9D9C2480D7CF32A1A1322065', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100075033', 'deviceUDID': '74f560ea575148cfa02173b5d50492ad', 'name': 'Basement Stairs', 'token': '257A5324CAAD9E3011E964C09A27CC47', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c010004c458', 'deviceUDID': 'e2abd27375a34fa5b6f80fdf3a2fedba', 'name': 'Garage Fridge', 'token': 'C3A3488CC2342C8A15083BEE319B9F39', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100074bcd', 'deviceUDID': 'f26d5bc3da734588aca9e91da2c8b5b7', 'name': 'Garage Motion', 'token': 'B58BD964F3F29CF97065CD99143ABD34', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c020005ca60', 'deviceUDID': '06326306a9794126aba60770f8482e2d', 'name': 'Garage Temperature', 'token': 'B60C1EA7F4198D4CD89BF418F166A0D8', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100063524', 'deviceUDID': '3a9fddd9f1a343488f6b897e344d17e3', 'name': 'Kitchen Fridge', 'token': '39126021820D4D92100F11C9A829D7F0', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100090d2e', 'deviceUDID': '71fee28929174bb095b6e05766583f2a', 'name': 'Machine Shop Motion Sensor', 'token': '4C4B5760F769A8C8345E3DE106764D48', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0200076baf', 'deviceUDID': '1d3e9b6beca14bffa54f4c8c5d7eb470', 'name': 'Screen Porch Temperature', 'token': '960D33529B3526CF469515F41B371D5E', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c02000ca0f2', 'deviceUDID': '2635e0da3439452c8015244725f856cb', 'name': 'Shop Stairs Door Sensor', 'token': '498AA52AE154E138723BA81259A01289', 'type': 'DoorSensor', 'parentDeviceId': None, 'modelName': 'YS7704-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100075378', 'deviceUDID': 'b436e639361943b4bd5e5d3e541723e6', 'name': 'shop Stairwell', 'token': 'A3C1FC53C868B5E36BEF8AE6D3271F89', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c010004cbd9', 'deviceUDID': 'a5d4448c0a9e46419f3468ea5f407d3b', 'name': 'Spider Lake', 'token': 'E7496CC5BD1034D4409AFDC51869E44D', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8004-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c02000ca156', 'deviceUDID': 'f0b85664f2fd449898156d720649c41d', 'name': 'Tool Room Door Sensor', 'token': '7EE37DFFEC0CB7D836BA62B3A3F1B2C0', 'type': 'DoorSensor', 'parentDeviceId': None, 'modelName': 'YS7704-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100090c6b', 'deviceUDID': '4f321b5b28c24589aae2d585209268b7', 'name': 'Tool Room Motion Sensor', 'token': '840E59ABFD0B7FB04215EB9DA5CB8288', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100098c15', 'deviceUDID': 'f52d9cd79c0741e38c2a933f5d211363', 'name': 'Water Pump Outlet', 'token': '3BCAAF2A4C317104520910A29A3D41A0', 'type': 'Outlet', 'parentDeviceId': None, 'modelName': 'YS6803-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0200078fe5', 'deviceUDID': 'dd73bd9582c64324923143ac61198d8a', 'name': 'Well House Temperature', 'token': '2D31986E331744DA9A41F3A07B90AE12', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c010007495a', 'deviceUDID': 'e0729530911d4c708aa7bd5b367a6064', 'name': 'Woodshop Motion', 'token': '348BE8EF533A99B8ECDAB3E2BE9A79A6', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100063a2c', 'deviceUDID': '243ee4d7b8544760951022fab7f3ea0d', 'name': 'WoodshopTemp Humidity', 'token': 'F548FDEC2774416B7BC0CE4F1DB8008C', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100075618', 'deviceUDID': 'c76a871c1bce40c99ff67a6b6dd8dd5e', 'name': 'Workshop Motion', 'token': 'D48ABA71859E471754556E1440891338', 'type': 'MotionSensor', 'parentDeviceId': None, 'modelName': 'YS7804-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c0100063078', 'deviceUDID': '21d928ed95f64391a7d61b5d614f37ec', 'name': 'Workshop Temp and Humidity', 'token': '0B958957F1FC17F684D13C1EE562F062', 'type': 'THSensor', 'parentDeviceId': None, 'modelName': 'YS8003-UC', 'serviceZone': 'us_west_1'}, {'deviceId': 'd88b4c1603025463', 'deviceUDID': '16a35a2e0e4942839ec187c5553b345b', 'name': 'YoLink Hub', 'token': 'DAB5E188D4A5DFB563BA10BD77350942', 'type': 'Hub', 'parentDeviceId': None, 'modelName': 'YS1603-UC', 'serviceZone': None}] 2024-05-07 08:55:56,263 Thread-7 udi_interface ERROR yoLink_init_V3:connect_to_broker: Exception - connect_to_broker: timed out Any thoughts? Thanks oin advance. -Xathros

I’m in a good place with eISY and PG3x linking Kasa,Yolink,AmbientWeather and a bunch of other things with my Insteon gear. Alexa is able to operate almost everything. I’ve also set up homebridge to get Siri control working but that still leaves something to be desired. My hope is that Matter will unify things so that I can control and query things equally with Alexa, Siri or Google without the need for things like homebridge. Some of my automations are via Alexa routines or in Apple home rather than eISY programs. Ideally I’d have all of the logic on the eISY and not have to depend on internet access or worry about Amazon breaking their stuff on a regular basis. I have a few Matter capable Kasa devices that Apple HomeKit found and adopted without much effort on my part. I control them via Kasa poly on the eISY for the most part. -Xathros

Hi All, Just to add myself to the pool here. Contact sensors not triggering Alexa routines for me either. Been out for maybe about a week (Not sure exactly when it stopped working). I see the correct contact state in the Alexa app and it changes in nearly real time. I don't believe this is a UDI skill or portal problem at this point. Looks like Amazon just broke their stuff. Probably happened around the time they added the floor plan smart home feature. HMMM - I set up a floor plan to play with in the Alexa app maybe around the time the routines stopped triggering. Anyone else or is that just coincidence? -Xathros

Hello @JMC, Log into Openweathermap.com with your account credentials. Click API Keys at the top of the page. In another browser window/tab log into Polyglot. Click on details on the Openweathermap node server, scroll down to custom configuration parameters and compare the API key listed there with the one in Openweathermap.com window/tab. In addition, on the Openweathermap node server, you can select the log tab and set log level to INFO. Stop and start the node server and watch the log for any info that might clue you in to what's going wrong. Hope this helps. -Xathros

3.1.2 Running fine for me as well. I had installed 3.1.1 after the 5.71 IoX upgrade with no problems as well. -Xathros

Hello Javi, I've seen some chatter over the years about adding a color picker to UD Mobile. Is that still on the roadmap? I've been getting by with a web based color to hex tool and copy/pasting into UD Mobile but it would be soooo much nicer if we could just do this at the point of use within UD Mobile. Any thoughts / timeline? Thanks and keep up the awesome work! -Xathros

Thank you. This will make finding problems in the log much easier. -Xathros

Hello @bmercier, Not sure is this is a bug or not but in at least the last 2 versions of PG3X, I am unable to get the system log to stay at anything other than the info level. I can change the dropdown to any other log level but if I leave the log page and come back, it's back to info. I'd prefer to have at error or warning for my normal day to day usage. -Xathros

Hello all, Please disregard my post (above) about disabled programs running. After messing with this for a while I finally realized that I had some Alexa routines set up that followed my state variables for the washer and dryer running states. Life was so much simpler when everything was done on the ISY... Now with automations set up in ISY, Alexa, Kasa, Smartthings, HomeKit etc it's getting harder to figure out exactly where the point of failure lies when there's a problem. I should have known it wasn't the ISY/IoX! 🤨 -Xathros

Same here. In fact, I've been struggling to get all 3 of my doors working with the My-Q stuff since one is a commercial opener and some of the My-Q gateway/hub devices don't work with the commercial openers. Finally got it all working and now they block my access with anything other than their crappy app. The only real feature I use in their app is a scheduled close at night if I forgot and left a door open. I can code that on the ISY so no loss there. I'm installing the YoLink stuff and will end up with better functionality on all three doors for less than the price of one My-Q gateway. And no more disco party flashing lights when I close my shop door from the house! -Xathros

Disabled Program still triggering Hello all. After the DST issues yesterday and messing around re-enabling all of my normally enabled programs, I've run into a curious situation. I have a pair of programs that I have disabled and they are still triggering based on the change in state of a state var. I have enabled/disabled them again and they still trigger. As a test, I created another simple program that triggers on a state var, disabled it and tested, it does NOT trigger when I change the variable state. Here is the program that should not be running Note that it shows as disabled. I have searched using the find feature for anything that might call this program and everything that references s.DryerRunning and there is nothing else that would trigger this to run. #Washer Notifier-Tracker is also triggering while disabled based on the change in it's state var. There are no folder conditions present in the Washer-Dryer folder. Now here is my test program: This one does not trigger when I set s.test to 1. This is the behavior I expect from a disabled program. Here is my version info: isy-5.7.0_5 Name : isy Version : 5.7.0_5 Installed on : Mon Nov 6 08:09:02 2023 CST And to maintain some continuity with the posts above, my Sunrise/Sunset times are correct today! -Xathros

Well, thanks to the DST kerfuffle today, I had to restart my systems. I have lost access to all 3 of my My-Q doors. Just ordered the YoLink Garage Door stuff. I'm already using YoLink for motion and temp sensing and am quite happy with the performance and stability of their devices. Can't say I'm going to miss Chamberlain, My-Q and their issues. I'll keep the My-Q node server installed for now in case Goose and the others can get it working again. -Xathros

Sunrise/Sunset are an hour early on my system as well. I'm in Central Timezone. DST checkbox is checked and grayed out. -Xathros

Hey @DreamerI90, You're not alone. This morning all of my programs were disabled. Quite sure this has to do with DST change. Over the years, I have had odd issues with the ISY and DST changes. This I think is the first time all of my programs went disabled though. It wasn't too hard for me to recover as I have all of my disabled program names begin with a # so I can sort on the summary screen select all but the #programs and re-enable all at once. A trick I learned a while back on these forums. Interestingly, I restarted IoX before discovering that all the progs were disabled and any program that was set to run at startup did in fact run as well as any that were called by my startup programs. I get that the programs that were called by others should have ran. Not sure if a DISABLED program that is set to run at startup should actually run at startup. @Michel Kohanim or @Chris Jahn - Thoughts, comments? Thanks. -Xathros

FWIW, My My-Q instance has been running trouble free for nearly 2 weeks now. Based on the chatter above, I don't dare restart it. -Xath

@Andy C First let me say I use beeps for doors opening all the time! I absolutely love the feature and am disappointed to be losing this capability as I move from Insteon to Kasa wall switches. I'm keeping a bunch of Insteon plug modules mostly just to keep my beeps! I'm not sure if this will help with your freezing problem or not but may I suggest that you create a scene containing all of the devices that you want to beep and then have your program beep that single scene rather than all of the devices individually. This will greatly reduce the Insteon traffic and make things much smoother. In addition, all of the devices will beep simultaneously rather than each in turn which I found I prefer. Hope this helps. -Xathros

Updated to new MyQ poly this morning and I'm back up and running. For those who updated and tried to restart right away, stop the poly for 30 minutes then restart. Thanks @Goose66for the quick response and update! -Xathros

I have both an ! and an @ in my PW but same without and they work in the MyQ app just fine. I did see someone in the Home Assistant world claiming to have solved it by changing user agent in the request to none. See below: JGrantman commented last month OK... this sure looks like an issue with Home Assistant. MyQ working via app without issue. Had been working in Home Assistant without issue for months or more... maybe 18 months? Update to Home Assistant 2023.9.1 and it broke. Same unauthorized error in logs. Following steps fixed issue for several days (until update to Home Assistant 2023.9.2). docker exec -it homeassistant bash cd /usr/local/lib/python3.11/site-packages/pymyq/ cp request.py request_bup.py vi request.py i to enter insert mode Modify line 34 Was self._useragent = None Is self._useragent = str("none") Esc key to exit insert mode :w + enter to write the changes :x + enter to exit VI Restart Home Assistant After update to Home Assistant 2023.9.2 after restart MyQ not working (again). Didn't even bother checking logs and just popped open ssh and executed the same steps (above) and restarted. MyQ now working as expected. Line 34 in /usr/local/lib/python3.11/site-packages/pymyq/request.py appears to be the culprit. Did not check if it changed with Home Assistant 2023.9.1 or if something else changed resulting in line 34 becoming an issue? Does it matter? There is enough discussion and detail confirming the change to line 34 fixes MyQ and persists (until Home Assistant update reverts the fix back to not working state). What is the impact or risk to using the line 34 update going forward? Obviously someone closer to the code and with sufficient understanding of the entire code could weigh in on any non-obvious negative impact if line 34 in /usr/local/lib/python3.11/site-packages/pymyq/request.py is changed -- but it seems like low hanging fruit and easy fix to big impact issue. (Big impact if you use MyQ for garage door). Dunno if this helps with the MyQ poly or not but figured I'd share what I found. -Xathros

Like @Chris McKean, @dbwarner5 and @glarsen above, a 30 minute shutdown did not solve the issue. I left if shutdown overnight and still a problem on startup today. For what its worth, the MyQ app on my iPhone is working just fine using the exact same credentials. Any other ideas? Thanks! -Xathros

Hello, I am having an issue with the MyQ Nodeserver this morning. After upgrading PG3x to the latest version (3.2.9), the node server cannot log into the MyQ service. I don't believe this is related to the PG3x update other than for the fact that the upgrade caused a restart and the node server needed to re authenticate with MyQ. I'm guessing MyQ changed something on their end? Here is an excerpt from my log: Network/server error logging into MyQ service: 401 Client Error: Unauthorized for url: https://partner-identity.myq-cloud.com/connect/token Any ideas? Thanks in advance. -Xathros

Hi DennisC, Thanks. I figured out which node the file belongs with and then removed the file. The node still appears to operate normally and now my backup completes. I'll watch for any other anomalies and hope that I haven't done any damage by removing the file. -Xathros