[BUG] Target Nozzle and Bed Temp not showing in console anymore

[Gloom536]

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

When I set a temperature for my nozzle and/or bed on my printer LCD screen, when monitoring console (through octoprint), I see "0" as target temp. I see the current value going up, but the target temp isn't shown

Bug Timeline

It started after I flashed the latest bugfix 2.1.x, Last time I updated was November 26th and it was working fine

Expected behavior

I expect the target temp in console to show what I have set on my printer LCD

Actual behavior

It shows a target temp of 0.

Steps to Reproduce

1. set a bed and/or nozzle temp on your printer from the LCD screen
2. check your console target value
3. notice that it is showing 0, but that the nozzle and/or bed is still heating

Version of Marlin Firmware

Bugfix 2.1.x

Printer model

Creality Ender 5 Plus

Electronics

Stock

LCD/Controller

Stock LCD controller with RELOADED UI

Other add-ons

PT1000 nozzle thermistor, Microswiss hotend

Bed Leveling

UBL Bilinear mesh

Your Slicer

Other (explain below)

Host Software

OctoPrint

Don't forget to include

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

Configuration files.zip

Slicer: Orcaslicer

When setting nozzle/bed temp from console directly (with S104 command by exemple), the target temp will show as expected

[classicrocker883]

it is you Configuration files, I loaded it up in a simulator and automatically get the same error

Error:MAXTEMP triggered, system stopped! Heater_ID: E0 
echo:Err: MAXTEMP

another thing is HEATER_0_MAXTEMP 340 and you don't have UBL just AUTO_BED_LEVELING_BILINEAR

the problem is TEMP_SENSOR_0 1047 Pt1000. changing to default 1 doesn't make the issue

[ellensp]

@classicrocker883 did you get your issues confused?

This issue does not mention MAXTEMP

This issue is about reloaded user interface and how setting the temperature in the UI dos not show up in the M155 Temperature Auto-Report via console

[classicrocker883]

not confused at all. testing this in simulator gives those errors because of PT1000. I suppose then it isn't compatible

[Gloom536]

I don't have a maxtemp error. It's only not showing in auto-report in console when I set my temp from my LCD Screen with reloaded UI. I can't put default temp sensor in my config file as I now have a PT1000 temp sensor... it wouldn't report the good data.

[classicrocker883]

I'm just talking about using the simulator to reproduce the main issue. in doing so I run into another issue - which has to do with using PT100/PT1000 thermistor types - just saying to get around that to be able to use the simulator I just used 1 instead

[Gloom536]

Something must be wrong with the simulator because I can build it and I dont get this error. Or thete is something I dont understand regarding that

…

________________________________ From: Andrew ***@***.***> Sent: Tuesday, January 6, 2026 7:18:46 PM To: MarlinFirmware/Marlin ***@***.***> Cc: Gloom536 ***@***.***>; Author ***@***.***> Subject: Re: [MarlinFirmware/Marlin] [BUG] Target Nozzle and Bed Temp not showing in console anymore (Issue #28205) [https://avatars.githubusercontent.com/u/18502096?s=20&v=4]classicrocker883 left a comment (MarlinFirmware/Marlin#28205)<#28205 (comment)> I'm just talking about using the simulator to reproduce the main issue. in doing so I run into another issue - which has to do with using PT100/PT1000 thermistor types - just saying to get around that to be able to use the simulator I just used 1 instead — Reply to this email directly, view it on GitHub<#28205 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZCKU6IKCWIPVWJQUAABW5T4FRGGNAVCNFSM6AAAAACOFMDJOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJWHAYTKOJYGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

I think it has something to do with the actual extruder. when entering M104 S100 (100 deg for example) it says E1 Heating... so I assume that whatever octoprint is reading is Extruder 0 instead of the one you are using