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 integration stopped workin with 2024-1-4 core update #108609

Closed
Quadcrawler opened this issue Jan 21, 2024 · 18 comments
Closed

Yolink integration stopped workin with 2024-1-4 core update #108609

Quadcrawler opened this issue Jan 21, 2024 · 18 comments

Comments

@Quadcrawler
Copy link

The problem

Yolink integration stopped working with 2024-1-4 update.

What version of Home Assistant Core has the issue?

2024-1-4

What was the last working version of Home Assistant Core?

2024-1-3

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Yolink

Link to integration documentation on our website

No response

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

@TheJulianJES
Copy link
Contributor

You really need to provide more information (like logs, diagnostics information), but this is likely a duplicate of:

Possible fix:

@badmadscientist
Copy link

I can confirm that yolink motion is broken in 2024-1-4 and 2024-1-5. I rolled back to 2024-1-3 and it's working again; this is the information gathered before the rollback.

`Logger: yolink.mqtt_client
Source: runner.py:188
First occurred: 5:05:35 PM (3 occurrences)
Last logged: 5:06:05 PM

yolink mqtt client disconnected!`

`Logger: yolink.mqtt_client

Source: runner.py:188

First occurred: 1:00:02 PM (632 occurrences)

Last logged: 3:38:33 PM

yolink mqtt client disconnected!

token expired or invalid, acquire new one.`

Sorry I dont appear to be able to dig into more logs - if they're still there after a rollback, and you give me some guidance, I'll provide whatever logs I can.

@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)

@captshadab
Copy link

Uploading IMG_7192.png…

@derekmborges
Copy link

Similar to @badmadscientist, I also experienced an outage of the integration, and rolling back to 2024.1.3 made it work again.

@yestrdave
Copy link

I can also confirm rolling back to 2024.1.3 allows the integration to work again. .4 and .5 break the integration . Happy to help

@balucanb
Copy link

Just bumping this as I and I assume anyone using YoLink is having the same issue. Has there been any actual verification that this will be fixed in a upcoming update
?

@yestrdave
Copy link

@balucanb all I have seen.
#108518 (comment)

@balucanb
Copy link

Yes I did see that! Personally would like to see something with a little more detail...LOL.

@srivasv
Copy link

srivasv commented Jan 26, 2024

@balucanb I think #108555 is the PR fixing it. However I can't say when it'll be merged and a new version of the core library will be released.

@mattomu22
Copy link

I am using yolink sensor in my Alarmo setup. Can you please expedite the fix ? Thank you so much.

@madbrain76
Copy link

My many Yolink motion sensors are not triggering automations anymore. @matrixd2 What's holding up the commit of the PR ?

@badmadscientist
Copy link

Have you tried rolling back to 2014-1-3. I did, and that works. It'll get your sensors back up and working until the fix hits mainstream.

@madbrain76
Copy link

@badmadscientist thanks. No, I haven't tried. I don't want to lose all the other sensor data - my HAOS install has over 1000 entities - Yolink is far from the only integration I use.

Is it possible to disable the broken built-in Yolink integration and add one with the pending fix in HACS ?

@LindsayReid
Copy link

LindsayReid commented Jan 29, 2024

I think the problem has been caused by an update to Home Assistant and YoLink is not the only addon affected. In the absence of a fix from either HA or Yo, the only solution for many of us is to revert to the 2014-1-3 version. It is a painless process - you only need to restore the "core". We just need to be patient.

@matrixd2
Copy link
Contributor

Please upgrade to version 2024.1.6

@LindsayReid
Copy link

Many thanks - that seems to have sorted the problem.

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests