Xathros

Hello Jimbo, I upgraded the KASA plugin last week and seem to have lost the ability to use the HS220 Smart dimmers. In trying to debug this, I removed one of the dimmers from the plugin, then from the KASA app and reinstalled the dimmer into the App and restarted the plugin. I found in the log where the plugin sees the dimmer and attempts to add it bit it errors as follows: 2026-05-31 00:02:35.282 Thread-11 (run_forever) udi_interface WARNING Controller:discover_new_add_device: Found a new device D8:07:B6:17:B5:A5, adding Island2026-05-31 00:02:35.283 Thread-11 (run_forever) udi_interface ERROR Controller:add_device_node: Device type not yet supported: DeviceType.Dimmer Any way we can regain support for the smart dimmers? Thanks. -Xathros

Is the any possibility that you can use the value in gcode state to populate the finished value into printer state at the end of a print? I guess the best solution would be to get the IoX to recognize the gcode state properly. I haven't heard anything from @Michel Kohanim yet about that issue. Thanks again for your time on this. -Xathros

Thanks. That explains the command failures. I'll put the H2D into LAN only mode and test commands after the current batch of prints is done. Let me know how the alternate status values work out. -Xathros

@bpwwer, Chamber light on/off nor any of the other printer commands are working with my H2D. Maybe I need to be in LAN only mode for them to work but all of the status stuff is working without. I agree that IoX is seeing the correct status for Gcode state. I think printer state could use a look over however. After a print completes, Gcode state says FINISH but printer state remains at PRINTING even after the printer has gone to sleep long after a completed print. I do see other printer states during print start such as homing toolhead, changing filament, calibrating extrusion, cleaning nozzle tip etc. I have had to use some of the other values like percent complete, time remaining, bed target temp and bed current temp to work out the actual state of affairs (finished / idle) at the end of a print. All of these work in the programs unlike Gcode state. I'm hoping @Michel Kohanim can shed some light on why programs are triggering on but not evaluating gcode state properly. Anyway, thanks for looking into this and for your time and effort in developing this plugin. -Xathros

Thanks @bpwwer, I can see the values change in the admin console and in the plugin as you describe. I will check last run time to verify program run. It is odd that I can't get the program to evaluate true when testing "IS" or "IS NOT" for any value. I'm testing with ver 1.0.3 of the plugin as of today with no discernible changes from my previous observations. @Michel Kohanim , Any thoughts on this matter? Is this a bug in IoX? Thanks in advance. -Xathros

@bpwwer, Just a bump. Any thoughts about the above? Thanks. -Xathros

Hello @bpwwer, Wondering if you have any thoughts about the above? I've found a workaround of job finished using percent complete but am unable to act upon any of the error conditions as they all appear in Gcode state. The behavior of Gcode State is very odd in the console. I can't get an IF to evaluate TRUE no matter if I test = or NOT= for any of Gcode State's values. Also as stated above, there is no control from the admin console to the printer. This is obviously not a life threatening situation here but I would like to implement some of my ideas if possible. Thanks again! -Xathros

Just throwing my name into the pool. Same story here. -Xathros

Hello, I just started playing with this plugin and am having an issue where the Gcode state does not seem to work in my programs. I have a program that tests for Gcode state is RUNNING The status on the device shows RUNNING in the admin console but the program shows FALSE. I can see activity from the plugin in the event log as the Gcode state changes and the status is updated on the device in the admin console. Any idea why the program won't show TRUE when the status matches? Also it appears that I'm unable to control the printer via the plugin. Pause, Resume, Chamber light on/off etc. Via program or directly in the admin console. My printer is an H2D if that matters. Thanks in advance. -Xathros

@Panda88 Up and running here again with 0.6.5. Thank you -Xathros

Thanks @bmercier , PG3 is up and going and I can access its console just fine. I opened Safari's console and tried for eisy-ui as suggested. Looks like a problem with a certificate. I tried again with http and am able to login fine. -Xathros

Yessir I am. Looks like an invalid certificate. -Xath

Hello everyone, I attempted to install eisy-ui 0.7.2 this evening. After running the update, I can no longer log in to the eisy-ui web app.. I get to the login screen but when submitting my credentials it just says network error in red beneath the password field . I have rebooted, stopped and started the eisy-ui service but still unable to login. I AM still able to log into the portal and the admin console normally. Any ideas? Thanks in advance. -Xathros

Not working for me either. Doesn't like the old auth key and can't seem to prompt Blink to send a new one. -Xathros

Hello Jimbo, I recently deployed a few EP25 plug modules. These or the WiFi,Bluetooth, HomeKit supported variety. The KASA app recognizes them as do Apple HomeKit, Alexa and Google. The KASA Plugin for PG3 does not seem to see them. Could support for these be added without too much trouble? Thanks in advance and let me know if there is anything I can provide to assist. -Xathros

I’m interested but will need the new hub first. -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

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