I keep getting CORRUPTED FRAME errors in my log when trying to send commands such as mos config-get from a Raspberry Pi over a custom cable. It’s worked find on other devices of the same hardware so I’m assuming it’s noise on the cable. Is there a way to slow down the baud rate for mos commands to improve things?
mgos-sgp30, the init method gets translated into
txn.hd.rx_len = 0; txn.hd.rx_data = NULL;
data.at(index)will return a numeric byte value but
data.slice(index, index+1)will return a string...
Have you already test EAP-TLS with the new mos version?
tbh, no, it's been a while since i've tested EAP. but i will.
Ok rojer, just found the error, by the past when mos read the certificate file in pem format the trailling 0 should be integrated to the buffer, but with the new one it seems that this 0 is not part of the buffer, or esp implementation changed...
Anyway to make EAP-TLS work without brick the device you need to add a trailling 0 at the end of each pem files, just checked now the error disappear and the device connected correctly to my radius server.