esera ethernet need help

[bosu1787]

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

[john30]

for Esera eth you should better use UDP due to latency issues and/or ensure that it is not buffering more than 1 symbol

[bosu1787]

thank you for answer. how can i set maxsymbol to 1 ?

[john30]

there is a configuration tool for the esera device, in which you can adjust UDP/TCP etc.

[bosu1787]

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/ 2022-04-17 17:39:19.529 [main notice] ebusd 22.2.p20220227 started with full scan on device udp:192.168.50.23:5000 2022-04-17 17:39:19.542 [bus notice] bus started with own address 31/36 2022-04-17 17:39:19.545 [mqtt notice] connection established 2022-04-17 17:39:19.555 [bus notice] signal acquired 2022-04-17 17:39:29.545 [main notice] starting initial full scan 2022-04-17 17:41:29.864 [main notice] update check: revision v22.2 available 2022-04-17 17:46:42.023 [bus notice] max. symbols per second: 109 2022-04-17 17:51:45.039 [bus notice] max. symbols per second: 118

pi@raspberrypi:~ $ ebusctl i version: ebusd 22.2.p20220227 update check: revision v22.2 available device: udp:192.168.50.23:5000 signal: acquired symbol rate: 44 max symbol rate: 90 min arbitration micros: 3 max arbitration micros: 35 min symbol latency: 4 max symbol latency: 6 reconnects: 0 masters: 1 messages: 11 conditional: 0 poll: 0 update: 4 address 31: master #8, ebusd address 36: slave #8, ebusd

[neutrino220]

I have the same problem with the Esera Ethernet Ebus Bridge. But if i switch to UDP, eBusd is connected but no Data comes in. Adjusting the poti brings no better results.

[bosu1787]

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/ 2022-05-23 12:16:23.157 [main notice] ebusd 22.2.p20220227 started with full scan on device udp:192.168.50.34:5000 2022-05-23 12:16:23.162 [bus notice] bus started with own address 31/36 2022-05-23 12:16:23.164 [mqtt notice] connection established 2022-05-23 12:16:23.171 [bus notice] signal acquired 2022-05-23 12:16:28.987 [bus notice] new master 10, master count 2 2022-05-23 12:16:33.163 [main notice] starting initial full scan 2022-05-23 12:16:39.746 [update notice] received unknown MS cmd: 1026b509030d0400 / 0321ffaa 2022-05-23 12:16:43.780 [main error] scan config 15: ERR: CRC error 2022-05-23 12:16:46.593 [bus notice] new master 01, master count 3 2022-05-23 12:16:46.593 [update notice] received unknown BC cmd: 01feb505054ec00b0080 2022-05-23 12:16:47.210 [main error] scan config 26: ERR: CRC error 2022-05-23 12:16:59.381 [main error] scan config 06: ERR: CRC error 2022-05-23 12:17:00.492 [update notice] received unknown MS cmd: 1026b509030d0400 / 0321ffaa 2022-05-23 12:17:02.297 [update notice] received unknown MS cmd: 1050b504010d / 050000d40305 2022-05-23 12:17:04.176 [main error] scan config 15: ERR: arbitration lost 2022-05-23 12:17:06.303 [main error] scan config 26: ERR: ACK error 2022-05-23 12:17:08.741 [main error] scan config 50: ERR: CRC error 2022-05-23 12:17:12.310 [update notice] received unknown MS cmd: 100ab503020001 / 0affffffffffffffffffff 2022-05-23 12:17:12.990 [update notice] received unknown MS cmd: 10edb503020001 / 0affffffffffffffffffff 2022-05-23 12:17:22.327 [main error] scan config 06: ERR: CRC error 2022-05-23 12:17:25.298 [bus notice] scan 0a: ;Vaillant;PMW01;0206;8302 2022-05-23 12:17:25.299 [update notice] store 0a ident: done 2022-05-23 12:17:25.299 [update notice] sent scan-read scan.0a QQ=31: Vaillant;PMW01;0206;8302 2022-05-23 12:17:25.299 [bus notice] scan 0a: ;Vaillant;PMW01;0206;8302 2022-05-23 12:17:25.309 [main notice] read common config file vaillant/scan.csv 2022-05-23 12:17:25.310 [main notice] read common config file vaillant/general.csv 2022-05-23 12:17:25.311 [main notice] read common config file vaillant/broadcast.csv 2022-05-23 12:17:25.320 [main notice] read scan config file vaillant/0a.pmw.hwc.csv for ID "pmw01", SW0206, HW8302 2022-05-23 12:17:25.326 [main notice] found messages: 118 (15 conditional on 8 conditions, 0 poll, 8 update) 2022-05-23 12:17:29.832 [main error] scan config 15: ERR: CRC error 2022-05-23 12:17:33.404 [main error] scan config 26: ERR: read timeout 2022-05-23 12:17:35.823 [bus notice] new master 03, master count 4 2022-05-23 12:17:35.823 [update notice] received unknown MS cmd: 1008b513020508 / 00 2022-05-23 12:17:36.609 [main error] scan config 50: ERR: CRC error 2022-05-23 12:17:39.177 [bus notice] scan ed: ;Vaillant;PMS01;0111;8502 2022-05-23 12:17:39.177 [update notice] store ed ident: done 2022-05-23 12:17:39.177 [update notice] sent scan-read scan.ed QQ=31: Vaillant;PMS01;0111;8502 2022-05-23 12:17:39.177 [bus notice] scan ed: ;Vaillant;PMS01;0111;8502 2022-05-23 12:17:39.833 [main error] scan config ed: ERR: ACK error 2022-05-23 12:17:48.152 [update notice] received unknown MS cmd: 01ecb505084dfc040000320100 / 00 2022-05-23 12:17:49.870 [update notice] received unknown BC cmd: 01feb505054ec00b0080 2022-05-23 12:17:51.991 [bus notice] scan 06: ;Vaillant;PMS01;0111;8502 2022-05-23 12:17:51.991 [update notice] store 06 ident: done 2022-05-23 12:17:51.991 [update notice] sent scan-read scan.06 QQ=31: Vaillant;PMS01;0111;8502 2022-05-23 12:17:51.991 [bus notice] scan 06: ;Vaillant;PMS01;0111;8502 2022-05-23 12:17:52.243 [main error] scan config 06: ERR: CRC error 2022-05-23 12:17:54.587 [main error] scan config 08: ERR: CRC error 2022-05-23 12:17:56.401 [update notice] received unknown MS cmd: 10ecb5040121 / 054f00015132 2022-05-23 12:17:57.713 [main error] scan config 15: ERR: CRC error 2022-05-23 12:18:00.059 [main error] scan config 50: ERR: ACK error 2022-05-23 12:18:03.062 [main error] scan config ec: ERR: ACK error 2022-05-23 12:18:05.764 [main notice] read scan config file vaillant/ed.pms.sc.csv for ID "pms01", SW0111, HW8502 2022-05-23 12:18:05.765 [main notice] found messages: 186 (15 conditional on 8 conditions, 0 poll, 8 update) 2022-05-23 12:18:19.128 [main error] scan config 06: ERR: CRC error 2022-05-23 12:18:20.421 [update notice] received unknown MS cmd: 1008b513020508 / 00 2022-05-23 12:18:22.130 [main error] scan config 08: ERR: ACK error 2022-05-23 12:18:24.710 [bus notice] scan 15: ;Vaillant;UI ;0508;6201 2022-05-23 12:18:24.710 [update notice] store 15 ident: done 2022-05-23 12:18:24.710 [update notice] sent scan-read scan.15 QQ=31: Vaillant;UI ;0508;6201 2022-05-23 12:18:24.710 [bus notice] scan 15: ;Vaillant;UI ;0508;6201 2022-05-23 12:18:25.429 [main error] scan config 15: ERR: CRC error 2022-05-23 12:18:27.909 [main error] scan config 50: ERR: CRC error 2022-05-23 12:18:30.314 [main error] scan config ec: ERR: CRC error 2022-05-23 12:18:31.557 [update notice] received unknown MS cmd: 1008b513020508 / 00 2022-05-23 12:18:43.899 [main error] scan config 06: ERR: CRC error 2022-05-23 12:18:46.223 [main error] scan config 08: ERR: ACK error 2022-05-23 12:18:48.641 [main error] scan config 15: ERR: ACK error 2022-05-23 12:18:51.025 [main error] scan config 50: ERR: ACK error 2022-05-23 12:18:53.427 [bus notice] scan ec: ;Vaillant;SOLSY;0500;6301 2022-05-23 12:18:53.427 [update notice] store ec ident: done 2022-05-23 12:18:53.427 [update notice] sent scan-read scan.ec QQ=31: Vaillant;SOLSY;0500;6301 2022-05-23 12:18:53.427 [bus notice] scan ec: ;Vaillant;SOLSY;0500;6301 2022-05-23 12:18:53.550 [update notice] received read hwc Status QQ=10: 75;on;-;60 2022-05-23 12:18:53.640 [main error] scan config ec: ERR: CRC error 2022-05-23 12:19:04.085 [update notice] received unknown MS cmd: 1050b504010d / 050000d40305 2022-05-23 12:19:07.171 [main error] scan config 06: ERR: ACK error 2022-05-23 12:19:07.812 [update notice] received unknown MS cmd: 1050b5050427015a01 / 00 2022-05-23 12:19:09.817 [main error] scan config 08: ERR: CRC error 2022-05-23 12:19:11.971 [main error] scan config 15: ERR: CRC error 2022-05-23 12:19:14.017 [bus notice] max. symbols per second: 117 2022-05-23 12:19:14.052 [main error] scan config 50: ERR: ACK error 2022-05-23 12:19:16.182 [main error] scan config ec: ERR: CRC error 2022-05-23 12:19:28.438 [update notice] sent unknown MS cmd: 3106b5090124 / 09003231313634313030 2022-05-23 12:19:28.594 [main error] scan config 06: ERR: CRC error 2022-05-23 12:19:30.757 [main error] scan config 08: ERR: ACK error 2022-05-23 12:19:32.916 [main error] scan config 15: ERR: CRC error 2022-05-23 12:19:35.059 [bus notice] scan 50: ;Vaillant;SOLSY;0500;6301 2022-05-23 12:19:35.059 [update notice] store 50 ident: done 2022-05-23 12:19:35.059 [update notice] sent scan-read scan.50 QQ=31: Vaillant;SOLSY;0500;6301 2022-05-23 12:19:35.059 [bus notice] scan 50: ;Vaillant;SOLSY;0500;6301 2022-05-23 12:19:35.238 [main error] scan config 50: ERR: ACK error 2022-05-23 12:19:37.397 [main error] scan config ec: ERR: CRC error 2022-05-23 12:19:49.560 [update notice] sent scan-read scan.06 id QQ=31: 2022-05-23 12:19:49.717 [main error] scan config 06: ERR: CRC error 2022-05-23 12:19:51.853 [main error] scan config 08: ERR: CRC error 2022-05-23 12:19:53.987 [update notice] sent unknown MS cmd: 3115b5090124 / 09003231313530373030 2022-05-23 12:19:54.071 [main error] scan config 15: ERR: ACK error 2022-05-23 12:19:56.246 [main error] scan config 50: ERR: CRC error 2022-05-23 12:19:58.399 [main error] scan config ec: ERR: CRC error 2022-05-23 12:20:10.494 [main error] scan config 06: ERR: ACK error 2022-05-23 12:20:12.828 [main error] scan config 08: ERR: read timeout 2022-05-23 12:20:14.992 [main error] scan config 15: ERR: CRC error 2022-05-23 12:20:17.229 [main error] scan config 50: ERR: CRC error 2022-05-23 12:20:19.377 [main error] scan config ec: ERR: CRC error 2022-05-23 12:20:30.749 [update notice] received unknown MS cmd: 1008b513020508 / 00 2022-05-23 12:20:31.499 [main error] scan config 06: ERR: ACK error 2022-05-23 12:20:33.734 [main error] scan config 15: ERR: CRC error 2022-05-23 12:20:36.035 [main notice] read scan config file vaillant/50.solsy.mc.csv for ID "solsy", SW0500, HW6301 2022-05-23 12:20:36.040 [main notice] found messages: 271 (19 conditional on 11 conditions, 0 poll, 8 update) 2022-05-23 12:20:38.207 [update notice] sent unknown MS cmd: 31ecb5090124 / 09003231313530373030 2022-05-23 12:20:38.504 [main notice] read scan config file vaillant/ec.solsy.sc.csv for ID "solsy", SW0500, HW6301 2022-05-23 12:20:38.506 [main error] error executing instructions: ERR: duplicate name, last error: included "vaillant/iotest620.inc" for "ec", error including "vaillant/errors.inc" for "ec": ERR: duplicate name vaillant/errors.inc:4: ERR: duplicate name, invalid name 2022-05-23 12:20:38.506 [main notice] found messages: 342 (19 conditional on 11 conditions, 0 poll, 8 update) 2022-05-23 12:20:46.702 [update notice] received unknown BC cmd: 01feb505054ec00b0080 2022-05-23 12:20:50.826 [main notice] read scan config file vaillant/06.pms.csv for ID "pms01", SW0111, HW8502 2022-05-23 12:20:50.826 [main notice] found messages: 407 (19 conditional on 11 conditions, 0 poll, 8 update) 2022-05-23 12:20:52.988 [main error] scan config 15: ERR: CRC error 2022-05-23 12:20:53.089 [bus notice] max. symbols per second: 130 2022-05-23 12:21:05.174 [main error] scan config 15: ERR: CRC error 2022-05-23 12:21:17.477 [main notice] read scan config file vaillant/15.ui.csv for ID "ui", SW0508, HW6201 2022-05-23 12:21:17.479 [main notice] found messages: 591 (19 conditional on 13 conditions, 1 poll, 8 update) 2022-05-23 12:21:17.874 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:21:18.027 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:21:23.271 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:21:23.900 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:21:24.008 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:21:29.360 [bus error] poll ui YieldThisYear failed: ERR: read timeout 2022-05-23 12:21:35.280 [bus error] poll ui YieldThisYear failed: ERR: read timeout 2022-05-23 12:21:41.122 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:21:46.772 [update notice] received unknown BC cmd: 01feb505054ec00b0080 2022-05-23 12:21:47.141 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:21:53.282 [bus error] poll ui YieldThisYear failed: ERR: read timeout 2022-05-23 12:21:59.138 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:21:59.247 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:22:02.567 [update notice] received read hwc Status QQ=10: 75;on;-;60 2022-05-23 12:22:05.283 [bus error] poll ui YieldThisYear failed: ERR: read timeout 2022-05-23 12:22:08.324 [update notice] received read hwc currenterror QQ=10: -;-;-;-;- 2022-05-23 12:22:11.103 [bus error] poll ui YieldThisYear failed: ERR: ACK error 2022-05-23 12:22:11.736 [update notice] received unknown MS cmd: 1008b513020508 / 00 2022-05-23 12:22:17.126 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:22:23.166 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:22:23.281 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:22:23.396 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:22:23.598 [update notice] sent poll-read ui YieldThisYear QQ=31: 2022-05-23 12:22:23.709 [bus error] poll ui YieldThisYear failed: ERR: CRC error 2022-05-23 12:22:29.293 [bus error] poll ui YieldThisYear failed: ERR: read timeout 2022-05-23 12:22:35.176 [bus error] poll ui YieldThisYear failed: ERR: CRC error

