Octofarm: Websocket terminated. Ping/ Pong check failed.

What version are you on please?

Could you also attach the latest state log where this is happening as well please?

This is on 1.1.5.5 running on windows 10.

log copy.txt

Hi, here the same issue.

OctoFarm Version 1.1.5.5
Running on Ubuntu 20.04 x64
Raspberry PI 3B+
nodejs v13.14.0
mongo v3.6.8
npm v6.14.4
OctoPrint 1.4.0 on Raspberry PI 3B+

OctoFarm-State.log

Greetings, take care.

Hi,

Octofarm 1.1.5.4
Running on Windows 10
Mix of RPI 3s and 4s
Octoprint 1.4.0

Having same issue... printers will sporadically show as offline and forcing a re-sync corrects it. Changing timeouts does not seem to make a difference.

Just upgraded to 1.1.5.5 and still having same issue

I have just pushed a change to development if anyone wants to see if it's fixed it.

I would be happy to test

I will jump on the dev branch and let you know

Installed 1.1.5.6 and started server and it pulled all 4 of my printers status immediately and showed as online. Can say for sure yet but so far it looks better.

Just noticed 2 things not working... and I understand this is a dev build, but right now when I go into a printer to control/start a print, T0 temp registers and shows set and actual temps, Bed temp, however, does not show set or actual temp. I also noticed that even though I have filament assigned to a printer, it shows that filament assigned in the list view but when I open a particular printer to start a print, the filament drop down does not show the assigned filament and is not populated with any of the filaments in the database. So far, however, I have not lost connection to any of the printers sporadically.

There's major development on this version it was just to test the connections. Good to know. Id go back to the previous version until I can finish the changes for this version.

To fix the 1.1.5.5 version it's literally one single line change if you want? Then the older version keeps working till this is ready.

Runner/stage.js on line 55.
if (client.ws.isAlive === false) return client.ws.instance.close();
Should become:
if (client.ws.isAlive === false) return client.ws.instance.terminate();

I have run overnight and both are still showing online.

Looks like original issue is confirmed fixed in dev.

Sweet. there's instructions above to apply the fix to the old version as dev is currently broken with the tool0 changes that are coming to support multiple tools/chambers. When those are complete I will push all to master