FluidNC LED Musings

Right, I looked at that thread (and linked it in my original post). I’m just looking to do that automatically based on the status string. So, no button presses, no custom gcode.

That’s good to know. I’m not using my FluidDial or a spindle so I have the expansion socket open. I’ve been following some threads where these concerns have been discussed, but they’re way over my head.

Based on my websocket experience, I’m not sure how well that will go since I’ll already be using a websocket connection. I’m specifically using the WebUI v3 websocket port (82 vs 81) so only one connection is active. I may still be able to use the standard port for this purpose which doesn’t auto-close connections when a new one is made. From the FluidNC side, it needs nothing more than the status strings so it may be a non-issue.