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

Issue not resolved #104588

Closed
mvroosmalen1970 opened this issue Nov 27, 2023 · 5 comments
Closed

Issue not resolved #104588

mvroosmalen1970 opened this issue Nov 27, 2023 · 5 comments

Comments

@mvroosmalen1970
Copy link

          I've played around with this one a bit. In general, the integration works on my end

image

However, the library the integration uses is old and even archived by the creator:

Ref: https://github.com/richard-better/pushbullet.py

The library was built against an old version of the websocket-client, which had some breaking changes over time. The error reported in this issue is an result of that.

A related issue was originally reported upstream: richard-better/pushbullet.py#178

There are more issues with the library, like these warnings: richard-better/pushbullet.py#180.

Not sure what the right answer to this issue is in this case. The integration can work, but may crash (e.g., when a connection closes for whatever reason). A simple fix is not there. The best fix is replacing the library with another (or a new one).

PS: Rolling back the change made in 2022.12, will not fix/workaround this issue.

../Frenck

Originally posted by @frenck in #83097 (comment)

Do we have a solution with:
https://github.com/benshep/pushbullet.py

The problem is that sometimes this error pops up and stops automations. Was not sure how to test the other branch of Pushbullit

Mark

@home-assistant
Copy link

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

Code owner commands

Code owners of pushbullet 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 pushbullet 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)


pushbullet documentation
pushbullet source
(message by IssueLinks)

@joostlek
Copy link
Member

Please fill in the issue template

@mib1185
Copy link
Contributor

mib1185 commented Nov 27, 2023

The #83097 (comment) is still valid

A simple fix is not there. The best fix is replacing the library with another (or a new one).

@lumper5
Copy link

lumper5 commented Jan 24, 2024

The issue with Pushbullet failing continues. The issue is laid out by @frenck in #83097 (comment) . After each restart Pushbullet integration will work as intended: collect and display pushes and SMSes. After 1-2 hours (or so) the integration stops working until the next system reboot. Repeatedly.

@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 Apr 30, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 30, 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

4 participants