You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything seems to work with my Washer except for the Download Cycle. I.e. the washing program that you can download in the lg thinq app so that you then can use it on your washer. Currently, even if I select the "Download Cycle" on the washer, the integration still says that I've selected "Cotton" and if I try to start the washer remotely with the downloaded cycle preselected, the washer automatically switches to "Cotton" when it starts. I don't see the downloaded cycle in the list of programs availible in the integration either, or any mention of it in the attributes of the entities created.
The text was updated successfully, but these errors were encountered:
I think I have a similar problem. But the same you had with the donwloaded program I had with the pre installed program "easy care" in german Pflegeleicht. I selected Pflegeleicht in Homeassistant and also manually switched at the washer to pflegeleicht. Homeassistant was previously set to current course, I changed to pflegeleicht and started the machine. But the ThinQ App showed Cotton as running program. Maybe it's related to the machine modell?
Here it's a: F4WB209Y
[Edit]
I also can't select the downloaded program
[/Edit]
Everything seems to work with my Washer except for the Download Cycle. I.e. the washing program that you can download in the lg thinq app so that you then can use it on your washer. Currently, even if I select the "Download Cycle" on the washer, the integration still says that I've selected "Cotton" and if I try to start the washer remotely with the downloaded cycle preselected, the washer automatically switches to "Cotton" when it starts. I don't see the downloaded cycle in the list of programs availible in the integration either, or any mention of it in the attributes of the entities created.
The text was updated successfully, but these errors were encountered: