search

sman591 / homebridge-lg-thinq-ac

Homebridge plugin for LG ThinQ-enabled portable air conditioner
Apache License 2.0
53 stars 16 forks source link

Model number not accurate, and certain modes not available? #35

Open DataFran opened 4 years ago

DataFran commented 4 years ago

Hello, When setting this up the plugin auto-assigned the model number, but it doesn't seem to be accurate, and therefore doesn't list all the modes available on the device. I have two LW8017ERSMs, but Homebridge lists them as "WIN_056905_WW" and doesn't offer the Fan or Energy Saver option. Is this something I can edit somehow?

sman591 commented 4 years ago

This mismatch in model number is unfortunately correct - the LG API doesn't provide us the public/marketing-based model number but rather an internal model number.

Energy saver isn't supported yet given HomeKit doesn't have native support for it. For fan, if you change the mode to "auto" on the Home app, does the unit switch to fan mode?

DataFran commented 4 years ago

Ah ha! Yes it does. Auto = Fan, Cool = Cool, Heat = Dry, and Off = Off. Odd that Homekit would leave out Fan and Energy Saver modes, seems like pretty common stuff, but I'm new to all this so what do I know.

I am still getting the below in the log every refresh. Don't know if that's related to modes existing but not having Homekit support:

[LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8

Thanks for your help!

Phoendor commented 4 years ago

Ah ha! Yes it does. Auto = Fan, Cool = Cool, Heat = Dry, and Off = Off. Odd that Homekit would leave out Fan and Energy Saver modes, seems like pretty common stuff, but I'm new to all this so what do I know.

I am still getting the below in the log every refresh. Don't know if that's related to modes existing but not having Homekit support:

[LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8

Thanks for your help!

Hi! What mode is selected in ThinQ app when you see this line in log?

DataFran commented 4 years ago

Looks like it happens when it's set to "Energy Saver" either manually, or by the ThinQ app. So the plugin doesn't know what to do with that setting I guess. Is there a way to silence the talk-back, or reassure the plugin that this is a valid setting?

Phoendor commented 4 years ago

Does every mode (heat cool etc) have energy saving mode? Do heat + energy / cool + energy / fan + energy provide same unsupported API values?

DataFran commented 4 years ago

There’s only one energy saver mode. The full list of modes is: Cool Energy Saver Fan Dry

Energy Saver is also an AC mode, but fully distinct on both the front of the device itself, and in the ThinQ app. It’s not an additional option you can turn on with the other modes.

Does that help/answer your question?

sman591 commented 4 years ago

Awesome, makes sense. I'll see if we can add this

TWDickson commented 4 years ago

Also chiming in and I'm getting the same error on my unit, model number LW1517IVSM. Everything seems to be as @DataFran provided. It seems that since Homekit only provides: Auto Heat Cool Off

It would be nice to remap these to something different, i.e. auto would be energy saver mode (8). My AC also doesn't support temperature ranges either.

Edit: Mine is listed as (WIN_056905_WW) in homekit