We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My refrigerator has separate sensing for freezer door and fridge door (they are shown and logged separately in the THINQ app)
In HA, I only see binary_sensor.lgfridge_door_open
Would it be possible to add support for the freezer door?
I've seen you ask people for the json, but I don't know which log file and what string to search for to get that for you.
Thanks! Just installed a few minutes ago, but looks awesome!
Dave
The text was updated successfully, but these errors were encountered:
I got these from the device page if they are helpful, but it seems they are based on the integration here and not on the device itself?
Still happy to get the correct file if someone can tell me which log file it is in, and what to look for in that log file.
smartthinq_sensors-01JC1B7MG8MX999NJ3D9DCEZ1Y-LGFridge-f12f55e30d54fe1b41ee483755511b80.json WW23120715134910333344.json
Sorry, something went wrong.
There is no such information in the ThinQ API interface, so the developer won't be able to implement such. Please check the official documentation: https://thinq.developer.lge.com/en/cloud/docs/thinq-connect/device-profile/refrigerator/
No branches or pull requests
My refrigerator has separate sensing for freezer door and fridge door (they are shown and logged separately in the THINQ app)
In HA, I only see binary_sensor.lgfridge_door_open
Would it be possible to add support for the freezer door?
I've seen you ask people for the json, but I don't know which log file and what string to search for to get that for you.
Thanks! Just installed a few minutes ago, but looks awesome!
Dave
The text was updated successfully, but these errors were encountered: