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

Yolink stopped updating sensors in HA. Yolink App still works #108518

Closed
StephenShamakian opened this issue Jan 20, 2024 · 19 comments
Closed

Yolink stopped updating sensors in HA. Yolink App still works #108518

StephenShamakian opened this issue Jan 20, 2024 · 19 comments

Comments

@StephenShamakian
Copy link

The problem

Core: 2024.1.3
Supervisor: N/A
Operating System: Container
Frontend: 20240104.0
Unraid Container
https://www.home-assistant.io/integrations/yolink/

My Yolink devices are communicating fine to the Yolink app but home assistant is not reporting their statuses. I deleted the integration and re-created it with the same errors after re-creating it.

HA Log File:
2024-01-20 11:38:34.316 ERROR (MainThread) [yolink.mqtt_client] yolink mqtt client disconnected!

2024-01-20 11:38:39.473 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:39.632 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:39.790 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:39.948 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.105 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.263 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.421 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.578 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.739 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable
2024-01-20 11:38:40.757 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 10.10.9.5 data: Unable to connect to the device: 10.10.9.5:9999:
2024-01-20 11:38:40.896 ERROR (MainThread) [yolink.mqtt_client] unexcept exception:
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable

What version of Home Assistant Core has the issue?

2024.1.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Yolink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/yolink

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @matrixd2, mind taking a look at this issue as it has been labeled with an integration (yolink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of yolink can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign yolink Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


yolink documentation
yolink source
(message by IssueLinks)

@StephenShamakian
Copy link
Author

FWIW I went back to HA Core v2024.1.2 and that still doesn't work. I don't think this is a HA related issue. It seems like maybe the MQTT server address for yolink may have changed based on the error messages? Is there anyway to enable more verbose debugging logs?

@GregRocket
Copy link

Same Issue for me too after updating to 204.1.4 from core-2024.1.3

Core 2024.1.4
Installation Type Home Assistant OS
Supervisor 2023.12.1
Operating System 11.4
Frontend 20240104.0
Raspberry Pi 4
https://www.home-assistant.io/integrations/yolink/

HA Log File:
yolink mqtt client disconnected!
7:03:44 AM – (ERROR) runner.py - message first occurred at 6:49:56 AM and shows up 56 times
unexcept exception:
7:00:04 AM – (ERROR) /usr/local/lib/python3.11/site-packages/yolink/mqtt_client.py - message first occurred at 6:49:47 AM and shows up 30 times

@meeowgler
Copy link

meeowgler commented Jan 20, 2024

FYI - The homebridge yolink by @dkerr64 plugin still works if you need an immediate workaround.

@StephenShamakian
Copy link
Author

@GregRocket Strange, v2024.1.4, v2023.1.3 and v2024.1.2 all don't work with the same MQTT error for me. Back-porting HA doesn't work for me. Granted I'm running HA via a container not on a Pi device. But I wouldn't think that would matter?

@GregRocket
Copy link

@StephenShamakian I just updated to 2024.1.5 still not working.

@DaveR2419
Copy link

I'm having same issue with 2024.1.5 update. I can restore 1.4 and then working again.

@ottrwat
Copy link

ottrwat commented Jan 21, 2024

Same here. Doesn't work with 2024.1.5. Devices show up but not responsive. Seems like if I reload the yolink intergration it works for a little bit but then goes back to unresponsive. All works fine if restore back to 1.4.

Yolink app works fine.

@rgnet5
Copy link

rgnet5 commented Jan 22, 2024

It looks like if you reload the integration, it will pick up the current state, but it does not catch any changes. When I open my garage door, it shows up as "closed" in HA. When I refresh, it shows "Open". When I closed the door, it still shows "Open" until I refresh the integration. So HA picks up the static state on refresh, but does not pickup any state changes on it's own. Yolink app works fine.

@bfish2
Copy link

bfish2 commented Jan 22, 2024

Same issue... following.

@timothybuchanan
Copy link

My Yolink temperature sensors are working but motion sensors are not. Running core 2024.1.5, supervisor 23.12.1.

@espeir
Copy link

espeir commented Jan 22, 2024

Having the same issue. Running core 2024.1.5. Supervisor 2023.12.1.

@mikedrews
Copy link

Following as I have the same issue. Core 2024.1.5

Logger: yolink.mqtt_client
Source: /usr/local/lib/python3.11/site-packages/yolink/mqtt_client.py:71
First occurred: January 21, 2024 at 12:08:47 PM (2930 occurrences)
Last logged: 1:00:59 PM

unexcept exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/yolink/mqtt_client.py", line 59, in _listen
async with client.messages() as messages:
^^^^^^^^^^^^^^^^^
TypeError: 'async_generator' object is not callable

@mindbenderz
Copy link

I ran a wireshark on HA and found an error with yolink mqtt integration while trying to connect up to api.yosmart.com:8003...
Header Flags: 0x20, Message Type: Connect Ack
Acknowledge Flags: 0x00
Return Code: Connection Refused: identifier rejected (2)

@captshadab
Copy link

Hello

Will be fixed in next update of home assistant
Uploading IMG_7192.png…

@matrixd2
Copy link
Contributor

Please upgrade to version 2024.1.6

@DaveR2419
Copy link

DaveR2419 commented Jan 31, 2024 via email

@timothybuchanan
Copy link

Yes, thank you for your work on this.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests