-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No boiler detected #230
Comments
are you sure no other tool is using the same device /dev/ttyUSB0? like fhem e.g. |
Arf! You are true.
But, I still don't get the other masters on the network. |
check for messages being sent/received by using "ebusctl raw" for a start. then the ebusd.log should reveal whats on the wire. you could also go and check "ebusctl grab result" |
Hello back... 1st of all, happy new year! Here is the result of grab, not really expressive! :)
On the other hand, the raw data are really RAW :) If anything seems to be abnormal, that would help.
|
same issue as before, you need to make sure that no other process is using the serial interface! |
We did a fresh install of a raspbian (stetch this time instead of jessie) and only setup wifi + update + ebusd package. We have quite the same result :
And the logs looks like this :
|
as said before, the data is just no ebus traffic but something else. check your system for any other process using the device e.g. using lsof and searching for ttyUSB0 in the output |
We red what you said before and that's the reason why we re-installed a fresh raspbian to avoid any modification that could influence this.
When we disconnect the ebus wires from the board, nothing appears in "raw logging mode". Does this means that the boards is doing a mess with the boiler data? Let me know where we should discuss about this? (as we are not german speaking, the fhem forums are quite weird :) ) |
the thing is: the data of the ebusd.log is just not ebus traffic. this is something completely different. |
As you expected, something else was writing on the USB-serial BUS : The hardware on which we connected. The issue was coming from us, we connected the R.Pi to an Wemos D1 installed on the eBUS adapter v2.2. Actually, by default those hardware are setup to be used with a serial connection to a terminal (Putty). So the bytes we got in our logs are probably the menus displayed on this interface. John30 gave me a track to use this interface :
We actually used the UART provided separately with the hardware and I soldered it to be connected directly on the base board. Thanks for the support, I hope that could help others to avoid to do the same error. (RTFM :) ) |
Hello,
1st of all, thanks for the great job (it looks to be great, because that doesn't work yet on our side :-)
We are using an eBUS adapter 2.2 (pre-soldered) connected to a R.Pi3 USB port. The eBus is connected to the 2-wire of a Vaillant EcoTec Plus.
The eBus seems to be communicating :
When I start with scanconfig, I don't see any scan being done successfully. There are also those "max. symbols per second notices, that's quite strange.
The http interface gives the following JSON :
Any idea of what we missed?
Thanks in advance.
Rac'
The text was updated successfully, but these errors were encountered: