esera ethernet need help #589
Comments
|
for Esera eth you should better use UDP due to latency issues and/or ensure that it is not buffering more than 1 symbol |
|
thank you for answer. how can i set maxsymbol to 1 ? |
|
there is a configuration tool for the esera device, in which you can adjust UDP/TCP etc. |
|
i have that tool WIZ107SR i set it now to UDP but max symbol rate is 90 pi@raspberrypi:~ $ sudo ebusd -f -d udp:192.168.50.23:5000 --latency=10000 --receivetimeout=100000 --mqttport=1883 --mqtthost=192.168.50.79 --httpport=8889 --scanconfig=full -c /etc/ebusd/ pi@raspberrypi:~ $ ebusctl i |
|
I have the same problem with the Esera Ethernet Ebus Bridge. |
|
after fine ajustment of potentiometer i got this but also i can see few errors. do i need to try to adjust more? sudo ebusd -f -d udp:192.168.50.34:5000 --latency=10000 --receivetimeout=100000 --mqttport=1883 --mqtthost=192.168.50.79 --httpport=8889 --scanconfig=full -c /etc/ebusd/ |
|
Vaillant auroFLOW plus VPM 15 D is not supported by ebusd? i think the unknow messages is from my solar station auroflow vpm 15d |
|
@neutrino220 for UDP to work, at least one character needs to be sent to the device from ebusd as otherwise it doesn' know the target IP, as described in the wiki under --initsend. othwerwise you'd have to configure the fix target IP and port in the device. @bosu1787 I did not mean the max symbol rate as reported by ebusd but the number of cached symbols after which the interface will send the data to ebusd. this can be set up in that WIZ tool iirc "a few errors" are generally not a problem, but in your log these are not just a few but almost every second message. that is way too much for running it smoothly. you need to get the poti adjusted better. or mayber change the cabling, connect the interface closer to the heating circuit. |
This helped me too but the problem was the Powersupply. I hope it helps you too. |
which ground? can you explain me how to do that? thank you |
Ive connected the Powersupply normally to the Esera Ethernet Adapter and also parallel the negative connector (of the 12/24V side between powersupply and Esera Adapter) to the yellow/green protective ground conductor. |
|
af
pfff thank you is a lot better im not getting crc errors anymore after i connect de powers supply to gnd |
I think @john30 should implement this to the Wiki. |
|
@john30 now im getting no errors only "received unknown MS cmd" i have a question on mqtt explorer i dont see all the data for exemple i dont se Ntc1Sensor from pms but if i hit "ebusctl read -c pms Ntc1Sensor" i recive the value with no lag. the same for "ebusctl read -c bai WaterPressure" so im not able to set this in HomeAssistant. here is my new log |
yeap definitely, at least for esera koppler |
|
uh, no, I'll definitely not guide people into connecting the power supply output to the ground of the installation. you better ask the manufacturer for help, not me |
|
@john30 why WaterPressure is not discovered in HomeAssistant? how can i add WaterPressure in HA? |
|
@bosu1787 completely off topic, so please ask somewhere else |
Description
no response from "ebusctl i"
edit: after reboot the rpi i got response from ebusctl but no ebus device was found...
pi@raspberrypi:/etc/ebusd $ ebusctl i
version: ebusd 22.2.p20220227
device: 192.168.50.23:5000
signal: acquired
symbol rate: 20
max symbol rate: 80
min arbitration micros: 3
max arbitration micros: 79
min symbol latency: 4
max symbol latency: 5
reconnects: 0
masters: 2
messages: 12
conditional: 0
poll: 0
update: 4
address 10: master #2
address 31: master #8, ebusd
address 36: slave #8, ebusd
pi@raspberrypi:/etc/ebusd/vaillant $ ebusd -f -c /tmp --logareas bus --loglevel info --lograwdata=bytes -d 192.168.50.23:5000
2022-04-12 05:27:01.960 [bus notice] bus started with own address 31/36
2022-04-12 05:27:01.961 [bus notice] <aa
2022-04-12 05:27:01.961 [bus notice] signal acquired
2022-04-12 05:27:01.989 [bus notice] <aa
2022-04-12 05:27:02.033 [bus notice] <fa
2022-04-12 05:27:02.078 [bus notice] <fd
2022-04-12 05:27:02.119 [bus notice] <aa
2022-04-12 05:27:02.162 [bus notice] <aa
2022-04-12 05:27:02.206 [bus notice] <aa
2022-04-12 05:27:02.248 [bus notice] <aa
2022-04-12 05:27:02.291 [bus notice] <ea
2022-04-12 05:27:02.378 [bus notice] <aa
2022-04-12 05:27:02.420 [bus notice] <aa
2022-04-12 05:27:02.463 [bus notice] <aa
2022-04-12 05:27:02.507 [bus notice] <aa
2022-04-12 05:27:02.550 [bus notice] <aa
2022-04-12 05:27:02.592 [bus notice] <fa
2022-04-12 05:27:02.639 [bus notice] <ff
2022-04-12 05:27:02.679 [bus notice] <aa
2022-04-12 05:27:02.722 [bus notice] <aa
2022-04-12 05:27:02.765 [bus notice] <aa
2022-04-12 05:27:02.808 [bus notice] <aa
2022-04-12 05:27:02.851 [bus notice] <aa
2022-04-12 05:27:02.938 [bus notice] <d5
2022-04-12 05:27:02.981 [bus notice] <aa
2022-04-12 05:27:03.023 [bus notice] <aa
2022-04-12 05:27:03.067 [bus notice] <aa
2022-04-12 05:27:03.110 [bus notice] <aa
2022-04-12 05:27:03.153 [bus notice] <fe
2022-04-12 05:27:03.198 [bus notice] <ff
2022-04-12 05:27:03.239 [bus notice] <aa
2022-04-12 05:27:03.282 [bus notice] <aa
2022-04-12 05:27:03.325 [bus notice] <aa
2022-04-12 05:27:03.368 [bus notice] <aa
2022-04-12 05:27:03.411 [bus notice] <aa
2022-04-12 05:27:03.454 [bus notice] <ff
2022-04-12 05:27:03.499 [bus notice] <f5
2022-04-12 05:27:03.540 [bus notice] <aa
2022-04-12 05:27:03.583 [bus notice] <aa
2022-04-12 05:27:03.626 [bus notice] <aa
2022-04-12 05:27:03.670 [bus notice] <aa
2022-04-12 05:27:03.713 [bus notice] <fa
2022-04-12 05:27:03.758 [bus notice] <fd
2022-04-12 05:27:03.798 [bus notice] <aa
2022-04-12 05:27:03.842 [bus notice] <aa
2022-04-12 05:27:03.885 [bus notice] <aa
2022-04-12 05:27:03.928 [bus notice] <aa
2022-04-12 05:27:03.971 [bus notice] <aa
2022-04-12 05:27:04.014 [bus notice] <ff
2022-04-12 05:27:04.058 [bus notice] <f5
2022-04-12 05:27:04.100 [bus notice] <aa
2022-04-12 05:27:04.143 [bus notice] <aa
2022-04-12 05:27:04.186 [bus notice] <aa
2022-04-12 05:27:04.229 [bus notice] <aa
2022-04-12 05:27:04.273 [bus notice] <fa
2022-04-12 05:27:04.358 [bus notice] <aa
2022-04-12 05:27:04.402 [bus notice] <aa
2022-04-12 05:27:04.445 [bus notice] <aa
2022-04-12 05:27:04.488 [bus notice] <aa
2022-04-12 05:27:04.531 [bus notice] <aa
2022-04-12 05:27:04.574 [bus notice] <fe
2022-04-12 05:27:04.618 [bus notice] <f5
2022-04-12 05:27:04.660 [bus notice] <aa
2022-04-12 05:27:04.704 [bus notice] <aa
2022-04-12 05:27:04.746 [bus notice] <aa
2022-04-12 05:27:04.789 [bus notice] <aa
2022-04-12 05:27:04.832 [bus notice] <fa
2022-04-12 05:27:04.879 [bus notice] <ff
2022-04-12 05:27:04.918 [bus notice] <d5
ebusd version
latest release
ebusd arguments
EBUSD_OPTS="--scanconfig --mqttport=1883 --mqtthost=localhost -d tcp:192.168.50.23:5000"
Operating system
Debian 11 (Bullseye) / Raspbian 11 / Ubuntu 20-21
CPU architecture
armv7l
Dockerized
No response
Hardware interface
Esera Ethernet
Related integration
TCP (cmdline client like ebusctl or netcat)
Logs
2022-04-12 10:02:42.386 [main notice] ebusd 22.2.p20220227 started with full scan on device 192.168.50.23:5000
2022-04-12 10:02:43.241 [bus notice] bus started with own address 31/36
2022-04-12 10:02:43.241 [bus notice] signal acquired
2022-04-12 10:02:43.242 [mqtt notice] connection established
2022-04-12 10:02:53.242 [main notice] starting initial full scan
2022-04-12 10:04:30.641 [bus notice] new master 10, master count 2
2022-04-12 10:04:35.989 [main error] scan config 15: ERR: ACK error
2022-04-12 10:04:48.757 [main error] scan config 15: ERR: read timeout
The text was updated successfully, but these errors were encountered: