FIXED: See comments - ERROR: Failed Setup, will retry: ThinQ platform not ready
robkjr opened this issue · comments
Describe the bug
SInce the last HACS update I receive the following with my ThinQ integration. This used to work perfectly but now seems broken.
Expected behavior
HACS inegration worked prior to last update.
Screenshots
Environment details:
- Environment (HASSIO, Raspbian, etc): HASSIO
- Home Assistant version installed: Latest version
- Component version installed: Latest Version
- Last know working version: Previous version.
- LG device type and model with issue: ALL
- LG devices connected (list): 3 window ACs and a dishwasher
Output of HA logs
This seems to be the relevent log information
2024-06-21 08:11:35.461 WARNING (MainThread) [custom_components.smartthinq_sensors] Connection not available. ThinQ platform not ready
Traceback (most recent call last):
File "/config/custom_components/smartthinq_sensors/init.py", line 269, in async_setup_entry
client = await lge_auth.create_client_from_token(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/init.py", line 153, in create_client_from_token
return await ClientAsync.from_token(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 1605, in from_token
await client.refresh()
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 1513, in refresh
self._auth = await self.auth.refresh(True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 989, in refresh
access_token, token_validity = await self._gateway.core.refresh_auth(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 707, in refresh_auth
out = await self._auth_request(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 653, in _auth_request
oauth_url = await self.get_oauth_url()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 436, in get_oauth_url
async with self._get_session().post(
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 1197, in aenter
self._resp = await self._coro
^^^^^^^^^^^^^^^^
Additional context
Add any other context about the problem here.
I'm having the exact same problem.
On a reload of the integration i am getting this error log:
Error setting up entry LGE Devices for smartthinq_sensors
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/init.py", line 286, in async_setup_entry
lge_devices, unsupported_devices, discovered_devices = await lge_devices_setup(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/init.py", line 568, in lge_devices_setup
if not await dev.init_device():
^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/init.py", line 435, in init_device
await self._create_coordinator()
File "/config/custom_components/smartthinq_sensors/init.py", line 458, in _create_coordinator
await coordinator.async_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 288, in async_refresh
await self._async_refresh(log_failures=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 268, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/init.py", line 463, in _async_update
await self._async_state_update()
File "/config/custom_components/smartthinq_sensors/init.py", line 475, in _async_state_update
state = await self._device.poll()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/devices/ac.py", line 914, in poll
res = await self._device_poll(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 689, in _device_poll
snapshot = await self._get_device_snapshot(thinq2_query_device)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 634, in _get_device_snapshot
return await self._mon.refresh(query_device)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 153, in refresh
if refresh_auth := await self._refresh_auth():
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 113, in _refresh_auth
return await self._refresh_client()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 117, in _refresh_client
async with Monitor._client_lock:
File "/usr/local/lib/python3.12/asyncio/locks.py", line 14, in aenter
await self.acquire()
File "/usr/local/lib/python3.12/asyncio/locks.py", line 113, in acquire
await fut
asyncio.exceptions.CancelledError
Ditto. Been this way for quite some time.
I seem to have the same issue as well.
It is not initializing with the message "Failed setup, will retry: Thinq platform not ready"
Well I'm glad to see I'm not the only one. Is there anyone still monitoring this project to see if there's a fix?
Seems like LG has changed or broken something because now my Google Home app won't connect. I've lost all control over my LG devices except for the LG App.
I FIXED THIS!!!!!! It turns out I had South Korea geo-blocked on my firewall. Once unblocked, everything worked.
Mine actually started working yesterday after a complete reboot, i had to shut everything down because my utility meter got replaced.
OMG.
Indeed. 1 month ago I also added geo-blocking to my unifi UDM pro.
I checked if I had South Korea ticked... and it was. Now I unticked it. As a result, this plugin is now again working :D: D whahaha..
SO. Sorry for falsly confirming this bug.
@robkjr thank you for sharing your update
@edterbak It's not actually a bad thing to report this kind of thing. Helps others not chase their tails for weeks trying to figure out why it won't work. AND its a lesson for anyone using integrations and IoT devices that depend on cloud connectivity. Lastly it shows just were our daily data goes when we choose to use such devices.
I'm glad I reported this and I'm glad I was able to find the solution and share it. Frankly I think a note should be added to the installation instructions warning about geoblocking.
@robkjr Yes yes.. you are right. I did not intend to say you did something wrong here by reporting this issue. 😄
Not at all! And you are also right in your conclusion by putting this in here, it can help others. So indeed, thank you for that. In fact, it helped me.
I was only trying to say it was ME who caused this situation on my setup. As usual...
And of course for jumping to the conclusion that something outside of my doing/my setup was responsible. ghehe Sorry for that. 😄
Ugh, turns out my issue is not the same as here.