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.

Sign up for GitHub

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

Jump to bottom

Handling of disconnected and reconnected device #1

Closed
tomaae opened this issue Apr 19, 2020 · 2 comments
Closed

Handling of disconnected and reconnected device #1

tomaae opened this issue Apr 19, 2020 · 2 comments
Labels
bug Something isn't working.

Comments

@tomaae
Copy link

tomaae commented Apr 19, 2020

Version of the custom_component

Version not found in init.py, commit 45597c6

Configuration

Contains only login and password.

Describe the bug

  1. When device is unreachable, entities wont go to unavailable state.
  2. When device is unreachable, it will spam the log with error message.
  3. After device is reachable again, error message continues and entities are not updated.

To Reproduce
Unplug the device from power and wait

Expected behavior

  1. All entities should change to unavailable state.
  2. Error should appear only once in error log and should not repeat until device responds again.
  3. After device is available again, it should reconnect.

Debug log

2020-04-19 23:46:55 ERROR (SyncWorker_1) [custom_components.jq300] Sorry.. Something went wrong...
@tomaae tomaae added the bug Something isn't working. label Apr 19, 2020
@Limych
Copy link
Owner

Limych commented Dec 4, 2020

Fixed in last version of integration.

@Limych Limych closed this as completed Dec 4, 2020
Limych added a commit that referenced this issue Mar 8, 2021
@Limych
Merge pull request #1 from Limych/dependabot/github_actions/peter-eva…
5af5d09 
…ns/create-pull-request-v3.8.2

Bump peter-evans/create-pull-request from v2 to v3.8.2
@github-actions
Copy link
Contributor

github-actions bot commented Apr 6, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Limych @tomaae