lg_thinq: Missing entities for DEVICE_AIR_CONDITIONER (energy_current, filter_remaining_life) — available in ha-smartthinq-sensors but absent in official integration

[grfernandes54]

Integration name

lg_thinq

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lg_thinq

Describe the enhancement

Currently, the lg_thinq integration exposes a limited set of entities for LG air conditioners (e.g. DEVICE_AIR_CONDITIONER, model RAC_056905_WW). Several useful entities that were previously available through the community integration ha-smartthinq-sensors are absent from the official integration.
The specific missing entities for this device are:

Energy current — real-time power consumption (W)
Filter remaining life — percentage of filter life remaining

These entities are exposed by the LG ThinQ API and were working via ha-smartthinq-sensors until LG recently blocked the API endpoint that project relied on (see ollo69/ha-smartthinq-sensors#961). Since the official lg_thinq integration uses the sanctioned LG API, it is in the best position to expose these same capabilities — yet it currently does not.
It doesn't make sense for the official integration to offer fewer features than a community project was able to provide. Now that users are being forced to migrate from ha-smartthinq-sensors to lg_thinq, the feature gap is a real regression in functionality.

Use cases

1. Energy monitoring: The energy_current entity allows users to track real-time power consumption of their AC unit and integrate it into the Home Assistant Energy Dashboard or create automations (e.g., alert when consumption exceeds a threshold, or turn off the unit after X kWh).

2. Maintenance reminders: The filter_remaining_life entity enables automations that notify users when the air filter needs cleaning or replacement, helping maintain air quality and device efficiency.

Both use cases were fully functional with ha-smartthinq-sensors and are expected to work with the official API. Losing them forces users to either keep a broken/unsupported integration or abandon important automations entirely.

Anything else?

Related community issue (LG API block forcing migration): ollo69/ha-smartthinq-sensors#961
Test device: RAC_056905_WW (LG Split Air Conditioner)
The LG ThinQ developer API documentation lists energy and filter-related properties for DEVICE_AIR_CONDITIONER devices. If needed, I can provide a diagnostic dump or API response showing these properties are available for this device model.
Other users migrating from ha-smartthinq-sensors are likely affected by the same gap across multiple device types. This request may benefit a wider audience beyond AC users.

[github-actions[bot]]

🏷️ I've automatically added the integration: lg_thinq label to help categorize this feature request.

[justinmyersm]

Washer and Dryer:

• run_state (Used to determine if in Fresh Care or Wrinkle Care. The official 'Current status' only shows drying, detecting, spinning, running, rinsing, cooling.)
• current_course (Used to determine what course is chosen. The official integration does not offer this at all.)
• power (Used to determine if the washer or dryer are on or not. The official integration does not update this entity. It always shows off.)
• tub_clean (The official integration is constantly reset to 0, making this completely useless.)

LG, please either allow the other integrations to use the API, or offer feature parity, because this is really quite sad.

[tbclark3]

This native integration is practically worthless. My dishwasher sensors all say "unavailable" even when the power is on. None of the washer nor dryer sensors updates at all. The washer and dryer controls work (start,stop, power off) work, but ONLY if remote start has been enabled. Notably, the "remote start" sensor itself doesn't work. I haven't seen any of the refrigerator sensors update yet. The sensors to replace the air and water filters both say "replace" but I'm not sure whether that's because they need to be replaced or whether LG says that all the time, hoping to sell filters.

With the HACS integration, I was able to power on my hot water circulator pump when the dishwasher was running, or when the washer was using a cycle that needed hot water. I could have Alexa make an announcement if somebody held the refrigerator door open too long. I could let my water sensor know that an appliance was running and water was properly being used even though the house was unoccupied. I could have HA send me an alert to clean the dishwasher and washing machine if needed. All gone.

Until today, I was a huge fan of LG appliances. Now I'm looking for alternatives, and I'm quite sure that my next round of appliance purchases will NOT be LG.

[jprates]

Washer and Dryer:

* _run_state_ (Used to determine if in Fresh Care or Wrinkle Care. The official 'Current status' only shows drying, detecting, spinning, running, rinsing, cooling.)

* _current_course_ (Used to determine what course is chosen. The official integration does not offer this at all.)

* _power_ (Used to determine if the washer or dryer are on or not. The official integration does not update this entity. It always shows off.)

* _tub_clean_ (The official integration is constantly reset to 0, making this completely useless.)

LG, please either allow the other integrations to use the API, or offer feature parity, because this is really quite sad.

It's just unusable, this is an example of my dryer, it doesn't even tell you what program it is running, what good is this???

{
"messageId": "fNvdZ1brTn-wWkjhgG1234",
"timestamp": "2026-05-24T11:48:19.675524",
"response": {
"runState": {
"currentState": "COOLING"
},
"remoteControlEnable": {
"remoteControlEnabled": true
},
"timer": {
"remainHour": 0,
"remainMinute": 13,
"relativeHourToStop": 0,
"relativeMinuteToStop": 0,
"totalHour": 0,
"totalMinute": 50
}
}
}

[VHKRMOTL]

I tried a lot of things to eliminate a local problem including making sure the cell phone was on the 2.4G network with the LG devices (in case of mDNS), force stopping the cell phone app and restarting, agreeing to all of the agreements again and even going over to the circuit breaker and cycling the power on each device one at a time. Nope. The app keeps complaining "Cannot connect to the network. Try again later". I am disabling the SmartThinQ LGE Sensors HA integration and seeing if everything is better in the morning. If so, it could mean that running the SmartThinQ Sensors HA integration along side of the LG ThinQ HA integration results in a complete failure of connectivity to the LG server including the cell phone app. If true, either LG is forcing a complete server connectivity disable when detecting the SmartThinQ LGE Sensors HA integration or is killing the connection for a period of time as a result of too many simultaneous requests (throttling). The throttling problem was a major issue with the Chamberlain Garage Door official integration making it useless so much that I ended up throwing out the garage door opener and purchasing an Aladdin garage door opener that works with the Aladdin Connect HA integration which works well. Chamberlain lost me as a customer for the long term as a result of that nightmare. The throttling problem is still a big issue with the Hunter Hydrawise Sprinkler System official HA integration making it somewhat useless. Another reason LG may be developing and forcing a change to an official HA integratioin is that LG would have more control over the data rate and server utilization saving LG some costs with respect to renting Services as a Service (CPU cycles and bandwidth). In addition, the LG HA integration is terrible. Obviously a first draft with over 100 entities missing including absolutely all entities with respect to the stove portion of my range. The oven is still there (barely). There is a bigger issue here and that is the poor performance of many of the cloud serviced HA integrations including official and custom. I have started researching for solutions that do not require cloud integration. So far, the non cloud devices I own are very reliable and the latency is non existent. Corporations need to focus on non-cloud solutions with firmware updates instead of the cloud based roll outs which were always intended to be only for early development. We HA users are willing to sacrifice some coin to eliminate the cloud based frustrations. For me, the key going forward is looking for ESP32 devices and products with ESP32 devices built in allowing for local integration and dumping the cloud.

[tbclark3]

I asked Gemini to analyze the code from the two Thinq integrations to see if the native integration can be improved. Apparently it cannot because LG deliberately withholds API endpoints. The only path forward for those who depend on working entities is for somebody to overcome whatever obstacle LG has thrown in the path of the "private" API. Here is Gemini's response:

You hit the nail on the head: the core of the problem lies in the fact that they are not using the same API. The fundamental architectural difference between how the unofficial HACS integration and the official built-in Home Assistant integration communicate with LG's servers explains why the official one is currently lacking so many features—and why fixing it isn't as simple as just copying code over.

An analysis of how both systems operate highlights these limitations and outlines what to expect moving forward:

1. The HACS Integration (ha-smartthinq-sensors)
   The Method: This custom integration acts as a "reverse-engineered" client. It effectively tricks LG's servers into thinking Home Assistant is the official ThinQ smartphone app. When you provide your username and password, it logs in exactly like the app does.
   The Capability: Because it mimics the app, it has access to the Internal/Private API. This API is incredibly verbose because the smartphone app needs to show you everything: real-time cycle tracking, precise sensor data, exact time remaining, instantaneous power consumption, and fine-tuned configuration toggles.
   The Catch: Because it’s an unofficial backdoor, LG can (and regularly does) change their app's authentication flow, introduce new CAPTCHAs, or block unofficial user-agents entirely. This is why it suddenly broke for you; LG closed the door on this specific method of username/password access.

2. The Official Built-In Integration (lg_thinq)
   The Method: The official integration uses the LG ThinQ Connect API via OAuth or Personal Access Tokens (PAT). This is a public-facing, official cloud endpoint provided by LG specifically for third-party smart home developers (like Home Assistant, Google Home, and Amazon Alexa).
   The Capability: LG deliberately restricts what data is exposed to this public API. Instead of sending raw, granular machine states, it passes generalized device types.
   The Catch: The public "Connect API" is heavily stripped down compared to the internal app API. For example, LG's developer documentation for the public API natively favors historical data aggregated on their cloud servers (like "energy used yesterday") rather than pushing real-time, high-frequency state changes (like "washer is currently spinning"). This is why critical sensors like active running states, countdown timers, and live wattages are missing or fail to update.

[jprates]

I see no reason at all for not supporting all app features in the native API.

It's ridiculous to have to impersonate an app and reverse engineer it in order to get the level of sensors and controls we like.

It's even worse to constantly put road blocks for people using the unofficial path, when what LG should be doing is to catch up to it.

They risk loosing all automation and smart home minded customers with dire moves like these, I for one I'm out if this continues.

C'mon LG, surely you can do better!

[fhroland]

I can confirm this issue for an LG split air conditioner as well.

The initial reason I looked into this was that the same values are missing or unreliable in both places: the LG ThinQ app itself and the Home Assistant LG ThinQ integration. In the LG ThinQ app, the air conditioner is often slow to become reachable, and the “Useful Features” / energy monitoring section frequently times out. In Home Assistant, the entities energy_current, filter_remaining_life and room_temperature are not available or remain unavailable.

This does not look like a simple local Wi-Fi problem. The device remains reachable on the local network while the ThinQ app or Home Assistant cannot retrieve the relevant data. I also captured network traffic at the FRITZ!Repeater the air conditioner is connected to. During ThinQ timeouts, the AC still keeps an active TCP connection to the LG cloud server alive and continues to exchange data. So the device is not offline in the local network sense, and the cloud connection itself does not appear to be completely down.

Device information shown by the LG app:

• Device app: 5028.01
• Modem: 2.6.7_RTOS_3K
• Firmware 1: SAA38690409.00000409.0

What makes this especially relevant is that energy_current worked reliably for this same device with the previous unofficial ha-smartthinq-sensors integration. So the value appears to exist in the device or at least was previously exposed through the older ThinQ path. With the official LG ThinQ integration / ThinQ Connect path, it is no longer available.

I would also like to stress that current power consumption for an air conditioner is not just a nice-to-have value or a gimmick.

For HVAC devices, this is a key value for serious home automation: PV surplus control, dynamic electricity tariffs, battery and load management, energy dashboards, cost-aware operation and grid-friendly behavior all depend on knowing the actual current consumption.

In my case, the lack of an energy_current / current power entity would be a relevant factor against buying additional LG split air conditioners in the future. If this value exists in the device and was previously available through ha-smartthinq-sensors, it would be very unfortunate if it is no longer exposed through the official LG ThinQ integration / ThinQ Connect API.

Reliable access to current power consumption enables more cost-conscious, environmentally responsible and grid-supportive operation. For air conditioners, this is not a fringe feature, but an important requirement for modern home automation.

[VHKRMOTL]

Missing everything (all entities) associated with the Induction Cooktop that is part of the Range LSIL6336FE. Not even a simple "cooking" status sensor.