In development: LG SmartThinQ component

Check here: https://github.com/ollo69/ha-smartthinq-washer/blob/master/README.md

Where are you stuck?

i install ollo69
is there any card so i can run washer
is this only sensor

Thank you so much. This custom component worked flawlessly. Thanks again. Both my washer and dryer is not showing up in HA

1 Like

Works like a charm, I wish it had options for more sensors but just getting status of dryer and washer is huge improvement

What other sensors are you interested in? Pretty much everything is displayed in the sensor.washer and sensor.dryer and you can create a template sensor if you want to a sensor to display any of that data.

I posted my lovelace UI to the feature request thread, thought I should link to it from here.

@Tomek985 there are loads of sensor values available as attributes on the sensor component. You can see how I used those in my UI by taking a look at the yaml.

Any chance LG Refrigerator will be integrated?

1 Like

@ollo69 Apologies if this has already been asked… Does your component handle dishwashers as well?

Just noticed that, works great!
One welcome implementation detail was handling of defective LG design of Washer when it disconnects.

Not yet…

All,

I just released a new version with refrigerator support.
For the moment refrigerator sensor are very limited and I need feedback because I don’t have one.

Important:

I renamed the repository to ha-smartthinq-sensors.
I also renamed the component to smartthinq_sensors, so you shoud de-configure and remove previous version and install and configure the new one.

Please provide your feed-back directly on github component repository.

Hi, @ollo69—have you considered contributing your improvements to the wideq library back to the main repository so other projects can use them? As it stands, because you have copied and modified the original source code, the changes you make there are not accessible to other tools—for example, integrations for smart home software beyond Home Assistant. And bug fixes we make in the central wideq repository won’t (automatically) be available to your component.

I am also a little disappointed that the documentation for your component doesn’t contain any attribution about where you took the original code from. You have also changed the license, which is not really allowed. I imagine that this may be an early foray into open-source development for you, which is really exciting! But you might want to read up on some OSS etiquette advice, for example.

1 Like

Hi @samps,

no problem from my point of view to contribute to the original WideQ library, problem is that I changed the structure to better manage devices in HA and merge the code id the library seems quite complex. Anyway I will be happy if you have some suggestion on how to proceed.

Related to documentation, you are right, I honestly do not have time to update it, but I will add asap reference to WideQ project.

For the license, yes I’m not so expert in open-source rules. Should I change to different one?

My objective was just to provide a working componet to the comunity and enjoy myself in code developing, there are no other interest insight.
I’m senior developer wih more than 25 years experience but write code still make me happy, but I normally work on non open-source projects…

1 Like

Awesome! It would be really fun to see how we can incorporate the changes—I think the best way to start would be seeing what parts are easiest to merge back without wholesale restructuring and open a pull request. Or if you think the reorganization is an important improvement, maybe you can open an issue to describe the idea for how the new organization should go?

A good place to start understanding a given license is choosealicense.com’s bullet-point explanations. For MIT, there is basically only one requirement: you can do literally anything you want with the code, but you have to include the attribution and license notice with any redistribution. So that means one easy option is to just include the same LICENSE file as for the original code. Or you can pick any license you like for your code as long as you just add the attribution statement for the code that has been reused.

Thanks for your awesome efforts on making all this stuff better and cover more device types!! It’s truly great and the best kind of outcome of the open-source development model.

1 Like

This is amazing. Thank you!

Good job!!

I would like support LG HAVC (PC12SQ NSJ), please :blush:

Great work @ollo69 ! This works great for my washer and dryer. My LG refrigerator also shows now in HA. The door open sensor works, however the fridge and freezer temps are incorrect.

Actual Fridge Temp = 36 F
Home Assistant Sensor = 51.8 F

Actual Freezer Temp = 0 F
Home Assistant Sensor = 46.4 F

I thought maybe there was just an offset for some reason, but when I lowered the Freezer temp 3 degrees, the Home Assistant sensor reported an increase of 5 degrees. So it isn’t just a simple offset unfortunately.

I need some more information because every LG device have different working mode.
Are you able to provide me some debug log as decribed here so that I can check the right way to detect temperature?

Thanks

@ollo69, I updated my smartthinq integration in HACS to v0.3.8 and now the temperatures show correctly for the freezer and fridge!

After upgrade to v0.3.8 dont show temperature.