Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
While d eveloping TDM, I've been trying to find out if entire device management could be done without using WebUI; the simple answer is no, because of console. While a lot of data can be requested via MQTT, some debugging information is available only there. Hence my suggestion, to add the possibility to forward console to MQTT.
Why? Because for a tool that's not meant to be used as a main interface to Tasmota, webserver takes up a reasonably amount of resources.
As it will naturally increase MQTT chatter a lot, I have a few thoughts how to avoid it.
This is just a concept, as I'm not proficient enough (or at all?) in C++ to even attempt making a draft or a PR, but @shantur said that this should be easy to implement.
Another option (which @jziolkowski won't like it) can be Websockets. That could give Tasmota another way to communicate to. In my opinion, one good thing about using Websocket for configuration management is that Websockets can be used without any MQTT broker setup.