John
John
I always use LIbreoffice, works fine
just try with a higher latency for a start
did you adjiust the poti well enough?
lets have a look at some raw logging. whats the environment exactly? i.e. adapter, USB-serial bridge, host, ebus devices
as you can see in the log, when ebusd sends 0x40, it receives 0x1d instead, so the protocol is broken: ``` 2022-02-16 16:19:44.116 [bus notice] >40 2022-02-16 16:19:44.120 [bus notice]
if your interface can't receive the expected symbols, then using another interpreter on the messages won't be able to do any better
no idea about that
does this issue still persist? what does the Wemos status page look like in this situation?
is it possible that the Wemos has issues with WiFi stability?
I guess this is related to https://github.com/john30/ebusd-esp/issues/50