I also had a lot of errors, such as this one and others. They seamed to be hardware related (Ebus adapter shield v.5). After a firmware update they were gone.
In the process of searching the cause (ebus adapter or binding), I made two scripts to communicate with the adapter with the ebusctl command, without the binding.
I still use the scripts as they give me direct control over the communication. I don’t promote them over the binding, but you could use them to find the cause of your problem.
You should also be aware that the ebus is quite slow (2400 bits per second). I poll the devices every minute.