-
Notifications
You must be signed in to change notification settings - Fork 12
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
Docker companion on separate host - no notifications after klipper host boot #78
Comments
Hey, At the very bottom of the log, I can see that notifications are issued. |
Just letting you know, I am having the same issue. I have had to restart the docker container for mobileraker on my Synology NAS after restarting my sonic pad, or i don't get the push notifications. |
Ill try to debug the container in my machine later this week. |
|
@Clon1998 I'll try and do some testing with this for you. I haven't noticed that. Off the top of my head, as soon as i restart the sonic pad, mobileraker doesn't send any push notifications, till i restart the container. |
Hello,
I am running mobileraker_companion in docker on a separate host. Klipper host is a separate machine that I turn off during night time. I noticed that I will receive no notifications from companion until I restart the container, however in the logs I can see it's picking up the printer once klipper host is started.
Here's the last log from the container, as expected there's a good number of failed to connect errors ending with the companion reaching out to klipper host once I powered it on. I've done several prints since then and got 0 notifications. Then I restarted container and as visible in the logs I am getting notifications again.
mobileraker_logs.txt
The text was updated successfully, but these errors were encountered: