New FluidNC Release 3.4.8
Bug Fixes
Fixes to Bluetooth/Telnet/Websockets When commands were being sent via Bluetooth (and also telnet websockets), certain operations like homing would discard sent-ahead GCode commands. Those other channels now behave almost identically with regard to send-ahead. In addition, Bluetooth - but not telnet and websocket - now supports advanced line editing like serial. (#482)
Enhancements
Bad gcode debug message Shows line sent when invalid or unsupported gcode is rejected when $Message/Level=Debug
User settable start message New NVS setting $Start/Message to control the startup message. This can be used if your gcode sender requires a specific message like Grbl 1.1g ['$' for help]. See this wiki section on how to use it. (#480)
https://github.com/bdring/FluidNC/wiki/FluidNC-Commands-and-Settings#start_message
Fluidterm edit mode Returns editing mode to the the default (off) when it closes. Furthermore, by sending CTRL-L, a sender can turn off advanced editing mode explicitly.
Refactored control switches They will report and show startup errors a little differently now - the control switch names in the messages are now spelled the same as their configuration items. Also fixes rare ESP32 problem where switches reported incorrectly if read too soon after setup.