LG ThinQ Dynamic for eISY / PG3x — Beta Testers Wanted!

I've released LG_ThinQ v0.5.4 Beta in the PG3x Beta Store and am looking for a few people willing to test it.

The plugin automatically discovers compatible LG ThinQ appliances and adds them to IoX, providing real-time status updates and supported controls for use in your home automation programs.

So far, I've tested it with an LG washer, dryer, microwave, and dual oven. I'd especially like feedback from users with other LG appliances.

You will need the Thin Q app and your registered PAT key.

IMPORTANT: This is BETA software. BACKUP, BACKUP, BACKUP your eISY before installing!

Please understand that I have a full-time job and develop this plugin in my spare time. I may not always respond immediately to questions or problems, but I'll do my best to get back to everyone as quickly as I can.

If you give it a try, please let me know what appliances you have, what works, and what doesn't. Feedback and bug reports are always appreciated.

Please remember: Backup, Backup, Backup before installation of the plug in.

Thanks to everyone willing to help test!

@TJF1960 I installed the Beta LG ThinQ plugin to give it a try and provide some feedback. The only LG appliance I have attached to my ThinQ account is an LSN120HSV4 mini split inside wall unit with a PCRCUDT3 Wifi module. The ThinQ app identifies it as a Wall-Mounted A/C.

Plugin installed correctly and connected to my ThinQ account after I created and input my thinq_pat. The Plugin created a "LG ThinQ" node with a subnode for my A/C unit. Unit data seems to populate correctly, although the plugin at this point offers no control, just reporting for my unit. Data reported as follows:

If I turn the unit on, the Run State correctly updates. Updates take a couple of minutes, or immediately if you Query. If I set the sleep timer, the "Timer Relative Minute to Stop" in the right hand column updates (although when I turn it off, this doesn't reset, probably because the unit doesn't report a reset on this event). Note that both the current temperature and target temperature report in Celsius, with no option to change. Since GV7 is the target temperature, I thought that I could change the target temperature by using the G07C07 command at the bottom, but this doesn't seem to affect the target temp.

I am currently on the production IoX 6.1.2_7 and PG3x 3.4.26. I installed the plugin through the PG3 console, not through EISY-ui, although it appears in EISY-ui. Hope this helps your development. Let me know if you have any questions on my install.

Good report! Thank you.

If you could PM me the log files from pg3x I will check to see what info can be had.

After the discovery, the plugin gets what info it can from the LG API and builds what it can from that info., not a lot for controls sadly. But having the logs may provide some more detail.

Thank you!

-Tim

Edit: Also, I need the logs from the initial install, and input of the PAT key to reboot to discovery etc., hopefully all of the is contained in the current log? Along with some of the settings you changed on the unit might be helpful as well. Lol, basically everything from install to now.

Edited 18 hours ago18 hr by TJF1960
additional log info

Log files sent via PM.

Log files no longer contained previous installation, so I stopped and deleted the node server and reinstalled at 10:08:14 this morning in the logs. The ThinQ node server is installed in slot 5. I also temporarily stopped the Ambient weather node server in slot 3 to reduce the entries in the log files, since that NS updates about 20 values every minute. Reinstallation went smoothly and nodes appeared in IoX.

After installation, I modified a number of settings on the unit (through the ThinQ app) to see what the affect on the node values would be. On/off updates relatively quickly, and consistently updates if the node is queried, as do current temperature and target temperature (in Celsius). Interestingly, most of the timer values seem to update when set, and will update as the time counts down, but will not reset after the unit or timer is switched off. GV15/GV18 appear to correspond to what the unit calls Sleep Timer. GV14/GV17 correspond to the unit's "One Time Schedule" start and GV16/GV19 correspond to the unit's "One Time Schedule" start. Setting a recurring schedule on the unit does not appear to affect any of the node values. As my unit is a heat pump, it has mode in addition to on/off, and changing the mode from heat to cool does not appear to be reflected anywhere in the node.

Let me know if you need anything else.

Dave

Received logs and thank you for the notes above. I will return.

-Tim