Let me correct you here - your printer vendor broken the firmware or rather the M105 output format in the new release. I suggest to scream a bit at your printer vendor, they can't just start changing output formats if they feel like it, they have to adhere to the established protocol if they expect interoperability with existing solutions on the market.
First of all, I think it seems like Octoprint is working correctly, and the Creality 3D CR-X is breaking the protocol.
When I compare Creality 3D's firmware to the original Marlin firmware, it seems like they have changed a lot in the Marlin 1.1.0 code, and it seems like line number 7445 in marlin_main.cpp should be deleted:
(sourcecode available here: https://www.creality3donline.com/blog/download-b0034.html)
That being said, and due to the fact that I am a CR-X owner, I need a solution while Creality 3D and Octoprint fights about the protocol, and I'm not very keen to change firmware on my newly bought printer at the moment.
My very dirty solution is to add the following 4 lines between the "##~~ busy protocol handling" and "##~~ debugging output handling" sections of the /home/pi/oprint/lib/python2.7/site-packages/octoprint/util/comm.py on my octopi (line number 1559).
## Fix Creality 3D CR-X breaking with standards
findBadTempReply = re.search(r"^((ok)*)\ ==(T|B):([0-9\.]*)\ /([0-9\.]*)\ .*$",line)
line = line.replace(" =="," ")
I'm no python programmer, and might just have broken every rule in all the good the books, but hey - now I got a temperature readig.
(The fix will most likely be overwritten whenever I update Octoprint)
Maybe someone could translate this to a plugin called "Fix very broken CR-X firmware replies" or something like that, so we can move on with our lives while Creality fixes their broken firmware?
@rapotjau Think of 3D printing as the wild, wild west. Foosel is the local sheriff in town and the printer manufacturer is like that traveling guy who sells snake oil remedies and you bought one of them.
Sometimes this isn't easy. I get that you'd like to not re-flash your new printer's firmware but some of these vendors truly don't know what they're doing. I contracted for a big manufacturer here in San Diego and their understanding of the software would just make you shake your head. How could they be so utterly clueless? And yet, few of these manufacturers know the software side of the business like they (hopefully) do understand the hardware.
Fast-forward a year from now and you'll probably agree with me. It wouldn't hurt to learn how to re-flash your printer's firmware. Learn how to do it and you can re-flash it back to Creality's compiled firmware if you didn't like the experience.
Use ssh firstname.lastname@example.org or the equivalent command in PuTTY to remote into your Raspberry Pi computer (noting that the default password is "raspberry").
Run the command touch /home/pi/.octoprint/plugins/CrealityTemperature.py
Run the command nano /home/pi/.octoprint/plugins/CrealityTemperature.py
Copy and paste the content as provided above for the Python code, making sure to add an extra Enter (hard return) at the end of the file. Press Ctl-X and follow the prompts to save the content to the same file.
Run sudo reboot to reboot your Raspberry Pi computer.
When OctoPrint is again available, give it a test to see if this fixes the temperature.