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

Bot connection loss #63

Open
Trenar opened this issue Dec 9, 2019 · 4 comments
Open

Bot connection loss #63

Trenar opened this issue Dec 9, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@Trenar
Copy link
Contributor

Trenar commented Dec 9, 2019

Hi all,
I have still another problem with the TeleFrame. It seems that the bot looses the server-connection. The software itself works fine, no freezing system or so, but if I send an image, it will not be displayed until I restart the software (or pi).
Can this be related to wifi power management in the pi or is it a software issue? By thinking over this, I thought about a notification (or a simple symbol like the pause-symbol) when the internet-connection is lost. I'm however not quite sure how to implement this...

@palmerich
Copy link

just checking (noob too) - did you try with a wired connection to narrow it down?

Kind regards,
Andreas

@gegu
Copy link
Collaborator

gegu commented Dec 11, 2019

I tested this by triggering a reboot of my firewall. It then takes some time for the messages to arrive after the connection is reestablished - here about half an hour.

@Trenar
Copy link
Contributor Author

Trenar commented Dec 12, 2019

did you try with a wired connection to narrow it down?

I'm running TeleFrame on a RasPi 3A+, which has no wired connector...

I tested this by triggering a reboot of my firewall. It then takes some time for the messages to arrive after the connection is reestablished - here about half an hour.

For me it seems like the reconnection can't be reestablished at all.. Tried running TeleFrame over night (without toggling monitor or so), sent new photos but they won't get displayed. Sending "Hi" to check if the bot is alive also gives no answer.

@Trenar
Copy link
Contributor Author

Trenar commented Dec 13, 2019

Today I had another issue (which was related to the router failing) but the bot could not reconnect after re-establishing network connection. When the pi was reconnected, I ssh'ed to it and opened the screen session where Teleframe is running in. There was this error message
Failed to fetch updates. Waiting: 1s request to https://api.telegram.org/botTOKEN/getUpdates?offset=569122325&limit=100&timeout=30 failed, reason: read ETIMEDOUT

This looks like it tries to connect a hundred times and then gives up. Do I get this right? How can we handle this? I was thinking of a daily reboot of the pi or restarting teleframe or at least the bot, or a regular check for a valid network connection..

@LukeSkywalker92 LukeSkywalker92 added the bug Something isn't working label Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants