Communication error - OpiTemp: can't determine the temperature, are you sure you're using Armbian?

[DennisRN]

What is the problem?

I am getting a Communication error with the text:
There was a communication error while talking to your printer. Please consult the terminal output and octoprint.log for details. Error: Too many consecutive timeouts, printer still connected and alive?

What did you already try to solve it?

I have tried to restart printer, RasberryPi and router

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No, i am getting the same error

Systeminfo Bundle

octoprint-systeminfo-20220222235516.zip (136.0 KB)

WRITE HERE

Creality CR10v3 with BL-Touch
Raspberry Pi 4 Model B Rev 1.4
Octoprint 1.7.3
Phyton 3.7.3
OctoPi 0.18.0

WRITE HERE

[Ewald_Ikemann]

Hello @DennisRN !

OpiTemp is if you are using an OrangePi.

But you are using Raspberry Pi.

|  plugins:
|    pi_support:
|      model: Raspberry Pi 4 Model B Rev 1.4
|      octopi_version: 0.18.0
|      throttle_state: '0x0'

So it will not work.

If you want the SoC Temp in the navbar you may use

Top Temp

or

Navbar Temp

[DennisRN]

Thanks for a quick answer.

I have - without being aware of it - OpiTemp and TopTemp running.
I have now disabled OpiTemp and will see if that does the trick.

[DennisRN]

I tried to disable the plugin (Opitemp), and it worked fine for about 2 hours.
Then the printer stopped with the same error.
I will try one more time but now i have uninstalled the plugin and cleaned all files of any rest from the plugin.

[DennisRN]

Well, that was a quick one...
20 min into the print and i get the same error.
I am attaching the SystemInfo file one more time since the plugin is removed so that can not be the error.
octoprint-systeminfo-20220223221144.zip (131.1 KB)

[Ewald_Ikemann]

@DennisRN

same error.

Can't be, because the plugin is deleted.

It seems you are now in trouble with Octoeverywhere.

[DennisRN]

Does that mean that i have to reinstall my RaspberryPi?

[DennisRN]

In trouble with Octoeverywhere...?
How can that be? I am accessing my octoprint through a local adresse
inside my local net. I get this error without using Octoeverywhere.

[Ewald_Ikemann]

2022-02-23 22:09:09,731 - octoprint.plugins.octoeverywhere - ERROR - Failed to find time estimate from OctoPrint. int() argument must be a string, a bytes-like object or a number, not 'NoneType'
2022-02-23 22:09:09,732 - octoprint.plugins.octoeverywhere - ERROR - Failed to find time estimate from OctoPrint. int() argument must be a string, a bytes-like object or a number, not 'NoneType'

[DennisRN]

@Ewald_Ikemann

octoeverywhere

I tried to uninstall the octoeverywhere plugin and that helped. Now i can print but not see the printer remotely.
I will try to install octoeverywhere again and see if the error comes again.

[DennisRN]

Uninstallig, cleaning and then installin Octoeverywhere seams to have done the trick!
But why Octoeverywhere did generate an error is still a mystery.
Many thanks for the help - i am happy and printing again...

[Ewald_Ikemann]

Maybe the other plugin broke something because it was meant to run on an Orange Pi and not Raspberry Pi