Got pretty far tonight:
1.) Now connects to MQTT and subscribes to your topics
2.) MQTT reconnect support if the connection is lost
3.) Right now it just logs the commands that appear on MQTT. It'd be awesome if someone who owns the devices could show the logs of messages. Like for a fridge - open/close door, for an oven - on/off, dishwasher - on/off, etc.
4.) Added refresh token support to OAuth
5.) Added the first steps of some error handling
6.) Code cleanups and removal of some duplicate code
Note: Right now I'm building this for v2 devices, older devices might not get detected. We can do v1 as well, but might be hard if we don't have devices to test with. wideq supports v1 nicely though so there is a really good example.
The idiots at Home Depot (last time I shop there!) just told me my appliances are delayed a month so this project is at a standstill unless someone can get me some mqtt messages to dissect.
Thanks for working this up. I am trying it out now. I got a LG fridge i have been wanting to play with, and rig a smart speaker like alexa to automatically yell at my kids when they leave the door open.
I've got an LG Washer & Dryer and I'd love to help provide more data; unfortunately, I can't get past the RSA and CSR key generation. Can you provide any more specifics on what should be selected on that cert site? Thanks.
Thanks - I've tried this multiple times, and keep getting this error:
Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: Cannot get property 'certificatePem' on null object
Google login worked fine for me. I created a brand new account linked to my Gmail and I was able to login and get my device list. Are you getting an error?
Ok, thanks for all the help I've received so far testing!
I just made a few enhancements:
The way I had this written before, it would only detect v1 devices. I enhanced it to detect v2 as well. I'd appreciate if, after running through the setup, people could show me the foundDevices variable from the app properties (you can hide the device_id if you like), you'll see entries like:
The version is what I'm really interested in, it will help us identify v1 vs v2 devices. Also, I don't currently have a real v2 device, I'm assuming the version string will be thinq2 but it'd be great to see
For anyone with a v1 device, I'm curious what you see in the logs. I currently get this after the devices are added {returnCd=0106, returnMsg=장치가 접속중이 아닙니다., stateCode=F, deviceState=D, timestamp=0} that's Korean for "Device is not connected." That makes sense because I tricked the app into creating a fake device. I'm curious if others get an error or if you see returnCd=0000 which would mean success. I plan to do more work later today so if someone has that much working it'd be great so I can do a little R&D and get it pulling device statuses
@syepes like I said, Google works fine for me. If you could please paste whatever error you're getting that'd be helpful.
@jonathan.lorber as I said in PM, more logs would be great. You're getting an INVALID_HEADER error which makes me think there's something else going on.
The DW times out and has to be made ready for even the ThinQ App to see it. Should we have the DW online/running when setting up, or is it just looking to devices already present in the app?
Most everything is delayed.. the common excuse .. Covid. We ordered new furniture was supposed to be here the week of Christmas. now its out to the 3rd week of January, I can assure you its not transportation slowing things down. we are moving product and material as fast as we can, with volumes growing daily.
What do you mean times out? Are you getting an error? If so please paste. Unfortunately I have no idea if it needs to be running. As I said, I don’t even own any of the devices yet. My advice would be this is going to be a group effort of trial and error. Try stuff and report back. Unfortunately, we don’t have answers yet so we need to try it out and come up with answers together.
Great news that it found the devices! You should see a device created that represents both your dishwasher and oven. However, they don't do anythign yet.
So that's the timeout you're referring to? That wouldn't have anything to do with the DW, it's not talking to the Dishwasher, it talks to the LG cloud. Can you click the Initialize button on that device and tell me what you see in it's logs? In fact, since the Dishwasher is a V1 device, the MQTT doesn't even really apply. I need to make some modifications so that, in your case, the MQTT is handled through your oven.
As far as what state will you see? Nothing. This is a far from complete integration at this point. Here's what would help:
In the logs for the app, with the latest version, if you click the Initialize button on your Dishwasher, can you tell me what gets logged for the APP? It will help me track down if we're successfully communicating with that.
We need to figure out why your MQTT disconnects. When you click the Initialize button as in the previous step, let me know what you see in the DEVICE logs
Once we get that working, then we can start getting the code together so you can log some messages while you "do stuff" (use the oven/stove, use the dishwasher) then I have to figure out what those log messages mean and reverse engineer to get the state.
We're getting somewhere, but there is still a lot of work to do before this is a useful integration. I'm still adding more today though so we'll keep getting closer!
