Closed FS1961 closed 1 year ago
Frank,
This card relies on testing the machine's state, and whether it matches certain English strings, such as '-'
, 'Standby'
, 'Detecting'
, 'Washing'
, 'Rinsing'
, and so on. Unfortunately, to my knowledge, there is no language-neutral way to get state from the LG ThinQ integration, and it varies based on system language.
It appears from your screenshot showing a course named Kurz 14
that, even if your Home Assistant installation may be in English, your LG account is not. The reason you're seeing the course at all (rather than that part hiding itself), and the reason the time is still showing, is probably because the washer is returning its state in another language, and all of the state comparisons made in the code become useless. That's my best guess based on what you've shown me (which does not include the possible or recent state values for the various entities and attributes).
Because of this, I cannot modify my card's code to support all languages or machines (your model is different and may have different state strings), and I cannot tell you precisely what you need to change to make the card work. You'll have to look at what values your entities return during a wash or dry cycle, and write them down. Then, you'll have to modify the configuration.yaml
and card code for this repository to fit those values, to the extent that they differ from the values I've given.
In this same vein, see my answer to your previous issue.
@phrz - Thanks for the response. Actually, most of the states are in English. Kurz is just "short" which is a wash cycle type. I'm happy to do the work, I'm just not sure where. Please see the below attachment. Does this change anything?
Frank, thanks for giving me more context. I see now that your LG account is returning English strings via the ThinQ integration, so that is NOT the cause of the problem.
But I notice that the entities are still showing "0:00:00" as the Remaining time, that the Run state is "Finished", and so on, so my card is accurately reporting this information. In my experience, the Run state is supposed to change to "-", and that's when my card shows everything as "turned off." Because yours is not doing that, the card is not turning off. As far as I know, your washer should be leaving the "Finished" state and going into the "-" state, and if it's not, it's either a difference in your hardware, or something is amiss.
Is this screenshot from right after it finished, or is it from just now? Has the washer been used very recently? Did you go and turn your washer off when you were done? Did your ThinQ integration lose its connection, and never update? Are you running a very old version of the ThinQ integration? I'm running v0.31.2, according to HACS, and the latest version is v0.31.3.
@phrz - Actually, I'm also running 0.31.3. The screen shot is current. The machine has been off (finished) for quite some time.
I'm going to run a load and see if anything changes.
Looks correct during.
Oddly, it's not updating though. And the app!
Updated when it changed cycles:
It's weird because the unit has stopped but the app and integration haven't updated.
Maybe an issue with the LG service and not the integration or the card?
I'm glad you were able to find where the issue lay: between the washer and the LG cloud, or possibly between the LG cloud and the integration. I'd recommend resetting your washer, or basically disconnecting the Wi-Fi and deleting it from the app, then re-adding it. Maybe check your router to see if the washer has poor signal strength. Otherwise, you can call LG, see if they will help (framed in the context of their official app, of course).
For now, I'll close the issue, because the bug doesn't seem to reside in this repository's implementation.
Thanks for indulging me! I'll drop you a line/note to let you know what I find out.
Hello,
Running the 31.3 LG integration and card is showing interesting things. First, I can't get the unit to show it's off/finished. The Wifi or sensing icon is on and the current course is really the last course it did. It is still showing 0:00:00 as the remaining time even though the unit is off? I must be stepping on something but not sure what. Not sure where to edit but I don't want to make it worse. This is an excellent integration - appreciate your hard work!
Please help!
p.s. - had to use a different font because the one you had referenced wasn't working for me for some reason - just fyi.
config.yml excerpt: sensor:
platform: template sensors: washer_door_lock: friendly_name: "Washer Door Lock" value_template: "{{ state_attr('sensor.front_load_washer','door_lock') }}"
washer_time_display: friendly_name: "Washer Time Display" value_template: > {% if is_state('sensor.front_load_washer_run_state', 'Finished') %} {% elif is_state('sensor.front_load_washer_run_state', 'Standby') %} -:-- {% else %} {{ state_attr('sensor.front_load_washer', 'remain_time') }} {% endif %}
blank: friendly_name: "Blank Sensor" value_template: ""
Template card: type: vertical-stack cards: