LG Range target temperature entities not working

[Waank1]

LG Stove model #LTE4815ST Integration lists 12 entities:

OVEN sensor.oven SmartThinQ LGE Sensors Kitchen — OVEN Cooktop center state sensor.oven_cooktop_center_state SmartThinQ LGE Sensors Kitchen — OVEN Cooktop left front state sensor.oven_cooktop_left_front_state SmartThinQ LGE Sensors Kitchen — OVEN Cooktop left rear state sensor.oven_cooktop_left_rear_state SmartThinQ LGE Sensors Kitchen — OVEN Cooktop right front state sensor.oven_cooktop_right_front_state SmartThinQ LGE Sensors Kitchen — OVEN Cooktop right rear state sensor.oven_cooktop_right_rear_state SmartThinQ LGE Sensors Kitchen — OVEN Cooktop state binary_sensor.oven_cooktop_state SmartThinQ LGE Sensors Kitchen — OVEN Oven lower state sensor.oven_oven_lower_state SmartThinQ LGE Sensors Kitchen — OVEN Oven lower target temperature sensor.oven_oven_lower_target_temperature SmartThinQ LGE Sensors Kitchen — OVEN Oven state binary_sensor.oven_oven_state SmartThinQ LGE Sensors Kitchen — OVEN Oven upper state sensor.oven_oven_upper_state SmartThinQ LGE Sensors Kitchen — OVEN Oven upper target temperature sensor.oven_oven_upper_target_temperature SmartThinQ LGE Sensors Kitchen — A clear and concise description of what the bug is. If possible attach the JSON info file for your devices: UNK All but 2 entities report as expected. Non working are: Oven upper target temperature Oven lower target temperature They both show: unknown all the time

Expected behavior Once oven is on and a temperature is set, I would expect entities to have some value:

Screenshots If applicable, add screenshots to help explain your problem.

Environment details:

• Environment (HASSIO, Raspbian, etc): HASSIO
• Home Assistant version installed:
  Core: 2023.12.3 Supervisor: 2023.11.6 Operating System: 11.2 Frontend: 20231208.2
• Component version installed:
• Last know working version: As far as I know they have never worked
• LG device type and model with issue: LG Stove model #LTE4815ST
• LG devices connected (list): LG Stove model #LTE4815ST and Refrigerator LMXS30796*

Output of HA logs Paste the relevent (SP) output of the HA log here. N/A

Software version
Device App: 35.58
Modem: QC Modem 1.2.80
Firmware: SAA39155802.00003483.0

**Additional context**
Add any other context about the problem here.
I Like the integration, not a deal breaker that they don't work, just would be nice.

[thomaskistler]

FWIW, my target temperature does work:

[Waank1]

Thanks, thomaskistler, Mine is a dual oven and the only 2 entities that don't work are the target temps.

I not sure if anyone is paying much attention to this custom integration any more.

[ollo69]

Please attach integration diagnostics (while device is on and target temperature set) so that I can analyze your payload.

[ollo69]

@Waank1 ,

please try is last release fix the issue.

[Waank1]

I tried it and it is working perfectly now. Thank you!

[ollo69]

Good, I close this.

[Waank1]

I spoke too soon. Now the current temperature is not working....... But the target temperature is. Actually they are both all over the place, current and target for upper and lower are now very inconsistent.

[ollo69]

I need more information. Please attach new diagnostic with the device turned on so that I can analyze returned data. If possible also collect some logs with debug level.

[ollo69]

I need diagnostics generated when target temperature is set, I think that the issue is related to unit of measure, but I need to see the values returned to understand where is the error.

[ollo69]

@Waank1,

you attach hacs diagnostics, I need integration diagnostiscs.

[ollo69]

Unfortunately this doesn't seems to be an issue related to the integration but the way the data is provided. When target temperature value is set, the current temperature returned is 0, at least in the payload present in the diagnostics provided, and for this reason is set to None (unknown in UI) My question is: what are the information provided by LG app?

[Waank1]

It has been many months since I have looked at the LG app. I just checked, it only provides the temperature (which is very slow to update) and the status ie. preheating, baking, broiling etc.

[ollo69]

When you say temperature you mean target or current? Could you extract a diagnostic when temperature is shown in LG app and give me detail (may be a picture) of information shown in the app at that moment?

[ollo69]

Tis is quite complex situation. Your app is saying 72, but in the payload I just see the target temperature = 200. It is also providing a value of 77 for the Lower Cook temp, just wondering if this value could be inverted. As first option you could try to collect some information in different condition (up on and low off, up off and low on, both on) and send diagnostic in every situation so that I can try to understand if there is some logics....

[thomaskistler]

It generally works for me. However, the resolution is quite poor and there doesn't seem to be any reports during pre-heating:

[image: Screenshot 2024-02-26 at 7.00.27 AM.png]

On Mon, Feb 26, 2024 at 1:04 AM ollo69 @.***> wrote:

Tis is quite complex situation. Your app is saying 72, but in the payload I just see the target temperature = 200. It is also providing a value of 77 for the Lower Cook temp, just wondering if this value could be inverted. As first option you could try to collect some information in different condition (up on and low off, up off and low on, both on) and send diagnostic in every situation so that I can try to understand if there is some logics....

— Reply to this email directly, view it on GitHub https://github.com/ollo69/ha-smartthinq-sensors/issues/647#issuecomment-1963624851, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEENVYJJHQYNCR4WZVESILYVRF3TAVCNFSM6AAAAABAY2P376VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTGYZDIOBVGE . You are receiving this because you commented.Message ID: @.***>

[ollo69]

@Waank1,

the situation is always the same, I see all values that do not match with value you provide, most of them set to 0. Please enable debug log and send me log file, the last thing I can do is check the raw data to verify if it is properly converted to status data. I would be surprised if something is wrong because should fail most of devices, but everything is possible...

[github-actions[bot]]

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.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.