Skip to content
New issue

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

AC: Stops reporting temperature after some time #41

Open
mpapierski opened this issue Jan 20, 2020 · 1 comment
Open

AC: Stops reporting temperature after some time #41

mpapierski opened this issue Jan 20, 2020 · 1 comment

Comments

@mpapierski
Copy link

mpapierski commented Jan 20, 2020

After some time my HASS instance is running, AC controls doesn't update the state anymore (i.e. start AC -> controls are still gray. After restarting HASS I can see the controls changing color after initiating an action). It's interesting because it does send requests and I can still turn on/off the AC unit. There's just no feedback from the server whatsoever. I also noticed the temperature doesn't get reported from the API and it stays constant.

It might be related to an error I noticed today that also killed my HASS instance:

  File "/home/michal/homeassistant/lib/python3.7/site-packages/wideq/ac.py", line 274, in poll
    res = self.mon.poll_json()
  File "/home/michal/homeassistant/lib/python3.7/site-packages/wideq/client.py", line 62, in poll_json
    data = self.poll()
  File "/home/michal/homeassistant/lib/python3.7/site-packages/wideq/client.py", line 44, in poll
    return self.session.monitor_poll(self.device_id, self.work_id)
  File "/home/michal/homeassistant/lib/python3.7/site-packages/wideq/core.py", line 336, in monitor_poll
    res = self.post('rti/rtiResult', {'workList': work_list})['workList']
KeyError: 'workList'

I'm running f6a5d03 and wideq==1.3.0

@sampsyo
Copy link
Owner

sampsyo commented Jan 20, 2020

Hello! I'm afraid there's not much we can help with here, since it sounds like the loss of monitoring is happening on the LG server side. Unless there's anything obvious in the log that would suggest more detail?

For the error, could you report a bug in the WideQ library? It's not clear exactly what the LG servers are doing, but maybe we can handle the failure more gracefully…

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

No branches or pull requests

2 participants