[bosu1787]

Vaillant auroFLOW plus VPM 15 D is not supported by ebusd? i think the unknow messages is from my solar station auroflow vpm 15d

[john30]

@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.

[bosu1787]

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs.

ebusd.log

[neutrino220]

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs.

ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors.

I hope it helps you too.

[bosu1787]

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs. ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors.

I hope it helps you too.

which ground? can you explain me how to do that?

thank you

[neutrino220]

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs. ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors. 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. Please notice: Im no electrician and this is at your own risk!

[bosu1787]

af

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs. ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors. 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. Please notice: Im no electrician and this is at your own risk!

pfff thank you is a lot better im not getting crc errors anymore after i connect de powers supply to gnd

[neutrino220]

af

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs. ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors. 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. Please notice: Im no electrician and this is at your own risk!

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. Toast me with a beer 🍻 😉

[bosu1787]

@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 ebusd.log

[bosu1787]

af

@john30 i moved the ebus kupler closer to the system so now the cables is about 2m max. now im getting a lot more data but still got a lot of errors... please check my logs. ebusd.log

This helped me too but the problem was the Powersupply. I'm getting the best results by using an battery (for testing). After that test i've connected the negative output from my Powersupply to ground and it works! Now im getting only a small number of errors. 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. Please notice: Im no electrician and this is at your own risk!

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. Toast me with a beer 🍻 😉

yeap definitely, at least for esera koppler

[john30]

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

[bosu1787]

@john30 why WaterPressure is not discovered in HomeAssistant? how can i add WaterPressure in HA?

[john30]

@bosu1787 completely off topic, so please ask somewhere else