ha-smartthinq-sensors
ha-smartthinq-sensors copied to clipboard
LG Signature Climate complex lsa50a
Hello!
Basic functions (power/pm sensors) works perfect but it would be nice to have more functions as:
- Speed (/Auto/High/Mid/Low)
- Mode (Silent/Purify/Humidi)
- Filters status
- Lighting mode and state
- Ionizer mode and state
Diagnostic log: lsa50a.json.txt
Could you clarify if and how the Mode affect the Speed? Could also clarify what is Ioniner (is alternative to others modes)
In silent mode speed choice is disabled (i think its forced to low). All speeds are available in humidi and purify modes.
Ionizer is an additional option (not separate mode) and work with any modes.
Ok, I will try to work on this next w.e.
Awesome news! Thx! And one more - this device also have humidi sensor. Can you add him too?
This is partial implemented in v0.23.0
:
- Speed (/Auto/High/Mid/Low) -> Based on Fan entities capabilities
- Filters status sensors
- Humidity sensor
For the Mode
, it is more complex in HA. It should be probably implemented as switchs, keeping in mind the interaction with Fan modes. I'll think about this.
Please provide feed-back about current implemented functionality.
@ollo69 all work perfectly!

Also i find one more air quality sensor: odor. I think its airState.quality.odor. It would be nice to add it too if it's not a big job.
And what do you think about the backlight control (airState.lightingState.displayControl)? The problem is that by default, the devices are turned on with the backlight at full brightness. And if it happens at night, it causes severe discomfort.
What about Fan control? Did you test it? Does it work?
Also i find one more air quality sensor: odor. I think its airState.quality.odor. It would be nice to add it too if it's not a big job.
What does this sensors means (unit, possible values, etc)
What about Fan control? Did you test it? Does it work?
The fan speed is changed via the slider, not via the drop-down menu. Is that the plan?
In drop-down menu only Auto:
What does this sensors means (unit, possible values, etc)
i think its OU/m3
The fan speed is changed via the slider, not via the drop-down menu. Is that the plan?
Yes, by design FAN speed must be represented as percentage. Preset modes can be used for specific fan modes (as Auto), and must be reset when a specific FAN speed percentage is set. You can see more details here.
Does speed change and Auto mode works properly?
i think its OU/m3
But what are the values range for this sensor? What is the data type (float, int...)
Preset modes can be used for specific fan modes (as Auto), and must be reset when a specific FAN speed percentage is set.
So maybe we can use only preset_modes
? I, as a user, do not know what percentage speed value corresponds to preset_modes and it will be difficult for me to set the correct value using the slider.
But what are the values range for this sensor? What is the data type (float, int...)
I think its same values as PM* sensors
So maybe we can use only
preset_modes
? I, as a user, do not know what percentage speed value corresponds to preset_modes and it will be difficult for me to set the correct value using the slider.
No, this is not how it should be. From dev docs:
Preset modes should not include named (manual) speed settings as these should be represented as percentages.
When you set a percentage, I write an additional attribute that will show to you the current named mode.
Okay. But it looks very inconvenient for the user. I wonder what the hassio developers were thinking about.
And should we use the same logic to select the operating modes?
"Value": {
"support.airState.opMode": {
"_comment": "FuncSync_\uc6b4\uc804\ubaa8\ub4dc",
"data_type": "enum",
"value_mapping": {
"0": "@NON",
"10": "@AP_MAIN_MID_OPMODE_CLEAN_W",
"12": "@AP_MAIN_MID_OPMODE_SILENT_W",
"13": "@AP_MAIN_MID_OPMODE_HUMIDITY_W"
}
},
And should we use the same logic to select the operating modes?
Again no, because you can have an op mode selected (Clean or Humidity) and at the same time change the Fan speed, and this is not compliant with specification:
Manually setting a speed must disable any set preset mode. If it is possible to set a percentage speed manually
without disabling the preset mode, create a switch or service to represent the mode
So OpMode
should be managed with some switches or a dedicated service
The real problems is that in HA do not exist a dedicated entity for air-purifier
, so we must use other entities and adapt for this use. But entities specification must be respected!
What you can do is join discord chat and ask to implement a new entity to manage all feature available in air-purifier
.
So OpMode should be managed with some switches or a dedicated service
Maybe as you realise it on AC?

AC must support temperature (current and target).
@ollo69 hello! I find bug. After switching off in hassio, the device physically turns off. But his status in hassio remains on. I rollback to 0.22.0 for test - it work correctly.
On the history line, you can see that the purifier status has never changed to off:
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
@ollo69 hello! I want to come back to this issue. Can you add control for Lighting mode and state for this device? Bcs when its turned on, green light always on. And no way to disable this. Light control support will help create automation that turns off the bright green light when the device is turned on.
@mo1seev,
I think we can use #475 for this.
@ollo69 im not sure, that its same, but lets wait and try =)
Bcs this device also have Ionizer as on AC. And its work for AC and not work for this device.
AC:
Purifier: