John
John
which ebusd version are you using?
21.3 was published short time ago. anyway I'd prefer if you could try with a build from the latest source
just use the .deb package of the [release](https://github.com/john30/ebusd/releases/tag/v21.3)
closed due to inactivity
what hardware interface do you have? there are some (actually many) that might miss some bytes or misinterpret the voltage value seen on the bus. you could use 'log raw...
closed due to inactivity
can you reproduce this with the current versions of ebusd and ebusd-esp?
this looks a lot like you have another process using the same ttyUSB0 device. candidates for such processes are fhem and other stuff. you can check with lsof if another...
did you jumper the adapter to non-enhanced mode? If not, you need to use `-d enh:/dev/ttyUSB0` instead of `-d /dev/ttyUSB0`
closed due to inactivity