eBus Schaltung in Betrieb nehmen

[john30]

Hier mal meine "aa"s

du hast Tonnen von "ERR: wrong symbol received", das kann so nicht funktionieren

[Physman]

Hmmm - ja, aber was kann ich dagegen tun?
Die rawdata mit "aa"s über das Poti trimmen, da kommen immer die Messages:

Machen die aus diesem log die "wrong symbol received"?

Code Auswählen Erweitern

2022-11-08 07:50:23.627 [update info] received BC cmd: 10feb516080025500708110222
2022-11-08 07:50:23.627 [update notice] received unknown BC cmd: 10feb516080025500708110222

[Physman]

Ich gebe auf - habe noch einmal den Poti von links nach rechts getrimmt. Leider ohne Erfolg.
Die früne LED flackert recht schön, dann kommt aber paar Sekunden ein kurzer längeres Leuchten, wo dann die "unknown BC cmd"s kommen.

Liegt das nun am Poti Tuning oder an der Latency in der ebusd?
Was kann ich sonst noch tun, ausser den Adapter im Hohen Bogen aus dem Fenster zu werfen?

[fishpepper]

Hallo Zusammen,

ich poste das hier noch einmal (hatte mit john30 schon mal über dieses "issue" kurz geredet) - evtl. hat ja hier jemand von den Experten noch eine Idee, auch wenn ich schon den neuen ebus Adapter reserviert habe.
Man liest hier schon mal des öfteren, dass einige Steuergeräte (700 / 430 / 470 etc) nicht gefunden werden beim Scan.

Ich habe das selbe Problem... Das bai Gerät ("MF=Vaillant;ID=BAI00;SW=0201;HW=9002") wird gefunden und ich kann wunderbar Daten lesen.
Das 700er nicht. Wenn ich die Therme neu starte dann taucht es als Adresse 15 auf, das CSV wird aber nicht geladen.

Starte ich ebusd neu während die Therme läuft findet er auf Adresse 15 nichts. Ich sehe nur Fehler im log:

Code Auswählen Erweitern


2022-11-09 06:52:49.206 [main debug] performing regular tasks
2022-11-09 06:52:49.206 [bus info] scan 15 cmd: 3115070400
2022-11-09 06:52:49.245 [bus notice] <aa
2022-11-09 06:52:49.246 [bus debug] start request 31
2022-11-09 06:52:49.246 [bus debug] arbitration start with 31
2022-11-09 06:52:49.287 [bus notice] <aa
2022-11-09 06:52:49.287 [bus notice] >31
2022-11-09 06:52:49.293 [bus notice] <31
2022-11-09 06:52:49.293 [bus debug] arbitration won
2022-11-09 06:52:49.293 [bus debug] arbitration delay 2213 micros
2022-11-09 06:52:49.293 [bus debug] switching from ready to send command
2022-11-09 06:52:49.296 [bus notice] >15
2022-11-09 06:52:49.301 [bus notice] <15
2022-11-09 06:52:49.301 [bus debug] send/receive symbol latency 5 ms
2022-11-09 06:52:49.304 [bus notice] >07
2022-11-09 06:52:49.310 [bus notice] <07
2022-11-09 06:52:49.310 [bus debug] send/receive symbol latency 5 ms
2022-11-09 06:52:49.312 [bus notice] >04
2022-11-09 06:52:49.318 [bus notice] <04
2022-11-09 06:52:49.318 [bus debug] send/receive symbol latency 5 ms
2022-11-09 06:52:49.321 [bus notice] >00
2022-11-09 06:52:49.326 [bus notice] <00
2022-11-09 06:52:49.326 [bus debug] send/receive symbol latency 5 ms
2022-11-09 06:52:49.326 [bus debug] switching from send command to send command CRC
2022-11-09 06:52:49.329 [bus notice] >8b
2022-11-09 06:52:49.334 [bus notice] <8b
2022-11-09 06:52:49.334 [bus debug] send/receive symbol latency 5 ms
2022-11-09 06:52:49.334 [bus debug] switching from send command CRC to receive command ACK
2022-11-09 06:52:49.392 [bus debug] notify request: ERR: read timeout
2022-11-09 06:52:49.392 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2022-11-09 06:52:49.392 [main error] scan config 15: ERR: read timeout



