mobileraker_companion
mobileraker_companion copied to clipboard
Clon1998
Disable Notifications for Timelapse Improved but still isn't fully working
Building on #73 and #81. As @Johnnytk36 had noted in #81, the notifications are now less when pausing and restarting to take a timelapse photo (not every layer), but are still happening, just intermittently. Often print will go 25-50% without any erroneous pause/start alerts then it will start showing these sometimes every few layers, sometimes for every layer until it completes.
If there's some type of logging you'd like to see or something to test, please let me know.
Hey, I have ran the current version of the companion + timelapse on two of my machines without any problem.
However, I am not using the parking mode. Can you confirm to me that you are using the parking mode?
Feel free to upload the logs. They are either located in /tmp/mobileraker.log or in the same location as all other logs.
I am using the parking mode.
I will enable it on one of my printers to debug it!
Same here. The parking between layers before taking the timelapse is what is triggering those notices.
Logfile of recent print is attached. Timelapse with parking between layers is on. There were only 34 layers and it sent me Pause/Start alerts for 2 layers sometime between 25-50% complete (between layers 8-18).
mobileraker_with_timelapse.log
Any updates on getting this fixed?
I lost track of this issue while working on 2.7.0. I will take a look in the next days to see if I am able to reproduce this issue and hopefully fix it.
In the meantime, can you provide me the version of the companion you are using @Snuffy2 ?
No worries, totally understand and thank you very much for a great tool. I'm running: Mobileraker app: 2.7.0-501 Mobileraker Companion: v0.4.0-58-g828e9a8c
No worries, totally understand and thank you very much for a great tool. I'm running: Mobileraker app: 2.7.0-501 Mobileraker Companion: v0.4.0-58-g828e9a8c
Thanks. The companion is a bit outdated but nothing major that would affect this issue. Also, just was able to reproduce that behavior locally. Just need to identify the root cause for this issue!