Frédéric

I’m not sure this is the only event with such problem . And it’s not easy to test all cases: direct request to octoprint, Nginx, Apache, Haproxy, etc. It could...

After 4 days of test, I have no more infinite loops. The problem was with empty responses like 502 and, also, with the Wifi driver. On the MKR 1010, perhaps...

I tested POST commands with octoPrintPrintHeadRelativeJog() and octoPrintPrinterCommand(). It also included minor debugging and optimisations after several tests.

I changed the delay during timeout, as the wifi driver crashs after a while.

This PR adds a part of the issue #30

This PR adds chamber features to get and set temperatures. I can't really test cause I don't have a printer chamber at home. It also adds printerBedTempHistoryTarget to struct printerBedCall.

I have less time now but, please, play theses features and tell me :-)

Flows seems to be kickoff with async but not crews. So, I guess, KeyboardInterrupt is not properly captured I found this in python doc. https://docs.python.org/3.13/library/asyncio-runner.html#handling-keyboard-interruption

I’m sorry, I don’t have a fix. Werk you able to reproduce the issue ?

An easy fix is : - go to root: su - - cd /home/pi/.pwn - source bin/activate - pip install scipy numpy matplotlib --upgrade