Status Polling crashes Octoprint when set to 0

[ghost]

May want to have the status polling set to 1 min minimum. Setting to the default of 0 causes Octoprint to get overloaded and crash. Took me a while to figure out what was going on.

[jneilliii]

Thanks. I'll take a look at handling this from the UI side by setting minimums on the inputs and changing the default setting.

[pazu86]

I think this is what has been killing my setup as well - is there a way to manually change that at the moment so I can keep using the plugin?

[jneilliii]

The setting is the Tasmota plugin's settings when you enable the polling status. Just change it from 0 to something else, 1 or greater.

If you can't get OctoPrint to load, then setting that in config.yaml manually would be a way to go, or possibly clearing the plugin's data in the plugin manager using the new eraser button in version 1.4.0 of OctoPrint when you get OctoPrint to load in safe mode.

[pazu86]

ah perfect - thanks, will check this once current print finishes

[pazu86]

So mine was set at 5 (and enabled), I've disabled polling and everything has staying working. So maybe related but not the same issue?

[jneilliii]

That's odd, sounds like a different issue then. Any errors in the logs?

[pazu86]

Not that I can see - when tailing the main log, it just stalls after you try and load the main GUI initially, no errors, service is still there but not responding. Running in safe mode works fine and by process of elimination that’s what I’ve narrowed it down to. I thought it might have been an SD card going so I tried a new card, fresh image and same issue. Are there any other logs I should be looking at? Matt Hodder 0422 610 560

…

________________________________ From: jneilliii <notifications@github.com> Sent: Wednesday, April 15, 2020 10:06:19 PM To: jneilliii/OctoPrint-Tasmota <OctoPrint-Tasmota@noreply.github.com> Cc: pazu86 <matt@mashd.net>; Comment <comment@noreply.github.com> Subject: Re: [jneilliii/OctoPrint-Tasmota] Status Polling crashes Octoprint when set to 0 (#67) That's odd, sounds like a different issue then. Any errors in the logs? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjneilliii%2FOctoPrint-Tasmota%2Fissues%2F67%23issuecomment-613997302&data=02%7C01%7C%7Cdef30683d4dd4a90c42d08d7e1356948%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637225491817013630&sdata=evozK8730imK9YhcAT3iIWC%2BjrHP3HFFMKM9l9o3lPE%3D&reserved=0>, or unsubscribe<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACQJMD5CFKAXBGNBECTQ4HTRMWPLXANCNFSM4LXE4FRQ&data=02%7C01%7C%7Cdef30683d4dd4a90c42d08d7e1356948%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637225491817023623&sdata=zBDhxna%2FY0l9gMVEDmig1a%2BMRrBnPGy16dr%2Frg5fp8s%3D&reserved=0>.

[jneilliii]

Since it's a ui related issue, I'd check the browser's developer console.