The current serial protocol is really only designed to for human interaction. It would be good to enhance to these to better support working with the EmonESP.
The current issues I am seeing is rebooting the EmonESP can change the EmonTx settings and likewise if the EmonTx reboots or you use it interactively (via the changes in #74 ) the output of the EmonTx can be parsed as an input string.
What would be nice would be to send (proper) JSON objects both as the EmonTx output and for sending commands to the EmonTx. Alternatively a slightly less drastic approach could be to start output/commands with a specific char and add a checksum at the end, similar to how RAPI works on the OpenEVSE
The current serial protocol is really only designed to for human interaction. It would be good to enhance to these to better support working with the EmonESP.
The current issues I am seeing is rebooting the EmonESP can change the EmonTx settings and likewise if the EmonTx reboots or you use it interactively (via the changes in #74 ) the output of the EmonTx can be parsed as an input string.
What would be nice would be to send (proper) JSON objects both as the EmonTx output and for sending commands to the EmonTx. Alternatively a slightly less drastic approach could be to start output/commands with a specific char and add a checksum at the end, similar to how RAPI works on the OpenEVSE