esphome / esphome/feature-requests

FluidNC WiFi communication (telnet or WebSockets client)

Open
#1,803 0 comments 0 reactions 0 assignees View on GitHub
Type: Communication Channel
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

I want to communicate with [FluidNC](https://github.com/bdring/FluidNC) over WiFi (I want to use the web interface so I don't want to go with BLE). That requires a telnet or WebSockets client but I can't find one.

It would be also amazing to have FluidNC sensors/outputs (like coordinates, alarms, coolant input, e-stop, door, etc.) but I don't ask for that much

**Please describe your use case for this integration and alternatives you've tried:**

I've created a simple pendant (aka remote control) that has some buttons, a rotary encoder and a screen and I want to see all the stats and be able to do actions (mainly send G-Code)

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the FluidNC communication options named in the request—telnet and WebSockets—and how the proposed pendant would send G-Code and receive status. Define the supported connection path and the minimum completed behavior before investigating whether sensor and output reporting is included.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.