Als Interface nutze ich einen selber gelöteten ebuzzz adapter (https://gitlab.com/fromeijn/ebuzzz-adapter).
Vom Aufbau her sieht der mit dem comparator etc gut aus (kein poti) und nutzt auch scheinbar einen brauchbaren cp210x als usb Wandler.
Das ganze hängt per USB an nem raspi.

Hat irgendjemand noch eine Idee was ich weiter testen kann? Ich bin fast so weit mein Oszi und/oder den Logicanalyzer in den Keller zur Therme zu schlürren und mir mal die Signale in echt anzusehen...
Das die 700er Geräte oft Probleme machen finde ich irgendwie komisch, die Bus Kommunikation sieht ja erstmal brauchbar aus bei mir.
Bei mir steckt das 700er Gerät auch direkt im Keller in der Therme, hat das evtl einen Einfluss?

Grüße,
Simon

[Physman]

Schön nicht alleine zu sein

Könnte es sein, dass der ebusd, hier bei mir mit Adresse 31 und 36 belegt, im Konflikt mit einer anderen Adresse im ebus des systems ist?
Wie sollte man das testen?

Ebusd eine andere Adresse zuweisen? Aber wie?

[fishpepper]

Ich glaub ich bin da was auf der Spur... Beim nachmessen habe ich gesehen das mein Adapter nie gesendet hat....
Ich hab dummerweise eine 12V statt 9.1V Zenerdiode bestellt und verbaut (Zahlendreher).
Ich habe mal testweise 15 normale Shorkys als Ersatz drangefriemelt, jetzt bekomme ich Daten und das CSV wird auch geladen!

Mein adapter hat wohl also nie gresendet! Das erklärt auch warum ich das bai Gerät gesehen habe, das 700er hat wohl von dem bai immer Daten gepollt, die hat ebud gesehen...
Übermorgen kommen die passenden Dioden, dann weiss ich mehr.
Wenn die Dioden da sind und alles klappt hätte ich ein drei fertig bestückte ebuzzz über falls jemand Interesse hat (musste 5 bestellen).

Grüße,
Simon

[Physman]

Freut mich!

Aber leider hilft das dem ESERA EBUS BUS Adapter nicht sehr. Heisst das denn, dass der ESERA Adapter nicht senden kann?
Sehe auch bei mir nur "<aa"s und keine ">aa"s....

Schade, dachte es könnte was werden...

[Physman]

ok, so die Adresse ist es auch nicht....

der ebsud.log in Debug sieht so aus:

Code Auswählen Erweitern

2022-11-10 07:37:12.621 [bus debug] ERR: SYN received during receive command, switching to ready
2022-11-10 07:37:14.571 [main debug] performing regular tasks
2022-11-10 07:37:14.571 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:37:15.705 [update info] received MS cmd: 1008b5110101 / 093c3600084c620000ff
2022-11-10 07:37:15.706 [update notice] received read bai Status01 QQ=10: 30.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:37:17.737 [update info] received MS cmd: 1008b5110100 / 08e901120000080081
2022-11-10 07:37:17.737 [update notice] received unknown MS cmd: 1008b5110100 / 08e901120000080081
2022-11-10 07:37:17.961 [update info] received BC cmd: 10feb51603010008
2022-11-10 07:37:17.961 [update notice] received update-read broadcast outsidetemp QQ=10: 8.000
2022-11-10 07:37:19.577 [mqtt debug] publish ebusd/broadcast/outsidetemp {
     "temp2": {"value": 8.000}}
2022-11-10 07:37:19.578 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 30.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:37:19.700 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:37:19.700 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:37:24.572 [main debug] performing regular tasks
2022-11-10 07:37:24.572 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:37:24.581 [bus debug] start request ff
2022-11-10 07:37:24.581 [bus debug] arbitration start with ff
2022-11-10 07:37:24.629 [bus debug] arbitration won
2022-11-10 07:37:24.629 [bus debug] arbitration delay 1767 micros
2022-11-10 07:37:24.629 [bus debug] switching from ready to send command
2022-11-10 07:37:24.637 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:24.645 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:24.653 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:24.662 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:24.662 [bus debug] switching from send command to send command CRC
2022-11-10 07:37:24.667 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:37:24.667 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:37:24.667 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:37:24.667 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:37:24.668 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:37:25.764 [update info] received MS cmd: 1008b5110101 / 09403800084c620000ff
2022-11-10 07:37:25.764 [update notice] received read bai Status01 QQ=10: 32.0;28.0;8.000;38.0;49.0;off
2022-11-10 07:37:26.668 [main debug] performing regular tasks
2022-11-10 07:37:26.668 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:37:26.668 [mqtt debug] publish ebusd/global/uptime 480
2022-11-10 07:37:26.669 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 32.0},
     "1": {"name": "temp1", "value": 28.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:37:27.746 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-10 07:37:27.747 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-10 07:37:29.745 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:37:29.745 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:37:31.712 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:37:31.712 [mqtt debug] publish ebusd/bai/Status02 {
     "0": {"name": "hwcmode", "value": "auto"},
     "1": {"name": "temp0", "value": 60},
     "2": {"name": "temp1", "value": 50.0},
     "3": {"name": "temp0", "value": 80},
     "4": {"name": "temp1", "value": 55.0}}
2022-11-10 07:37:35.794 [update info] received MS cmd: 1008b5110101 / 093a3600084c620000ff
2022-11-10 07:37:35.794 [update notice] received read bai Status01 QQ=10: 29.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:37:36.668 [main debug] performing regular tasks
2022-11-10 07:37:36.669 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:37:36.700 [bus debug] start request ff
2022-11-10 07:37:36.700 [bus debug] arbitration start with ff
2022-11-10 07:37:36.750 [bus debug] arbitration won
2022-11-10 07:37:36.750 [bus debug] arbitration delay 1650 micros
2022-11-10 07:37:36.750 [bus debug] switching from ready to send command
2022-11-10 07:37:36.757 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:37:36.765 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:36.773 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:36.781 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:36.782 [bus debug] switching from send command to send command CRC
2022-11-10 07:37:36.787 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:37:36.788 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:37:36.788 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:37:36.788 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:37:36.788 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 29.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:37:37.791 [update info] received MS cmd: 1008b5040100 / 0a03383707101104220008
2022-11-10 07:37:37.792 [update notice] received read bai DateTime QQ=10: valid;07:37:38;10.11.2022;8.000
2022-11-10 07:37:38.788 [main debug] performing regular tasks
2022-11-10 07:37:38.788 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:37:38.789 [mqtt debug] publish ebusd/bai/DateTime {
     "dcfstate": {"value": "valid"},
     "btime": {"value": "07:37:38"},
     "bdate": {"value": "10.11.2022"},
     "temp2": {"value": 8.000}}
2022-11-10 07:37:39.792 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:37:39.793 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:37:41.046 [network debug] [00004] wait for result
2022-11-10 07:37:41.046 [network info] [00004] client connection opened 127.0.0.1
2022-11-10 07:37:41.046 [main debug] >>> info
2022-11-10 07:37:41.048 [main debug] <<< version: ebusd 22.4.v22.4
device: /dev/ttyHZG
signal: acquired
symbol rate: 22
max symbol rate: 98
m ...
2022-11-10 07:37:41.050 [network info] [00004] connection closed
2022-11-10 07:37:41.793 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:37:42.047 [network debug] dead connection removed - 0
2022-11-10 07:37:42.794 [mqtt debug] publish ebusd/global/uptime 496
2022-11-10 07:37:45.808 [update info] received MS cmd: 1008b5110101 / 09363600084c620000ff
2022-11-10 07:37:45.808 [update notice] received read bai Status01 QQ=10: 27.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:37:46.048 [main debug] performing regular tasks
2022-11-10 07:37:46.048 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:37:46.088 [bus debug] start request ff
2022-11-10 07:37:46.088 [bus debug] arbitration start with ff
2022-11-10 07:37:46.138 [bus debug] arbitration won
2022-11-10 07:37:46.138 [bus debug] arbitration delay 2498 micros
2022-11-10 07:37:46.138 [bus debug] switching from ready to send command
2022-11-10 07:37:46.146 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:37:46.154 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:46.162 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:46.170 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:46.170 [bus debug] switching from send command to send command CRC
2022-11-10 07:37:46.177 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:37:46.177 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:37:46.177 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:37:46.177 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:37:46.177 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 27.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:37:47.823 [update info] received MS cmd: 1008b5100305ff01 / 00
2022-11-10 07:37:47.823 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-10 07:37:48.177 [main debug] performing regular tasks
2022-11-10 07:37:48.178 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:37:49.865 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:37:49.866 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:37:53.183 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:37:55.881 [update info] received MS cmd: 1008b5110101 / 09363600084c620000ff
2022-11-10 07:37:55.882 [update notice] received read bai Status01 QQ=10: 27.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:37:57.840 [update info] received BC cmd: 10feb516080057370710110422
2022-11-10 07:37:57.840 [update notice] received update-read broadcast vdatetime QQ=10: 07:37:57;10.11.2022
2022-11-10 07:37:58.091 [update info] received MS cmd: 1008b512020064 / 00
2022-11-10 07:37:58.091 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-10 07:37:58.178 [main debug] performing regular tasks
2022-11-10 07:37:58.178 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:37:58.187 [bus debug] start request ff
2022-11-10 07:37:58.187 [bus debug] arbitration start with ff
2022-11-10 07:37:58.191 [mqtt debug] publish ebusd/global/uptime 512
2022-11-10 07:37:58.235 [bus debug] arbitration won
2022-11-10 07:37:58.235 [bus debug] arbitration delay 1461 micros
2022-11-10 07:37:58.235 [bus debug] switching from ready to send command
2022-11-10 07:37:58.242 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:58.251 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:58.259 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:58.267 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:37:58.267 [bus debug] switching from send command to send command CRC
2022-11-10 07:37:58.273 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:37:58.273 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:37:58.273 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:37:58.274 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:37:58.274 [mqtt debug] publish ebusd/broadcast/vdatetime {
     "time": {"value": "07:37:57"},
     "date": {"value": "10.11.2022"}}
2022-11-10 07:37:58.275 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 27.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:37:59.276 [mqtt debug] publish ebusd/bai/StatusCirPump {
     "0": {"name": "", "value": "on"}}
2022-11-10 07:37:59.872 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:37:59.872 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:00.274 [main debug] performing regular tasks
2022-11-10 07:38:00.274 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:00.275 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:05.887 [update info] received MS cmd: 1008b5110101 / 09363600084c620000ff
2022-11-10 07:38:05.887 [update notice] received read bai Status01 QQ=10: 27.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:07.933 [update info] received MS cmd: 1008b5040100 / 0a03083807101104220008
2022-11-10 07:38:07.934 [update notice] received read bai DateTime QQ=10: valid;07:38:08;10.11.2022;8.000
2022-11-10 07:38:08.201 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-10 07:38:08.201 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-10 07:38:09.887 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:38:09.887 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:10.275 [main debug] performing regular tasks
2022-11-10 07:38:10.275 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:38:10.300 [bus debug] start request ff
2022-11-10 07:38:10.300 [bus debug] arbitration start with ff
2022-11-10 07:38:10.350 [bus debug] arbitration won
2022-11-10 07:38:10.350 [bus debug] arbitration delay 1560 micros
2022-11-10 07:38:10.350 [bus debug] switching from ready to send command
2022-11-10 07:38:10.358 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:38:10.366 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:10.374 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:10.383 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:38:10.383 [bus debug] switching from send command to send command CRC
2022-11-10 07:38:10.387 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:38:10.387 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:38:10.387 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:38:10.387 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:38:10.388 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:10.388 [mqtt debug] publish ebusd/bai/DateTime {
     "dcfstate": {"value": "valid"},
     "btime": {"value": "07:38:08"},
     "bdate": {"value": "10.11.2022"},
     "temp2": {"value": 8.000}}
2022-11-10 07:38:10.388 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 27.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:10.389 [mqtt debug] publish ebusd/bai/Status02 {
     "0": {"name": "hwcmode", "value": "auto"},
     "1": {"name": "temp0", "value": 60},
     "2": {"name": "temp1", "value": 50.0},
     "3": {"name": "temp0", "value": 80},
     "4": {"name": "temp1", "value": 55.0}}
2022-11-10 07:38:12.388 [main debug] performing regular tasks
2022-11-10 07:38:12.388 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:14.391 [mqtt debug] publish ebusd/global/uptime 528
2022-11-10 07:38:15.937 [update info] received MS cmd: 1008b5110101 / 09363600084c620000ff
2022-11-10 07:38:15.937 [update notice] received read bai Status01 QQ=10: 27.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:17.396 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 27.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:17.933 [update info] received MS cmd: 1008b5110100 / 08b801140000080081
2022-11-10 07:38:17.934 [update notice] received unknown MS cmd: 1008b5110100 / 08b801140000080081
2022-11-10 07:38:18.162 [update info] received BC cmd: 10feb51603010008
2022-11-10 07:38:18.163 [update notice] received update-read broadcast outsidetemp QQ=10: 8.000
2022-11-10 07:38:19.983 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:38:19.984 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:22.389 [main debug] performing regular tasks
2022-11-10 07:38:22.389 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:38:22.422 [bus debug] start request ff
2022-11-10 07:38:22.429 [bus debug] arbitration start with ff
2022-11-10 07:38:22.471 [bus debug] arbitration won
2022-11-10 07:38:22.471 [bus debug] arbitration delay 2483 micros
2022-11-10 07:38:22.471 [bus debug] switching from ready to send command
2022-11-10 07:38:22.479 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:22.488 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:22.496 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:22.504 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:22.504 [bus debug] switching from send command to send command CRC
2022-11-10 07:38:22.510 [bus debug] notify request: ERR: SYN received
2022-11-10 07:38:22.510 [bus debug] ERR: SYN received during send command CRC, switching to ready
2022-11-10 07:38:22.510 [main error] scan config 15: ERR: SYN received
2022-11-10 07:38:22.510 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:38:22.510 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:22.511 [mqtt debug] publish ebusd/broadcast/outsidetemp {
     "temp2": {"value": 8.000}}
2022-11-10 07:38:22.553 [bus debug] ERR: SYN received during receive command, switching to ready
2022-11-10 07:38:24.510 [main debug] performing regular tasks
2022-11-10 07:38:24.511 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:25.955 [update info] received MS cmd: 1008b5110101 / 09383600084c620000ff
2022-11-10 07:38:25.956 [update notice] received read bai Status01 QQ=10: 28.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:27.989 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-10 07:38:27.989 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-10 07:38:29.517 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 28.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:29.518 [mqtt debug] publish ebusd/bai/Status02 {
     "0": {"name": "hwcmode", "value": "auto"},
     "1": {"name": "temp0", "value": 60},
     "2": {"name": "temp1", "value": 50.0},
     "3": {"name": "temp0", "value": 80},
     "4": {"name": "temp1", "value": 55.0}}
2022-11-10 07:38:29.997 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:38:29.998 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:30.519 [mqtt debug] publish ebusd/global/uptime 544
2022-11-10 07:38:34.511 [main debug] performing regular tasks
2022-11-10 07:38:34.512 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:38:34.520 [bus debug] start request ff
2022-11-10 07:38:34.520 [bus debug] arbitration start with ff
2022-11-10 07:38:34.569 [bus debug] arbitration won
2022-11-10 07:38:34.569 [bus debug] arbitration delay 1986 micros
2022-11-10 07:38:34.569 [bus debug] switching from ready to send command
2022-11-10 07:38:34.577 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:34.585 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:34.594 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:38:34.602 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:34.602 [bus debug] switching from send command to send command CRC
2022-11-10 07:38:34.609 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:38:34.609 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:38:34.609 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:38:34.609 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:38:34.610 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:36.016 [update info] received MS cmd: 1008b5110101 / 09383600084c620000ff
2022-11-10 07:38:36.016 [update notice] received read bai Status01 QQ=10: 28.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:36.610 [main debug] performing regular tasks
2022-11-10 07:38:36.610 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:38.056 [update info] received MS cmd: 1008b5040100 / 0a03383807101104220008
2022-11-10 07:38:38.056 [update notice] received read bai DateTime QQ=10: valid;07:38:38;10.11.2022;8.000
2022-11-10 07:38:40.023 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:38:40.023 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:41.616 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:41.616 [mqtt debug] publish ebusd/bai/DateTime {
     "dcfstate": {"value": "valid"},
     "btime": {"value": "07:38:38"},
     "bdate": {"value": "10.11.2022"},
     "temp2": {"value": 8.000}}
2022-11-10 07:38:41.619 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 28.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:46.072 [update info] received MS cmd: 1008b5110101 / 09383600084c620000ff
2022-11-10 07:38:46.073 [update notice] received read bai Status01 QQ=10: 28.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:46.611 [main debug] performing regular tasks
2022-11-10 07:38:46.611 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:38:46.619 [bus debug] start request ff
2022-11-10 07:38:46.619 [bus debug] arbitration start with ff
2022-11-10 07:38:46.625 [mqtt debug] publish ebusd/global/uptime 560
2022-11-10 07:38:46.667 [bus debug] arbitration won
2022-11-10 07:38:46.667 [bus debug] arbitration delay 1093 micros
2022-11-10 07:38:46.667 [bus debug] switching from ready to send command
2022-11-10 07:38:46.676 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:46.685 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:38:46.692 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:46.701 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:46.701 [bus debug] switching from send command to send command CRC
2022-11-10 07:38:46.706 [bus debug] notify request: ERR: SYN received
2022-11-10 07:38:46.707 [main error] scan config 15: ERR: SYN received
2022-11-10 07:38:46.707 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:38:46.707 [bus debug] ERR: SYN received during send command CRC, switching to ready
2022-11-10 07:38:46.749 [bus debug] ERR: SYN received during receive command, switching to ready
2022-11-10 07:38:47.708 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 28.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:48.038 [update info] received MS cmd: 1008b5100305ff01 / 00
2022-11-10 07:38:48.038 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-10 07:38:48.707 [main debug] performing regular tasks
2022-11-10 07:38:48.708 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:50.085 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:38:50.085 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
2022-11-10 07:38:52.210 [network debug] [00005] wait for result
2022-11-10 07:38:52.210 [network info] [00005] client connection opened 127.0.0.1
2022-11-10 07:38:52.210 [main debug] >>> info
2022-11-10 07:38:52.215 [main debug] <<< version: ebusd 22.4.v22.4
device: /dev/ttyHZG
signal: acquired
symbol rate: 22
max symbol rate: 98
m ...
2022-11-10 07:38:52.217 [network info] [00005] connection closed
2022-11-10 07:38:52.713 [mqtt debug] publish ebusd/bai/SetMode {
     "hcmode": {"value": "auto"},
     "flowtempdesired": {"value": 32.5},
     "hwctempdesired": {"value": 60.0},
     "hwcflowtempdesired": {"value": null},
     "disablehc": {"value": 0},
     "disablehwctapping": {"value": 0},
     "disablehwcload": {"value": 0},
     "remoteControlHcPump": {"value": 0},
     "releaseBackup": {"value": 0},
     "releaseCooling": {"value": 0}}
2022-11-10 07:38:53.214 [network debug] dead connection removed - 0
2022-11-10 07:38:56.110 [update info] received MS cmd: 1008b5110101 / 09383600084c620000ff
2022-11-10 07:38:56.110 [update notice] received read bai Status01 QQ=10: 28.0;27.0;8.000;38.0;49.0;off
2022-11-10 07:38:57.215 [main debug] performing regular tasks
2022-11-10 07:38:57.216 [bus info] scan 15 cmd: ff15070400
2022-11-10 07:38:57.237 [bus debug] start request ff
2022-11-10 07:38:57.237 [bus debug] arbitration start with ff
2022-11-10 07:38:57.286 [bus debug] arbitration won
2022-11-10 07:38:57.287 [bus debug] arbitration delay 2340 micros
2022-11-10 07:38:57.287 [bus debug] switching from ready to send command
2022-11-10 07:38:57.294 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:57.303 [bus debug] send/receive symbol latency 6 ms
2022-11-10 07:38:57.311 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:57.319 [bus debug] send/receive symbol latency 5 ms
2022-11-10 07:38:57.319 [bus debug] switching from send command to send command CRC
2022-11-10 07:38:57.325 [bus debug] notify request: ERR: wrong symbol received
2022-11-10 07:38:57.325 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-11-10 07:38:57.325 [main error] scan config 15: ERR: wrong symbol received
2022-11-10 07:38:57.325 [mqtt debug] publish ebusd/global/scan "running"
2022-11-10 07:38:57.326 [mqtt debug] publish ebusd/bai/Status01 {
     "0": {"name": "temp1", "value": 28.0},
     "1": {"name": "temp1", "value": 27.0},
     "2": {"name": "temp2", "value": 8.000},
     "3": {"name": "temp1", "value": 38.0},
     "4": {"name": "temp1", "value": 49.0},
     "5": {"name": "pumpstate", "value": "off"}}
2022-11-10 07:38:58.067 [update info] received BC cmd: 10feb516080057380710110422
2022-11-10 07:38:58.068 [update notice] received update-read broadcast vdatetime QQ=10: 07:38:57;10.11.2022
2022-11-10 07:38:58.325 [update info] received MS cmd: 1008b512020064 / 00
2022-11-10 07:38:58.325 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-10 07:38:59.326 [main debug] performing regular tasks
2022-11-10 07:38:59.326 [mqtt debug] publish ebusd/global/scan "finished"
2022-11-10 07:38:59.326 [mqtt debug] publish ebusd/bai/StatusCirPump {
     "0": {"name": "", "value": "on"}}
2022-11-10 07:38:59.326 [mqtt debug] publish ebusd/broadcast/vdatetime {
     "time": {"value": "07:38:57"},
     "date": {"value": "10.11.2022"}}
2022-11-10 07:39:00.110 [update info] received MS cmd: 1008b5100900004178ffff000000 / 0101
2022-11-10 07:39:00.110 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0

[Physman]

Gerade mit einem einfachen Multimeter die ebus Spannung am Esera Adapter gemessen, überiwegend 21V bis auf wenn Signale kommen, dann geht es runter (nicht messbar mit dem Voltmeter).

Passt das so?

[lewej]

Hallo zusammen,

Ich habe folgendes System:
Vaillant geotherm vwl 81/3s.

Ebusd Adapter 2.0 der ohne Poti.

Ich kann meine Heizung auslesen und steuern. Alles funktioniert Super.
Jetzt kommt aber mein Problem. Sobald der ebusd Adapter an der geotherm hängt, funktioniert die Anlage 1W manchmal länger. Irgendwann verliert aber die Innenstation die Verbindung zur Aussenstation.
Zuerst dachte ich, ja kommt schon mal vor und hab mir erstmal nichts dabei gedacht.

Jetzt konnte ich aber feststellen, das es 100% am ebus Adapter liegt. Wenn ich diesen wieder entferne, funktioniert die Anlage zu 100%, seit einem Jahr kein einziger Ausfall.

Da wir eine PV Anlage bekommen, will ich den ebus Adapter wieder Inbetriebnehmen, damit ich meinen PV Überschuss in die Heizung einspeisen kann.

ebusd läuft wie folgt:

EBUSD_OPTS2="-d 192.168.10.46:8890 -p 8889 --latency=20000 --pidfile=/var/run/ebusdgeotherm.pid --logfile=/var/log/ebusd/ebusdgeotherm -c /etc/ebusd --scanconfig=full --pollinterval=300 --mqtthost=localhost --mqttport=1883  --mqttjson --mqtttopic=ebusdgeotherm/%circuit/%name"

Was mir aufgefallen ist, das der Adapter immer wieder das signal verliert.

020-01-11 08:55:01.038 [bus error] signal lost
2020-01-11 08:55:31.048 [bus error] signal lost
2020-01-11 08:58:27.071 [bus error] signal lost
2020-01-11 09:01:03.055 [bus error] signal lost
2020-01-11 09:03:33.027 [bus error] signal lost
2020-01-11 09:06:14.033 [bus error] signal lost
2020-01-11 09:07:44.018 [bus error] signal lost
2020-01-11 09:07:50.054 [bus error] signal lost
2020-01-11 09:08:14.031 [bus error] signal lost
2020-01-11 09:09:16.059 [bus error] signal lost
2020-01-11 09:13:36.040 [bus error] signal lost
2020-01-11 09:21:18.051 [bus error] signal lost
2020-01-11 09:23:19.022 [bus error] signal lost
2020-01-11 09:24:49.030 [bus error] signal lost
2020-01-11 09:25:39.013 [bus error] signal lost
2020-01-11 09:26:19.027 [bus error] signal lost
2020-01-11 09:28:50.029 [bus error] signal lost
2020-01-11 09:32:21.068 [bus error] signal lost
2020-01-11 09:32:41.053 [bus error] signal lost
2020-01-11 09:38:30.010 [bus error] signal lost
2020-01-11 09:42:54.037 [bus error] signal lost
2020-01-11 09:46:25.039 [bus error] signal lost
2020-01-11 09:50:46.009 [bus error] signal lost
2020-01-11 09:51:16.004 [bus error] signal lost
2020-01-11 09:51:35.014 [bus error] signal lost
2020-01-11 09:54:47.068 [bus error] signal lost
2020-01-11 09:57:48.050 [bus error] signal lost
2020-01-11 09:59:58.036 [bus error] signal lost
2020-01-11 10:00:18.063 [bus error] signal lost
2020-01-11 10:02:29.037 [bus error] signal lost
2020-01-11 10:03:19.042 [bus error] signal lost
2020-01-11 10:04:19.017 [bus error] signal lost
2020-01-11 10:11:51.061 [bus error] signal lost
2020-01-11 10:13:22.014 [bus error] signal lost
2020-01-11 10:16:23.017 [bus error] signal lost
2020-01-11 11:08:43.053 [bus error] signal lost
2020-01-11 11:12:07.000 [bus error] signal lost
2020-01-11 11:12:47.040 [bus error] signal lost
2020-01-11 11:13:47.053 [bus error] signal lost
2020-01-11 11:14:48.023 [bus error] signal lost
2020-01-11 11:15:48.052 [bus error] signal lost
2020-01-11 11:16:18.005 [bus error] signal lost
2020-01-11 11:16:48.010 [bus error] signal lost
2020-01-11 11:17:39.023 [bus error] signal lost
2020-01-11 11:19:49.039 [bus error] signal lost
2020-01-11 11:21:52.040 [bus error] signal lost
2020-01-11 12:04:14.023 [bus error] signal lost
2020-01-11 12:05:31.016 [bus error] signal lost
2020-01-11 12:07:01.012 [bus error] signal lost
2020-01-11 12:08:20.052 [bus error] signal lost
2020-01-11 12:09:41.069 [bus error] signal lost
2020-01-28 21:32:17.507 [mqtt error] communication error: connection lost

Hat jemand eine Idee oder ähnliche Probleme schon gehabt?

VG

[Johannes2]

Hallo,

ausdrücklich möchte ich mit bei allen hier im Thread bedanken. Ganz besonders bei @Reinhart, @john30, @zentis666 und @Reini88

Adapter V1.6
Obwohl schon etwas "angestaubt" habe ich mir eBus-Adapter-Platinen V1.6 bei einem deutschen Platinenfertiger herstellen lassen.

Grund:
Ich konnte es zeitlich nicht aushalten bis die V3.1 wieder verfügbar sind. Vorteil ohnehin: Diese V1.6 Platine kann ich mit meinem 15W Lötkolben selbst zusammen bauen, da keine SMD Bauteile drauf kommen.

Ablauf
Nachdem sowohl von Reichelt die Bauteile, als auch die Platine vom Platinenfertiger innerhalb weniger Tage angekommen sind, habe ich mir gestern am Samstag Zeit genommen und bin das Projekt angegangen. Tatsächlich habe ich es auf meine alten Tage geschafft den eBus Adapter und den eBus-Deamon auf einem Raspberry 3B+ zusammenzubauen, zu installieren und konfiguriert zu bekommen. Ich bin stolz auf mich, aber vor allem bin ich stolz auf Euch, welche seit Jahren ein so tolles Projekt voranbringen.

Dokumentation
Hauptsächlich bin ich nach diesem Threat "eBus Schaltung in Betrieb nehmen" und auch dem FHEM EBUS Wiki https://wiki.fhem.de/wiki/EBUS vorgegangen. Natürlich habe ich auch in die neueren Threads reingeschaut.

Hinweise, welche anderen vielleicht schneller auf die Sprünge helfen:

FTDI:
Als FTDI Modul habe ich mir von eBay dieses hier geholt: FT232RL FTDI Mini USB zu TTL Serien Adapter Modul 3.3V / 5 V https://www.ebay.de/itm/223727784474
Das funktioniert super. Das hat für RX und TX separate LEDs drauf. Auch für Power vom USB ist eine LED zur Kontrolle drauf.
RX und TX müssen zwischen FTDI Adapter und eBus-Adapter nicht getauscht werden. Da hatte ich etwas gehadert.

Widerstand R6 > [main error] scan config 08: ERR: arbitration lost
Als ich feststellte, dass später nach dem Abgleichen über das feine Potentiometer (gar nicht so schwer) die eBus Nachrichten zwar empfangen, aber Nachrichten nicht gesendet wurden, musste ich noch den R6 von 22k auf 10k austauschen.

Diesen Tipp hatte ich auch hier aus dem Threat mit Nachricht #1634 am: 25 August 2020, 15:58:50 https://forum.fhem.de/index.php/topic,46098.1634.html

Nach dem Austausch funktionierte das auch prima. Geäußert hat sich das "Nichtsenden" damit, dass der ebusd die Konfig nicht automatisch laden konnte.

Das äußerte sich mit diesen : "[main error] scan config 08: ERR: arbitration lost" Nachrichten

Code Auswählen Erweitern


2022-12-03 19:04:24.838 [main error] scan config 08: ERR: arbitration lost
2022-12-03 19:04:24.933 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:04:34.609 [update notice] received unknown MS cmd: 1008b5110101 / 096842008040440100ff
2022-12-03 19:04:34.888 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:04:35.134 [update notice] received unknown BC cmd: 10feb516080034041903120622
2022-12-03 19:04:35.325 [main error] scan config 15: ERR: arbitration lost
2022-12-03 19:04:35.399 [update notice] received unknown MS cmd: 1008b5110102 / 05033c964664
2022-12-03 19:04:35.679 [update notice] received unknown MS cmd: 1008b5110100 / 0848031232040f0001
2022-12-03 19:04:35.899 [update notice] received unknown BC cmd: 10feb51603012c02
2022-12-03 19:04:44.619 [update notice] received unknown MS cmd: 1008b5110101 / 096c46008040440100ff
2022-12-03 19:04:44.902 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:04:54.609 [update notice] received unknown MS cmd: 1008b5110101 / 09724a008040440100ff
2022-12-03 19:04:54.892 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:05:04.606 [update notice] received unknown MS cmd: 1008b5110101 / 09764c008040440000ff
2022-12-03 19:05:04.798 [main error] scan config 08: ERR: arbitration lost
2022-12-03 19:05:04.893 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:05:05.157 [update notice] received unknown MS cmd: 1008b5110102 / 05033c964664
2022-12-03 19:05:14.605 [update notice] received unknown MS cmd: 1008b5110101 / 096e50008040440000ff
2022-12-03 19:05:14.885 [update notice] received unknown MS cmd: 1008b5100900006b78ffff040000 / 0101
2022-12-03 19:05:24.592 [update notice] received unknown MS cmd: 1008b5110101 / 096250008042440000ff
2022-12-03 19:05:24.782 [main error] scan config 15: ERR: arbitration lost


Jetzt läufts in den Basics.

Code Auswählen Erweitern


pi@ebusd:~ $ ebusctl info
version: ebusd 22.4.v22.4
update check: OK
device: /dev/ttyUSB0
access: *
signal: acquired
symbol rate: 22
max symbol rate: 141
min arbitration micros: 363
max arbitration micros: 586
min symbol latency: 5
max symbol latency: 6
reconnects: 0
masters: 4
messages: 652
conditional: 0
poll: 0
update: 10
address 00: master #1
address 03: master #11
address 05: slave #1, scanned "MF=Vaillant;ID=VR921;SW=2706;HW=5703"
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "vaillant/bai.0010006101.inc" ([PROD='']), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=BASV2;SW=0507;HW=1704", loaded "vaillant/15.basv.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd


Nun mache ich mich mal an MQTT, FHEM und meinen VZLOGGER, Volkszähler.

Danke noch mal an Alle,

Gruß
Johannes

[mwolle]

Ich hätte hier auch eine Frage, bzgl. der Momentanen Leistung:

Code Auswählen Erweitern

ebusctl i
version: ebusd 22.4.v22.4-57-g5d3c6f09
update check: revision v22.4 available, vaillant/08.bai.csv: newer version available
device: tcp:192.168.178.126:5000
access: *
signal: acquired
symbol rate: 39
max symbol rate: 330
min arbitration micros: 2
max arbitration micros: 1996
min symbol latency: 3
max symbol latency: 62
reconnects: 11
masters: 3
messages: 757
conditional: 9
poll: 1
update: 12
address 03: master #11
address 04: slave #25, ebusd
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "vaillant/bai.0010006101.inc" ([PROD='']), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=UI   ;SW=0501;HW=6201", loaded "vaillant/15.ui.csv"
address 23: slave, scanned "MF=Vaillant;ID=SOLSY;SW=0500;HW=6301", loaded "vaillant/23.solsy.cc.csv"
address 25: slave, scanned "MF=Vaillant;ID=SOLSY;SW=0500;HW=6301", loaded "vaillant/25.solsy.hwc.csv"
address 26: slave, scanned "MF=Vaillant;ID=SOLSY;SW=0500;HW=6301", loaded "vaillant/26.solsy.hc.csv"
address 50: slave, scanned "MF=Vaillant;ID=SOLSY;SW=0500;HW=6301", loaded "vaillant/50.solsy.mc.csv"
address ec: slave, scanned "MF=Vaillant;ID=SOLSY;SW=0500;HW=6301", loaded "vaillant/ec.solsy.sc.csv"
address ff: master #25, ebusd

nun möchte ich die Momentan Leistung eigentlich haben, nach Recherche habe ich folgende Diskussionen dazu gefunden:
Einerseits über:

Code Auswählen Erweitern


bai PartloadHcKW = no data stored
bai ModulationTempDesired = no data stored

Aber das ist nur die maximale Heizlast in kW und die minimale Modulation in % als Dauerwert. Damit kann ich also am Ende nur auslesen, welche Minimalleistung die Therme kann. Dann gibt es noch diesen Wert:

Code Auswählen Erweitern


bai PowerValue = no data stored

Hier bekomme ich aber nur diesen Wert

Code Auswählen Erweitern


ebusctl r -f PowerValue
1b 04 58 0e 64 10


Das sagt mir gar nichts weiter...könnte das aber der gewünschte Wert sein, und dieser ist noch nicht übersetzt? Oder suche ich falsch für die Momentanleistung?

[mirror]

Zu PowerValue kann ich auch nichts sagen, kriege ähnliche Byte Folge.
Die Darstellung der aktuellen Leistung mache ich auf 2 Arten, userReading aus Temp differenz Vorlauf / Rücklauf und Durchfluß sowie mit current Power vom Gaszaehler Modul. Sieht plausibel aus - man sieht schon Verluste.
Hier das userReading:

Code Auswählen Erweitern

attr Vorlauf userReadings Leistung {sprintf("%.2f kW",maxNum((ReadingsNum($NAME, "Vorlauf",0)-ReadingsNum("Ruecklauf","Ruecklauf",0)),0)*ReadingsNum("Durchfluss","Durchfluss",0)*60/860)}


[Damian]

Nun mache ich mich mal an MQTT, FHEM und meinen VZLOGGER, Volkszähler.

Ich habe mir damals auch eine 1.6 Platine besorgt, die war allerdings schon zusammengelötet. Bald entstand der Wunsch alle wichtigen (und unwichtigen) Informationen auszulesen und zu visualisieren.

Das Ergebnis habe ich hier zusammengetragen:

https://wiki.fhem.de/wiki/DOIF/uiTable_Schnelleinstieg#Visualisierung_und_Steuerung:_Heiztherme

Vielleicht ist das für dich interessant, vor allem, da es auch ein Vaillant-Gerät ist.

[Damian]

Ich hätte hier auch eine Frage, bzgl. der Momentanen Leistung:
Aber das ist nur die maximale Heizlast in kW und die minimale Modulation in % als Dauerwert. Damit kann ich also am Ende nur auslesen, welche Minimalleistung die Therme kann. Dann gibt es noch diesen Wert:

Code Auswählen Erweitern


bai PowerValue = no data stored

Hier bekomme ich aber nur diesen Wert

Code Auswählen Erweitern


ebusctl r -f PowerValue
1b 04 58 0e 64 10


Das sagt mir gar nichts weiter...könnte das aber der gewünschte Wert sein, und dieser ist noch nicht übersetzt? Oder suche ich falsch für die Momentanleistung?

Hier meine Definition inklusive PowerValue:

Code Auswählen Erweitern

defmod vaillant MQTT2_DEVICE ebusd_bai
attr vaillant IODev MQTT2_FHEM_Server
attr vaillant devStateStyle style="text-align:left"
attr vaillant event-on-change-reading .*
attr vaillant group Therme
attr vaillant icon sani_boiler_temp
attr vaillant jsonMap Status01_0_value:Vorlauf Status01_0_name:0\
Status01_1_value:Ruecklauf Status01_1_name:0\
Status01_2_value:Aussentemp Status01_2_name:0\
Status01_3_value:Warmwasser Status01_3_name:0\
Status01_4_value:WWSpeicher Status01_4_name:0\
Status01_5_value:Pumpenstatus Status01_5_name:0\
Flame_0_value:Flame Flame_0_name:0\
Storageloadpump_percent0_value:Storageloadpump\
HwcTempDesired_tempv_value:WarmwasserSollTemp\
FlowTempDesired_temp_value:VorlaufSoll\
Hc1HeatCurve_0_value:HeizKennlinie Hc1HeatCurve_0_name:0\
HolidayEndPeriod_hto_value:FerienEnde\
HolidayStartPeriod_hfrom_value:FerienBeginn\
PumpPowerDesired_0_value:PumpenLeistungSoll PumpPowerDesired_0_name:0\
PumpPower_0_value:PumpenLeistung PumpPower_0_name:0\
PrimaryCircuitFlowrate_uin100_value:Umlaufmenge\
z1DayTemp_tempv_value:TagSolltemp\
z1NightTemp_tempv_value:NachtSolltemp\
FanSpeed_0_value:LuefterDrehzahl FanSpeed_0_name:0\
WaterPressure_pressv_value:Wasserdruck\
z1OpMode_opmode_value:Heizmodus
attr vaillant model eBus_bai_jsonmap
attr vaillant readingList ebusd/scan\x2e08/:.* { json2nameValue($EVENT) }\
ebusd/scan\x2e08/id:.* { json2nameValue($EVENT) }\
ebusd/scan\x2e15/id:.* { json2nameValue($EVENT) }\
ebusd/bai/SetMode:.* {}\
ebusd/bai/Status02:.* {}\
ebusd/bai/StatusCirPump:.* {}\
ebusd/scan\x2e15/:.* {}\
ebusd/bai/PumpHours:.* { json2nameValue($EVENT, 'PumpHours_', $JSONMAP) }\
ebusd/bai/WPPostrunTime:.* { json2nameValue($EVENT, 'WPPostrunTime_', $JSONMAP) }\
ebusd/bai/PowerValue:.* { json2nameValue($EVENT, 'PowerValue_', $JSONMAP) }\
ebusd/bai/StorageExitTemp:.* { json2nameValue($EVENT, 'StorageExitTemp_', $JSONMAP) }\
ebusd/bai/StorageTempDesired:.* { json2nameValue($EVENT, 'StorageTempDesired_', $JSONMAP) }\
ebusd/global/version:.* version\
ebusd/global/running:.* running\
ebusd/scan\x5c\x2e08/:.* { json2nameValue($EVENT, 'scan.08_', $JSONMAP) }\
ebusd/scan\x5c\x2e08/id:.* { json2nameValue($EVENT, 'id_', $JSONMAP) }\
ebusd/global/uptime:.* uptime\
ebusd/global/signal:.* signal\
ebusd/scan\x5c\x2e15/:.* { json2nameValue($EVENT, 'scan.15_', $JSONMAP) }\
ebusd/scan\x5c\x2e15/id:.* { json2nameValue($EVENT, 'id_', $JSONMAP) }\
ebusd/bai/FanSpeed:.* { json2nameValue($EVENT, 'FanSpeed_', $JSONMAP) }\
ebusd/bai/PumpPower:.* { json2nameValue($EVENT, 'PumpPower_', $JSONMAP) }\
ebusd/broadcast/vdatetime:.* { json2nameValue($EVENT, 'vdatetime_', $JSONMAP) }\
ebusd/broadcast/outsidetemp:.* { json2nameValue($EVENT, 'outsidetemp_', $JSONMAP) }\
ebusd/bai/DateTime:.* { json2nameValue($EVENT, 'DateTime_', $JSONMAP) }\
ebusd/global/updatecheck:.* updatecheck\
ebusd/bai/DCFTimeDate:.* { json2nameValue($EVENT, 'DCFTimeDate_', $JSONMAP) }\
ebusd/bai/HcPumpMode:.* { json2nameValue($EVENT, 'HcPumpMode_', $JSONMAP) }\
ebusd/bai/PumpPowerDesired:.* { json2nameValue($EVENT, 'PumpPowerDesired_', $JSONMAP) }\
ebusd/bai/HwcImpellorSwitch:.* { json2nameValue($EVENT, 'HwcImpellorSwitch_', $JSONMAP) }\
ebusd/bai/ReturnTemp:.* { json2nameValue($EVENT, 'ReturnTemp_', $JSONMAP) }\
ebusd/700/HwcStorageTempBottom:.* { json2nameValue($EVENT, 'HwcStorageTempBottom_', $JSONMAP) }\
ebusd/700/HwcTempDesired:.* { json2nameValue($EVENT, 'HwcTempDesired_', $JSONMAP) }\
ebusd/bai/FanPWMSum:.* { json2nameValue($EVENT, 'FanPWMSum_', $JSONMAP) }\
ebusd/bai/HcHours:.* { json2nameValue($EVENT, 'HcHours_', $JSONMAP) }\
ebusd/bai/HoursTillService:.* { json2nameValue($EVENT, 'HoursTillService_', $JSONMAP) }\
ebusd/bai/PumpHwcFlowNumber:.* { json2nameValue($EVENT, 'PumpHwcFlowNumber_', $JSONMAP) }\
ebusd/bai/WP:.* { json2nameValue($EVENT, 'WP_', $JSONMAP) }\
ebusd/700/WaterPressure:.* { json2nameValue($EVENT, 'WaterPressure_', $JSONMAP) }\
ebusd/bai/PrimaryCircuitFlowrate:.* { json2nameValue($EVENT, 'PrimaryCircuitFlowrate_', $JSONMAP) }\
ebusd/bai/Flame:.* { json2nameValue($EVENT, 'Flame_', $JSONMAP) }\
ebusd/bai/Storageloadpump:.* { json2nameValue($EVENT, 'Storageloadpump_', $JSONMAP) }\
ebusd/bai/Status01:.* { json2nameValue($EVENT, 'Status01_', $JSONMAP) }\
ebusd/bai/FlowTempDesired:.* { json2nameValue($EVENT, 'FlowTempDesired_', $JSONMAP) }\
ebusd/700/FrostOverRideTime:.* { json2nameValue($EVENT, 'FrostOverRideTime_', $JSONMAP) }\
ebusd/700/Hc1ActualFlowTempDesired:.* { json2nameValue($EVENT, 'Hc1ActualFlowTempDesired_', $JSONMAP) }\
ebusd/700/Hc1AutoOffMode:.* { json2nameValue($EVENT, 'Hc1AutoOffMode_', $JSONMAP) }\
ebusd/700/Hc1CircuitType:.* { json2nameValue($EVENT, 'Hc1CircuitType_', $JSONMAP) }\
ebusd/700/Hc1HeatCurve:.* { json2nameValue($EVENT, 'Hc1HeatCurve_', $JSONMAP) }\
ebusd/700/HcStorageTempBottom:.* { json2nameValue($EVENT, 'HcStorageTempBottom_', $JSONMAP) }\
ebusd/700/HcStorageTempTop:.* { json2nameValue($EVENT, 'HcStorageTempTop_', $JSONMAP) }\
ebusd/700/HolidayTemp:.* { json2nameValue($EVENT, 'HolidayTemp_', $JSONMAP) }\
ebusd/700/OpMode:.* { json2nameValue($EVENT, 'OpMode_', $JSONMAP) }\
ebusd/700/z1RoomTemp:.* { json2nameValue($EVENT, 'z1RoomTemp_', $JSONMAP) }\
ebusd/700/z1SFMode:.* { json2nameValue($EVENT, 'z1SFMode_', $JSONMAP) }\
ebusd/700/z1OpMode:.* { json2nameValue($EVENT, 'z1OpMode_', $JSONMAP) }\
ebusd/700/Time:.* { json2nameValue($EVENT, 'Time_', $JSONMAP) }\
ebusd/bai/EbusVoltage:.* { json2nameValue($EVENT, 'EbusVoltage_', $JSONMAP) }\
ebusd/bai/extWP:.* { json2nameValue($EVENT, 'extWP_', $JSONMAP) }\
ebusd/bai/FanStarts:.* { json2nameValue($EVENT, 'FanStarts_', $JSONMAP) }\
ebusd/700/z1NightTemp:.* { json2nameValue($EVENT, 'z1NightTemp_', $JSONMAP) }\
ebusd/700/z1DayTemp:.* { json2nameValue($EVENT, 'z1DayTemp_', $JSONMAP) }\
ebusd/700/HolidayStartPeriod:.* { json2nameValue($EVENT, 'HolidayStartPeriod_', $JSONMAP) }\
ebusd/700/HolidayEndPeriod:.* { json2nameValue($EVENT, 'HolidayEndPeriod_', $JSONMAP) }\
ebusd/700/z1Timer.Monday:.* { json2nameValue($EVENT, 'z1Timer.Monday_', $JSONMAP) }\
ebusd/700/z1Timer.Tuesday:.* { json2nameValue($EVENT, 'z1Timer.Tuesday_', $JSONMAP) }\
ebusd/700/z1Timer.Wednesday:.* { json2nameValue($EVENT, 'z1Timer.Wednesday_', $JSONMAP) }\
ebusd/700/z1Timer.Thursday:.* { json2nameValue($EVENT, 'z1Timer.Thursday_', $JSONMAP) }\
ebusd/700/z1Timer.Friday:.* { json2nameValue($EVENT, 'z1Timer.Friday_', $JSONMAP) }\
ebusd/700/z1Timer.Sunday:.* { json2nameValue($EVENT, 'z1Timer.Sunday_', $JSONMAP) }\
ebusd/700/z1Timer.Saturday:.* { json2nameValue($EVENT, 'z1Timer.Saturday_', $JSONMAP) }\
ebusd/bai/PrEnergyCountHc1:.* { json2nameValue($EVENT, 'PrEnergyCountHc1_', $JSONMAP) }\
ebusd/bai/PrEnergyCountHwc1:.* { json2nameValue($EVENT, 'PrEnergyCountHwc1_', $JSONMAP) }\
ebusd/bai/PrEnergySumHc1:.* { json2nameValue($EVENT, 'PrEnergySumHc1_', $JSONMAP) }\
ebusd/bai/PrEnergySumHwc1:.* { json2nameValue($EVENT, 'PrEnergySumHwc1_', $JSONMAP) }\
ebusd/bai/FanHours:.* { json2nameValue($EVENT, 'FanHours_', $JSONMAP) }\
ebusd/bai/HcHours:.* { json2nameValue($EVENT, 'HcHours_', $JSONMAP) }\
ebusd/bai/HwcHours:.* { json2nameValue($EVENT, 'HwcHours_', $JSONMAP) }\
ebusd/bai/HcStarts:.* { json2nameValue($EVENT, 'HcStarts_', $JSONMAP) }\
ebusd/bai/HwcStarts:.* { json2nameValue($EVENT, 'HwcStarts_', $JSONMAP) }\
ebusd/700/Date:.* { json2nameValue($EVENT) }\
ebusd/bai/HcPumpMode:.* { json2nameValue($EVENT) }
attr vaillant room DEVICES->MQTT2_DEVICE,Ebus
attr vaillant setList HeizKennlinie:selectnumbers,0,.1,2,1,lin ebusd/700/Hc1HeatCurve/set $EVTPART1\
TagSolltemp:selectnumbers,15,1,25,1,lin ebusd/700/z1DayTemp/set $EVTPART1\
NachtSolltemp:selectnumbers,15,1,25,1,lin ebusd/700/z1NightTemp/set $EVTPART1\
PumpenLeistungSoll:selectnumbers,0,1,8,1,lin ebusd/bai/PumpPowerDesired/set $EVTPART1\
WarmwasserSollTemp:selectnumbers,45,1,55,1,lin ebusd/700/HwcTempDesired/set $EVTPART1\
Pumpenmodus:select,1,2 ebusd/bai/HcPumpMode/set $EVTPART1
attr vaillant userReadings total_hc {ReadingsVal($name,"PrEnergySumHc1_0_value",0)/100000},\
total_hwc {ReadingsVal($name,"PrEnergySumHwc1_0_value",0)/100000},\
total_h {ReadingsVal($name,"PrEnergySumHc1_0_value",0)/100000+ReadingsVal($name,"PrEnergySumHwc1_0_value",0)/100000}

Es handelt sich bei PowerValue allerdings nur um die PumpenLeistung.

Die aktuelle "Heizleistung" kannst du einfach mit einem userReading mit differential aus dem userReading total_h (siehe oben) bestimmen.

Die Pumpenleistung sowie die Umlaufmenge (Durchfluss) lasse ich visualisieren (siehe dazu auch Post davor)