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

Handle reconnection cleanly #7

Open
qwandor-google opened this issue Sep 20, 2020 · 2 comments · May be fixed by #99
Open

Handle reconnection cleanly #7

qwandor-google opened this issue Sep 20, 2020 · 2 comments · May be fixed by #99
Assignees
@qwandor
Labels
enhancement New feature or request
Projects
Kanban Board

Comments

@qwandor-google
Copy link
Collaborator

If the connection is lost to the MQTT broker, publish-mqtt will currently crash due to send errors. We should figure out a way to handle this more cleanly and keep trying to reconnect instead.
@qwandor-google qwandor-google self-assigned this Sep 20, 2020
@qwandor-google qwandor-google added the enhancement New feature or request label Sep 20, 2020
@alsuren alsuren added this to backlog in Kanban Board Oct 7, 2020
@qwandor qwandor assigned qwandor and unassigned qwandor-google Oct 20, 2020
@qwandor qwandor moved this from backlog to in progress in Kanban Board Dec 16, 2020
@qwandor
Copy link
Collaborator

qwandor commented Dec 16, 2020

This is also an issue for homie-influx, potentially more so as it is handling multiple connections.

This was referenced Dec 16, 2020
Merged
Draft
@qwandor
Copy link
Collaborator

qwandor commented Jan 23, 2021

This is one way mijia-homie can die:

Jan 23 01:16:07 cottagepi mijia-homie[8762]: Trying to connect to Downstairs toilet from status: Unknown
Jan 23 01:17:05 cottagepi mijia-homie[8762]: Error: Mqtt state: Last pingreq isn't acked
Jan 23 01:17:05 cottagepi mijia-homie[8762]: Caused by:
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    0: Mqtt state: Last pingreq isn't acked
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    1: Last pingreq isn't acked
Jan 23 01:17:05 cottagepi mijia-homie[8762]: Stack backtrace:
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    0: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    1: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    2: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    3: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    4: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    5: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    6: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    7: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    8: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:    9: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:   10: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:   11: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:   12: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:   13: <unknown>
Jan 23 01:17:05 cottagepi mijia-homie[8762]:   14: __libc_start_main
Jan 23 01:17:05 cottagepi systemd[1]: mijia-homie.service: Main process exited, code=exited, status=1/FAILURE
Jan 23 01:17:05 cottagepi systemd[1]: mijia-homie.service: Failed with result 'exit-code'.

@alsuren alsuren moved this from in progress to ready for dev in Kanban Board Apr 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qwandor qwandor

Labels
enhancement New feature or request
Projects
Kanban Board
  
ready for dev
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make mijia-homie automatically reconnect to MQTT broker after network errors alsuren/mijia-homie
2 participants
@qwandor @qwandor-google