Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Air Conditioner integration with thinq #16

Open
drfant opened this issue Jun 23, 2021 · 14 comments
Open

Air Conditioner integration with thinq #16

drfant opened this issue Jun 23, 2021 · 14 comments

Comments

@drfant
Copy link

drfant commented Jun 23, 2021

I recently found your thingq integration for hubitat and installed it, but there is no device for air conditioner. Are you able to add one?

@dcmeglio
Copy link
Owner

dcmeglio commented Jun 23, 2021 via email

@drfant
Copy link
Author

drfant commented Jun 23, 2021 via email

@MikeBishop
Copy link

Likewise -- we're supposed to pick up our Thinq-connected A/C this afternoon. I'd be happy to help probe the API, etc. with some guidance.

@dcmeglio
Copy link
Owner

dcmeglio commented Jul 7, 2021

I have no way to test since I don't own one, but someone contributed some code that is working for him for AC devices, you can try the code from this branch https://github.com/dcmeglio/hubitat-thinq/tree/ac

Let me know how it works. I'd love to get some feedback before I merge it.

@MikeBishop
Copy link

MikeBishop commented Jul 8, 2021

From an initial poke at it:

  • Installs just fine, detects the A/C as a new device and creates it in Hubitat
  • Created device has properties that match the settings of the device, but don't seem to be updating as I change settings on the physical device. They update once when I click through the setup flow again, but stay static otherwise.
  • Properties aren't mapped as simply as I might hope:
    • Physical screen and app show target temp in Fahrenheit, but driver appears to show them in Celsius
    • OpMode description sounds like it wants things like Cool, Fan, etc. but Hubitat says the command takes a number, and the status shows a number; the link to list possible values doesn't work (private repo?). Link also overflows text box to display it.
    • The names TargetTimeToStart / TargetTimeToStop make it sound like they take wall clock times, but they actually take / expose number of minutes remaining until the action occurs. Thinq app exposes a wall-clock schedule option, but I don't see that reflected here. (I haven't tried enabling it in the app, however.)
    • WindStrength values likewise are at a link I can't access
    • Looking at the code, it appears that "Operation" (a number) reflects the current value of the power switch. Perhaps this should be exposed as an on/off switch state instead?

@dcmeglio
Copy link
Owner

dcmeglio commented Jul 9, 2021

Oh well, it was worth a shot.

@MikeBishop
Copy link

One additional test -- the commands do appear to work.

@dcmeglio
Copy link
Owner

dcmeglio commented Jul 10, 2021 via email

@dshannon73
Copy link

Watching this thread! Any update? Love my Hubitat, and my LG thinq A/C is my last device to get in.

@dcmeglio
Copy link
Owner

dcmeglio commented Sep 11, 2021 via email

@slingr-dev
Copy link

@dcmeglio I was able to import my 3 split A/Cs and they are working great. I've tested a nearly all of functionality using https://github.com/jbilodea/ThinQ_AC/blob/main/Possible_Values.txt as a guide and it works great. IMO, it is fine to merge.

@gleep52
Copy link

gleep52 commented Apr 9, 2022

FYI - Just found out about this project - love it. I added the branch code as a custom app - added the branch code AC drivers to the drivers in hubitat. It detects an "AIR CONDITIONER" and I can add it - but the current states is empty and it does not work with any values or buttons I click. Just curious if the others in this thread could help me get this working... What do I do with the possible_values.txt @slingr-dev - do I have a different issue since the hubitat device screen doesn't populate any current states? Almost feels like it's not actually talking to it properly...

In my hubitat log I do see things like this:

groovy.lang.MissingMethodException: No signature of method: [B.containsKey() is applicable for argument types: (java.lang.String) values: [airState.diagCode]
Possible solutions: contains(java.lang.Object) on line 908 (method checkValue)

@austin-millan
Copy link

FWIW the AC driver works enough for me in my Hubitat environment. Turns on/off and can increase/decrease temperature settings.

Let me know what needs to be tested and I'll report back with issues and logs.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants