Add light switch for AC#40
Conversation
|
Fix #38 |
|
What IDU model you tested this against? Quoting my PR #36:
In other words, this setting would need need at least being able to detect its "polarity". |
The one from #31 : AP09RK, or RAC_056905_WW by LG Firmware: 690474 |
So it's a Dual Cool Deluxe with air purification device then. Does switching the light ON and OFF from Home Assistant work? |
Yes!
No experience with them, but I wonder if the function is available at all on the LG app, #41 is also not in there. |
Drafteed
left a comment
Drafteed
left a comment
There was a problem hiding this comment.
Please rebase onto the master branch.
|
We still need a way to auto-detect this function presence so HA isn't filled with dead switches and sensors for each IDU. As I wrote above a week ago, the two IDU models I have access to both have tag 0x21f, however neither one allows writing to it and they have opposite reporting polarity on top of that. @skinkie Please post the The recently merged Does the proprietary ThiQ app show a display light switch for your IDU type? |
Which script executes that? If I want to do it manually before running the latest merge of your work?
Don't recall. And now it shows only 'disconnected'. Solved: DNS rebind protection. My problem at this moment. I upgraded to the latest code, for this I obviously had to shutdown the program. Airco does not reconnect to it, even after complete power off. I'll try to hookup the external DNS server tomorrow to see what it queries. |
|
@maciejsszmigiero can you comment on this one too? How do I send the command? |
|
Try something like Edit: To be clear, the MQTT server name is of the rethink built-in server, rather than the external HA one. |
{"did":"4b1a5154-ae3c-1df5-8c7c-64cbe91238bd","mid":1777328040947,"cmd":"packet","type":1,"data":"01010400000065020201027d416a0d"}Would love to understand the meaning of the |
|
That's the outgoing query packet to the device. We are interested in the incoming response to that packet from the device - it will have
Me too :) These numbers come from what the official cloud sends, there are some ideas what these could mean in the "TLVProtocol" page in Wiki. |
|
@maciejsszmigiero Something like this? |
|
Yes, Let me figure out what can be done here when I have a spare moment... |
|
The Since this bit is apparently also set on devices with broken/reverse polarity light switch at tag In the future it might be possible to use the firmware version tag |
|
@maciejsszmigiero how did you found out? |
|
These capability bits are described in a model JSON file that ThinQ API returns in the device list. Then capability tag to capability bits can be inferred by comparing which tags have the same bits set as bits in the model JSON file. |
Can we make this output documentation somewhere on the wiki? |
I second that :) @maciejsszmigiero I've sent you a collaborator invitation in case you'd like to update the wiki. |
|
Thanks @anszom - it's nice to be able to improve knowledge in the Wiki from time to time.
We'll see what could be done there in the longer term, however there's still a lot of manual guesswork required. |
|
Just checked my unit, and it reports the light state with inverted polarity. Writing the value makes the AC beep, but doesn't affect the light. 0x2da=0x4d81 |
4 participants
Me: reverse engineering the protocol
Me: guessing adding the light switch
Gemini: trying to fix the code
Me: actually fixing the HomeAssistant discovery