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

Pushbullet: Connection to remote host was lost. - goodbye #83097

Closed
Mariusthvdb opened this issue Dec 2, 2022 · 4 comments
Closed

Pushbullet: Connection to remote host was lost. - goodbye #83097

Mariusthvdb opened this issue Dec 2, 2022 · 4 comments

Comments

@Mariusthvdb
Copy link
Contributor

Mariusthvdb commented Dec 2, 2022

The problem

below error in the log, after updating to 2022.12 beta cycle

What version of Home Assistant Core has the issue?

2022.12.0b1

What was the last working version of Home Assistant Core?

2022.11

What type of installation are you running?

Home Assistant OS

Integration causing the issue

pushbullet

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: websocket
Source: /usr/local/lib/python3.10/site-packages/websocket/_logging.py:62 
First occurred: 08:42:25 (2 occurrences) 
Last logged: 08:42:25

Connection to remote host was lost. - goodbye
error from callback <bound method Listener.on_close of <PushBulletNotificationProvider(Thread-3, started daemon 140220581698352)>>: Listener.on_close() takes 2 positional arguments but 4 were given

Additional information

Scherm­afbeelding 2022-12-02 om 09 00 38

@home-assistant
Copy link

home-assistant bot commented Dec 2, 2022

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 Change the title of 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.

(message by CodeOwnersMention)


pushbullet documentation
pushbullet source
(message by IssueLinks)

@frenck frenck changed the title 2022.12 Pushbullet: Connection to remote host was lost. - goodbye Pushbullet: Connection to remote host was lost. - goodbye Dec 2, 2022
@frenck frenck added this to the 2022.12.0 milestone Dec 2, 2022
@frenck
Copy link
Member

frenck commented Dec 6, 2022

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

@oywino
Copy link

oywino commented Dec 9, 2022

I too had this isse @engrbm87 :

error from callback <bound method Listener.on_close of <PushBulletNotificationProvider(Thread-3, started daemon 139800596654896)>>: Listener.on_close() takes 2 positional arguments but 4 were given

Please fix according to suggestions from Frenck.

@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 Mar 16, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Apr 15, 2023
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

3 participants