WebSerial | Remote Serial monitor for ESP8266 & ESP32

This isn't a tested answer as I have no way of reading a serial port with actual data coming in.

However, looking at the characters that have been read correctly and those that haven't there is consistency.

Those that have been read correctly will not have a parity bit set (should there be one) and those that have been read incorrectly will have a parity bit set.

for example: lowercase g in ASCII is octal 147 - 01100111 in binary - an odd number of bits set uppercase S in ASCII is octal 123 - 01010011 in binary - an even number of bits set

The suspicion is therefore that different character codings are being used, particularly as there appears to be a merging of the T and , to give a character.

So, is parity being set on the serial device now but not being taken into account when reading the characters for example? Is some sixteen bit encoding being looked for or...

Sorry I cannot investigate further. At least try reading with the parity bit set rather than not as a starter.

In my case, this problem was solved by adding my user to the "dialout" group with sudo adduser [username] dialout (take into account that the machine should be restarted after that) and then it worked!.