Skip to content
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

[BUG] Temperature no longer reported to OctoPrint #20921

Closed
viper93458 opened this issue Jan 29, 2021 · 16 comments · Fixed by #20932 or #20959
Closed

[BUG] Temperature no longer reported to OctoPrint #20921

viper93458 opened this issue Jan 29, 2021 · 16 comments · Fixed by #20932 or #20959

Comments

@viper93458
Copy link

viper93458 commented Jan 29, 2021

Bug Description

Somewhere between yesterday morning and the most recent merges within 24 hours, OctoPrint can no longer read temperatures from my SKR Pro 1.0. It worked when I used Bugfix 2.0 from yesterday morning sometime (-8 PST) but when I used the latest bugfix this morning the issue cropped up. It causes OctoPrint to disconnect due to multiple timeouts.

Configuration Files

Configs.zip

Steps to Reproduce

Use the current bugfix 2.0 and connect to SKR 1.0 with Octoprint. It appears to connect OK but no temperature data is reported. This causes OctoPrint to throw an error about multiple timeout retires exceeded.

Expected behavior:

Temperatures would display

Actual behavior:

No temperature is displayed and the host disconnects.

Additional Information

I will do my best to provide any additional details as needed. I am not a developer so please be gentle. Thanks for your wonderful work and contributions to 3D printing and Open Source!

@lightmaster
Copy link

I was able to roll back to the commit 9e004a9 and it started working again, so it must be something related to PR #20913.

@viper93458
Copy link
Author

@lightmaster Thanks for the advise! I'll see if I can accomplish that. Unless a fix comes forth sooner. :)

@TheLion
Copy link

TheLion commented Jan 29, 2021

I noticed the same thing on my SKR 1.3. I did notice that Octoprint doesn't time out anymore when a print is started.

@GMagician
Copy link
Contributor

I confirm. It seems autotemp report is not working

@GMagician
Copy link
Contributor

GMagician commented Jan 30, 2021

After digging into code it seems that is called the template function (empty) instead of overridden one

@Z18Aplha
Copy link

Is there a quickfix?

@GMagician
Copy link
Contributor

Not yet, I think @thinkyhead should give a look at code to understand why override is not taking place

@benlye
Copy link
Contributor

benlye commented Jan 31, 2021

Is there a quickfix?

This worked for me (one line change in autoreport.h):
#20913 (comment)

@GMagician
Copy link
Contributor

yep that may solve but I think that virtual will add a cost in its call that is not desired

@gimpfenlord
Copy link

Is there a quickfix?

This worked for me (one line change in autoreport.h):
#20913 (comment)

can confirm this worked also for me.

@Z18Aplha
Copy link

Is there a quickfix?

This worked for me (one line change in autoreport.h):
#20913 (comment)

thx! i disabled the autoreport timeout in octoprint instead, works fine too. Octoprint polls Temperature now.

@rhapsodyv rhapsodyv linked a pull request Jan 31, 2021 that will close this issue
@X-Ryl669
Copy link
Contributor

The fix I've proposed is not optimal. We'll find a better solution.

@X-Ryl669
Copy link
Contributor

Can you try #20959, it should solve the building issue and also re-enable auto reporting correctly.

@rhapsodyv rhapsodyv linked a pull request Jan 31, 2021 that will close this issue
@benlye
Copy link
Contributor

benlye commented Feb 1, 2021

Can you try #20959, it should solve the building issue and also re-enable auto reporting correctly.

Working here.

@viper93458
Copy link
Author

Seems to be working for me again so I will close this out. Thanks!

-William

@github-actions
Copy link

github-actions bot commented Apr 3, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
9 participants