Andrey
Andrey
Hm, I've tried to set version to 1.4.0 in manifest.json and also to remove my APIError handler and today it works. I have this integration installed through HACS.
@mihail4anov if you have installed it through HACS, all you need is to update to the latest component version and just restart HA. No need to install anything on the...
@mihail4anov you don't need to do that, I just made a hack for my installation and removed it later. Did you installed the component from HACS? Have you tried to...
@mihail4anov Last error code you've shown says that your device is not connected, maybe it has lost WiFi connection. Try to restart it and check if it is accessible through...
@sampsyo I got error 0111 after HA reboot again and component is not working anymore. As far as i can see, it's not handled within wideq anywhere: https://github.com/sampsyo/wideq/blob/master/wideq/core.py#L172-L177 Traceback: ```...
As a temporary workaround you may try this. Open climate.py and find the function called `check_power` (aprox. line 244). After the following lines: ``` except wideq.InvalidRequestError: LOGGER.info('Power consumption not available.')...
Oh, speaking of that trace with _something about fans_ ``` Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 186, in _async_setup_platform await asyncio.gather(*pending) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 292, in async_add_entities await...
Hey folks. Did you tried official LG app when you got this message? In my case seems like official app can't connect to AC too, so it might be because...
Same here, just updated my two monitors, and both doesn't report anything to HA now.
Just faced the exact problem. Ksvc never becomes ready, because of "waiting for loadbalancer". Disabling proxy_protocol resolves the issue, but reveal other problems with client identification.