eBus Schaltung in Betrieb nehmen

Begonnen von Reinhart, 23 Dezember 2015, 15:19:45

Vorheriges Thema - Nächstes Thema

Willi_70

#1845
Hallo John,
ich glaube, Du hast mich auf die richtige Fährte gelockt. Ich habe den eBus jetzt mal den Loglevel auf Debug gestellt und Access auf *. Es scheint in der Tat daran zu liegen, dass die Arbitrierung fehlschlägt (s. Log unten).
Nachdem ich in den letzten Tagen soviel daran "verschlimmbessert" habe, wollte ich gestern nochmal abgleichen und deshalb habe ich den Abgleich wie hier beschrieben über das Netzteil durchgeführt: bei 11,99 V leuchtet die LED gerade noch nicht, bei 12,1V beginnt sie zu leuchten.
Wenn ich die so abgeglichene Schaltung mit

ebusd -f -c /tmp --logareas bus --loglevel info --lograwdata=bytes

in Betrieb nehme, dann erhalte ich folgenden Output:

2022-05-21 09:29:36.369 [bus notice] <aa
2022-05-21 09:29:36.416 [bus notice] <aa
2022-05-21 09:29:36.460 [bus notice] <aa
2022-05-21 09:29:36.505 [bus notice] <aa
2022-05-21 09:29:36.550 [bus notice] <aa
2022-05-21 09:29:36.595 [bus notice] <aa
2022-05-21 09:29:36.639 [bus notice] <aa
2022-05-21 09:29:36.682 [bus notice] <aa
2022-05-21 09:29:36.728 [bus notice] <aa
2022-05-21 09:29:36.773 [bus notice] <aa
2022-05-21 09:29:36.818 [bus notice] <aa
2022-05-21 09:29:36.863 [bus notice] <aa
2022-05-21 09:29:36.905 [bus notice] <aa
2022-05-21 09:29:36.950 [bus notice] <aa
2022-05-21 09:29:36.994 [bus notice] <aa


Hat irgendjemand noch einen Tipp, was ich versuchen könnte?

Hier nochmal ein Logauszug von heute früh:


pi@Raspi-EBus:~ $ cat /var/log/ebusd.log
2022-05-21 08:26:57.439 [main notice] ebusd 22.3.p20220508 started with auto scan on device /dev/ttyUSB0
2022-05-21 08:26:57.440 [main info] loading configuration files from https://cfg.ebusd.eu/
2022-05-21 08:26:57.630 [main info] reading templates /
2022-05-21 08:26:57.816 [main info] read templates in /
2022-05-21 08:26:57.816 [main info] reading file memory.csv
2022-05-21 08:26:58.008 [main info] successfully read file memory.csv
2022-05-21 08:26:58.008 [main info] reading file broadcast.csv
2022-05-21 08:26:58.202 [main info] successfully read file broadcast.csv
2022-05-21 08:26:58.202 [main info] read config files, got 11 messages
2022-05-21 08:26:58.205 [bus notice] bus started with own address 31/36
2022-05-21 08:26:58.205 [main info] registering data handlers
2022-05-21 08:26:58.205 [main info] registered data handlers
2022-05-21 08:26:58.218 [bus debug] ERR: SYN received during no signal, switching to ready
2022-05-21 08:26:58.218 [bus notice] signal acquired
2022-05-21 08:27:01.050 [bus notice] new master 10, master count 2
2022-05-21 08:27:01.117 [bus notice] new master 03, master count 3
2022-05-21 08:27:01.117 [update info] received MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:01.117 [update notice] received unknown MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:01.396 [update info] received MS cmd: 1008b5100900003d78ffff000000 / 0101
2022-05-21 08:27:01.396 [update notice] received unknown MS cmd: 1008b5100900003d78ffff000000 / 0101
2022-05-21 08:27:08.206 [main debug] performing regular tasks
2022-05-21 08:27:08.206 [bus info] scan 08 cmd: 3108070400
2022-05-21 08:27:08.252 [bus debug] start request 31
2022-05-21 08:27:08.252 [bus debug] arbitration start with 31
2022-05-21 08:27:11.055 [bus debug] arbitration lost
2022-05-21 08:27:11.055 [bus debug] ERR: arbitration lost during ready, retry
2022-05-21 08:27:11.147 [update info] received MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:11.147 [update notice] received unknown MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:11.147 [bus debug] start request 31
2022-05-21 08:27:11.148 [bus debug] arbitration start with 31
2022-05-21 08:27:11.333 [bus debug] arbitration lost
2022-05-21 08:27:11.334 [bus debug] ERR: arbitration lost during ready, retry
2022-05-21 08:27:11.425 [update info] received MS cmd: 1008b5100900003d78ffff000000 / 0101
2022-05-21 08:27:11.425 [update notice] received unknown MS cmd: 1008b5100900003d78ffff000000 / 0101
2022-05-21 08:27:11.425 [bus debug] start request 31
2022-05-21 08:27:11.426 [bus debug] arbitration start with 31
2022-05-21 08:27:21.122 [bus debug] arbitration lost
2022-05-21 08:27:21.122 [bus debug] ERR: arbitration lost during ready, retry
2022-05-21 08:27:21.214 [update info] received MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:21.214 [update notice] received unknown MS cmd: 1008b5110101 / 0970ffc00e00720000ff
2022-05-21 08:27:21.215 [bus debug] start request 31
2022-05-21 08:27:21.215 [bus debug] arbitration start with 31
2022-05-21 08:27:21.403 [bus debug] arbitration lost
2022-05-21 08:27:21.403 [bus debug] notify request: ERR: arbitration lost
2022-05-21 08:27:21.403 [main error] scan config 08: ERR: arbitration lost

Willi_70

#1846
Hallo zusammen,
ich bin derzeit einen kleinen (sehr sehr kleinen) Schritt weiter gekommen, habe aber dennoch etliche Fragen.
Mir haben die Einträge #892 und #893 in diesem Thread weiter geholfen.

Ich habe das Poti auf meiner Platine auf 12V wie im allerersten Beitrag in diesem Thread abgeglichen (bei 11.96V leuchtet die LED nicht, bei 12,03V beginnt sie zu leuchten). Die Spannung habe ich mittels eines 330 Ohm Hochlastwiderstandes direkt an der eBus-Adapter-Platine angelegt und auch direkt dort gemessen (kein eBus der Heizungsanlage angeschlossen; Rx auf Rx und Tx auf Tx, kein Crossover).

Ich habe dann den Adapter mit der Leitung angeschlossen, an der sonst das Internetmodul hängt (um ggfs. Leitungsprobleme auszuschließen).
Danach habe ich mit ebusd -f -c /tmp --logareas bus --loglevel info --lograwdata=bytes im Terminal nachgeschaut, ob ich die "aa" Einträge sehe (vorher den laufenden ebusd-Prozess gestoppt).
Die "aa" Einträge waren vorhanden, allerdings habe ich davor immer ein "<". Wenn ich den Eintrag #893 richtig gelesen habe, dann ist das ein Anzeichen dafür, dass Daten empfangen werden. Ich kann beim besten Willen kein ">" Zeichen vor den Daten bekommen (selbst dann nicht, wenn andere Zeichenketten als "aa" ausgegeben werden).
Übrigens kommen die "aa" Einträge über einen seeeehhhhrrr weiten Bereich im Poti, das bedeutet: egal, wie ich das Poti stelle, "aa" erscheint nahezu immer (ich muss dann regelmäßig wieder auf 12V abgleichen).

Wenn ich dann ebusd erneut starte und danach die Heizung aus- und wieder einschalten (Danke an Eintrag #892 ;)), dann erscheint nach einer Weile (ein paar Minuten muss ich immer warten) folgender Eintrag nach "ebusctl info":


pi@Raspi-EBus:~ $ ebusctl info
version: ebusd 22.3.p20220508
device: /dev/ttyUSB0
signal: acquired
symbol rate: 23
max symbol rate: 95
reconnects: 0
masters: 3
messages: 225
conditional: 3
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0707;HW=7401", loaded "vaillant/bai.308523.inc" ([HW=7401]), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2
address 31: master #8, ebusd
address 36: slave #8, ebusd


Das bedeutet - wenn ich das richtig interpretiere - dass schon mal ein Gerät gefunden und auch eine Konfigurationsdatei eingelesen wird (ich lade die Konfig vom ebusd.eu, nicht aus lokaler Konfiguration; Latenz=20).

Jedoch kann ich nur einige Daten auslesen, gerade die Heizungsspezifischen Daten werden immer mit einem "ERR: arbitration lost" quittiert:


pi@Raspi-EBus:~ $ ebusctl read outsidetemp
12.875

pi@Raspi-EBus:~ $ ebusctl read StorageTemp
ERR: arbitration lost


Im Log steht folgendes:


2022-05-29 15:42:45.423 [update info] received MS cmd: 1008b5110101 / 0964ff100d00684400ff
2022-05-29 15:42:45.424 [update notice] received read bai Status01 QQ=10: 50.0;-;13.062;0.0;52.0;68
2022-05-29 15:42:45.424 [bus debug] start request 31
2022-05-29 15:42:45.424 [bus debug] arbitration start with 31
2022-05-29 15:42:45.611 [bus debug] arbitration lost
2022-05-29 15:42:45.611 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 15:42:45.704 [update info] received MS cmd: 1008b5100900000078ffff010000 / 0101
2022-05-29 15:42:45.705 [update notice] received update-write bai SetMode QQ=10: auto;0.0;60.0;-;1;0;0;0;0;0
2022-05-29 15:42:45.705 [bus debug] start request 31
2022-05-29 15:42:45.706 [bus debug] arbitration start with 31
2022-05-29 15:42:45.892 [bus debug] arbitration lost
2022-05-29 15:42:45.892 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 15:42:45.986 [update info] received MS cmd: 1008b5040100 / 0a0348421529050722100d
2022-05-29 15:42:45.987 [update notice] received read bai DateTime QQ=10: valid;15:42:48;29.05.2022;13.062
2022-05-29 15:42:45.987 [bus debug] start request 31
2022-05-29 15:42:45.987 [bus debug] arbitration start with 31
2022-05-29 15:42:46.174 [bus debug] arbitration lost
2022-05-29 15:42:46.174 [bus debug] notify request: ERR: arbitration lost
2022-05-29 15:42:46.174 [main error] scan config 15: ERR: arbitration lost
2022-05-29 15:42:46.174 [main debug] >>> read outsidetemp
2022-05-29 15:42:46.174 [main info] read broadcast outsidetemp cached: 12.875
2022-05-29 15:42:46.174 [main debug] <<< 12.875
2022-05-29 15:42:46.175 [network info] [00009] connection closed
2022-05-29 15:42:46.248 [update info] received MS cmd: 1008b5110102 / 05033c965074
2022-05-29 15:42:46.249 [update notice] received read bai Status02 QQ=10: auto;60;75.0;80;58.0
2022-05-29 15:42:46.491 [update info] received BC cmd: 10feb516080046421529050722
2022-05-29 15:42:46.491 [update notice] received update-read broadcast vdatetime QQ=10: 15:42:46;29.05.2022
2022-05-29 15:42:46.761 [update info] received MS cmd: 1008b5110100 / 082b0315c818370080
2022-05-29 15:42:46.761 [update notice] received unknown MS cmd: 1008b5110100 / 082b0315c818370080
2022-05-29 15:42:46.979 [update info] received BC cmd: 10feb5160301e00c
2022-05-29 15:42:46.980 [update notice] received update-read broadcast outsidetemp QQ=10: 12.875
2022-05-29 15:42:47.020 [network debug] dead connection removed - 0


und

2022-05-29 16:00:52.385 [main debug] performing regular tasks
2022-05-29 16:00:54.447 [network info] [00011] client connection opened 127.0.0.1
2022-05-29 16:00:54.447 [main debug] >>> read StorageTemp
2022-05-29 16:00:54.447 [bus info] send message: 3108b509030d1700
2022-05-29 16:00:54.447 [network debug] [00011] wait for result
2022-05-29 16:00:54.472 [bus debug] start request 31
2022-05-29 16:00:54.472 [bus debug] arbitration start with 31
2022-05-29 16:01:00.163 [bus debug] arbitration lost
2022-05-29 16:01:00.163 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:00.257 [update info] received MS cmd: 1008b5110101 / 0988ffe00c00760000ff
2022-05-29 16:01:00.258 [update notice] received read bai Status01 QQ=10: 68.0;-;12.875;0.0;59.0;off
2022-05-29 16:01:00.258 [bus debug] start request 31
2022-05-29 16:01:00.258 [bus debug] arbitration start with 31
2022-05-29 16:01:00.446 [bus debug] arbitration lost
2022-05-29 16:01:00.446 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:00.538 [update info] received MS cmd: 1008b5100900004378ffff000000 / 0101
2022-05-29 16:01:00.539 [update notice] received update-write bai SetMode QQ=10: auto;33.5;60.0;-;0;0;0;0;0;0
2022-05-29 16:01:00.539 [bus debug] start request 31
2022-05-29 16:01:00.539 [bus debug] arbitration start with 31
2022-05-29 16:01:10.228 [bus debug] arbitration lost
2022-05-29 16:01:10.228 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:10.319 [update info] received MS cmd: 1008b5110101 / 0988ffe00c00760000ff
2022-05-29 16:01:10.320 [update notice] received read bai Status01 QQ=10: 68.0;-;12.875;0.0;59.0;off
2022-05-29 16:01:10.321 [bus debug] start request 31
2022-05-29 16:01:10.321 [bus debug] arbitration start with 31
2022-05-29 16:01:10.505 [bus debug] arbitration lost
2022-05-29 16:01:10.505 [bus debug] notify request: ERR: arbitration lost
2022-05-29 16:01:10.505 [bus error] send to 08: ERR: arbitration lost, retry
2022-05-29 16:01:10.596 [update info] received MS cmd: 1008b5100900004378ffff000000 / 0101
2022-05-29 16:01:10.597 [update notice] received update-write bai SetMode QQ=10: auto;33.5;60.0;-;0;0;0;0;0;0
2022-05-29 16:01:10.598 [bus debug] start request 31
2022-05-29 16:01:10.598 [bus debug] arbitration start with 31
2022-05-29 16:01:20.245 [bus debug] arbitration lost
2022-05-29 16:01:20.246 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:20.338 [update info] received MS cmd: 1008b5110101 / 0988ffe00c00760000ff
2022-05-29 16:01:20.338 [update notice] received read bai Status01 QQ=10: 68.0;-;12.875;0.0;59.0;off
2022-05-29 16:01:20.339 [bus debug] start request 31
2022-05-29 16:01:20.339 [bus debug] arbitration start with 31
2022-05-29 16:01:20.523 [bus debug] arbitration lost
2022-05-29 16:01:20.523 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:20.563 [bus debug] ERR: SYN received during receive command, switching to ready
2022-05-29 16:01:20.607 [bus debug] start request 31
2022-05-29 16:01:20.607 [bus debug] arbitration start with 31
2022-05-29 16:01:20.791 [bus debug] arbitration lost
2022-05-29 16:01:20.791 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:20.883 [update info] received MS cmd: 1008b5100900004378ffff000000 / 0101
2022-05-29 16:01:20.883 [update notice] received update-write bai SetMode QQ=10: auto;33.5;60.0;-;0;0;0;0;0;0
2022-05-29 16:01:20.884 [bus debug] start request 31
2022-05-29 16:01:20.884 [bus debug] arbitration start with 31
2022-05-29 16:01:21.071 [bus debug] arbitration lost
2022-05-29 16:01:21.071 [bus debug] notify request: ERR: arbitration lost
2022-05-29 16:01:21.071 [bus error] send to 08: ERR: arbitration lost, retry
2022-05-29 16:01:21.144 [update info] received MS cmd: 1008b5110102 / 05033c965074
2022-05-29 16:01:21.144 [update notice] received read bai Status02 QQ=10: auto;60;75.0;80;58.0
2022-05-29 16:01:21.145 [bus debug] start request 31
2022-05-29 16:01:21.145 [bus debug] arbitration start with 31
2022-05-29 16:01:30.292 [bus debug] arbitration lost
2022-05-29 16:01:30.292 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:30.380 [update info] received MS cmd: 1008b5110101 / 0988ffe00c00760000ff
2022-05-29 16:01:30.381 [update notice] received read bai Status01 QQ=10: 68.0;-;12.875;0.0;59.0;off
2022-05-29 16:01:30.382 [bus debug] start request 31
2022-05-29 16:01:30.382 [bus debug] arbitration start with 31
2022-05-29 16:01:30.566 [bus debug] arbitration lost
2022-05-29 16:01:30.566 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:30.658 [update info] received MS cmd: 1008b5100900004378ffff000000 / 0101
2022-05-29 16:01:30.659 [update notice] received update-write bai SetMode QQ=10: auto;33.5;60.0;-;0;0;0;0;0;0
2022-05-29 16:01:30.659 [bus debug] start request 31
2022-05-29 16:01:30.659 [bus debug] arbitration start with 31
2022-05-29 16:01:40.341 [bus debug] arbitration lost
2022-05-29 16:01:40.341 [bus debug] ERR: arbitration lost during ready, retry
2022-05-29 16:01:40.431 [update info] received MS cmd: 1008b5110101 / 0988ffe00c00760000ff
2022-05-29 16:01:40.432 [update notice] received read bai Status01 QQ=10: 68.0;-;12.875;0.0;59.0;off
2022-05-29 16:01:40.432 [bus debug] start request 31
2022-05-29 16:01:40.432 [bus debug] arbitration start with 31
2022-05-29 16:01:40.621 [bus debug] arbitration lost
2022-05-29 16:01:40.621 [bus debug] notify request: ERR: arbitration lost
2022-05-29 16:01:40.621 [bus error] send to 08: ERR: arbitration lost
2022-05-29 16:01:40.621 [bus error] send message part 0: ERR: arbitration lost
2022-05-29 16:01:40.621 [main debug] <<< ERR: arbitration lost
2022-05-29 16:01:40.622 [network info] [00011] connection closed
2022-05-29 16:01:40.713 [update info] received MS cmd: 1008b5100900004378ffff000000 / 0101
2022-05-29 16:01:40.713 [update notice] received update-write bai SetMode QQ=10: auto;33.5;60.0;-;0;0;0;0;0;0
2022-05-29 16:01:41.496 [network debug] dead connection removed - 0
2022-05-29 16:01:45.622 [main debug] performing regular tasks
2022-05-29 16:01:45.622 [bus info] scan 15 cmd: 3115070400
2022-05-29 16:01:45.645 [bus debug] start request 31
2022-05-29 16:01:45.645 [bus debug] arbitration start with 31


Deshalb (fehlendes ">" vor den "aa-Einträgen" und ständig abbrechende Arbitrierung) vermute ich, dass ich tatsächlich nicht auf den Bus schreiben kann (wobei ich bislang der Meinung war, dass "Arbitrierung" lediglich die Priorität von zwei gleichzeitigen Sendern auf einem Bus regelt; insofern kommt sie - meiner bisherigen Meinung nach - ja nur zum Tragen, wenn tatsächlich gesendet wird).

Ich bin mir nicht sicher, ob ich das korrekte USB-TTL-Modul habe. Es sieht ähnlich aus, wie das im allerersten Beitrag angegebene (rot, mit einem Jumper 3,3 und 5V, ich habe den Jumper auf 5V gesteckt). Allerdings steht auf dem Chip nichts drauf, deshalb weiß ich nicht, ob es ein FTDI-Chip ist. Meine ESPs kann ich damit prima programmieren und wenn ich ihn am eBus-Adapter habe, blinken die Rx und die Tx LED fleißig.

Das war eine sehr lange Vorrede, aber ich hoffe, ihr konntet bis hierher nachvollziehen, was ich gemacht habe.
Nun habe ich noch einige Fragen und hoffe auf Euren Input:

- Wie kann ich erkennen, ob ich tatsächlich nicht auf den Bus schreiben kann?
- Falls ich nicht schreiben kann, wie kann ich unterscheiden, ob es wegen eines falsch abgestimmten Potis ist, oder ob ich ein Problem mit der Latzenzzeit habe ("setserial /dev/ttyUSB0 low_latency" habe ich schon erfolglos ausprobiert)?
- Gibt es eine Möglichkeit, das "Finetuning" inkl. "Schreib-Test auf den Bus" über den "aa-Abgleich" zu machen (wie erwähnt, bekomme ich "aa" über einen sehr weiten Stellbereich, das ist bei mir alles andere, als "Finetuning")?
- Ist die Einstellung über das Labornetzteil auf 12V korrekt, oder benötige ich für Vaillant eine andere Spannung?
- Kann es sein, dass mein USB-TTL-Modul für diese Konstellation nicht funktioniert und falls ja, welches Modul würde Eurer Erfahrung nach vermutlich funktionieren?

Da ich jetzt schon bis hierher gekommen bin, möchte ich nicht an dieser Stelle abbrechen. Ich hoffe, dass irgendjemand Antworten auf meine Fragen hat oder mir andere Tipps geben kann. Wenn ich die Antwort irgendwo hier im Forum oder im Internet finden kann, dann gebt mir bitte einen Tipp, dann schaue ich selbst nach.


Vielen Dank,
Willi

Reini88

Hallo Willi,
ich bin nicht der Experte, der deine Fragen beantworten kann. Aber ich hatte auch mal das Problem mit der 1.6er Platine, dass ich zwar vom Ebus lesen, aber nicht schreiben konnte. Die Lösung war, dass ein Widerstand geändert werden musste. Seitdem läuft mein 1.6er-Adapter fehlerfrei. Schau mal den Beitrag #1634 an.

Willi_70

Hallo Reini,
danke für Deinen Tipp. Ich habe jetzt mal einen 10K als R6 eingelötet und die Schaltung nochmal auf 12V abgeglichen. Leider bekomme ich immer noch die "arbitration lost" Einträge im Log. Ich vermute, ich kann immer noch nicht auf den Bus schreiben.
Allerdings macht mir Dein Tipp Mut, weiter nach der Fehlerquelle zu suchen. Es gibt also noch Ansatzpunkte, um die Schaltung doch noch zum Fliegen zu bekommen, das macht Mut.
Mal sehen, ob ich es irgendwie doch noch hinbekomme. Werde morgen mal wieder Poti-Drehübungen machen...

Willi_70

#1849
Hallo zusammen,
ich habe jetzt nochmal komplett bei Null begonnen (sozusagen "total reset") und mir eine zweite Platine besorgt, nochmal alle Bauteile gem. Wiki-Link zur Einkaufsliste bestellt und beide Platinen identisch mit den neuen Bauteilen aufgebaut. Danach habe ich die Schaltung auf 12V abgeglichen und beide jeweils an den eBus der Heizung angeklemmt (der Abgleich auf "aa" passte auf Anhieb). In beiden Fällen wird die Therme erkannt, wenn ich sie - nachdem ich den Raspi gestartet habe und der ebusd läuft - nochmal aus- und einschalte. Ich kann bestimmte Werte auslesen (s. IMG_0997).
Deshalb gehe ich davon aus, dass das Poti richtig eingestellt ist (ich habe hier im Thread gelesen, dass das Poti zur Rx-Einstellung dient und mit dem Senden nix zu tun hat).
Beim Senden bekomme ich aber immer noch "arbitration lost" Einträge zu Hauf. Wenn ich ebusd z. B. starte, ohne dass ich anschließend die Therme aus- und wieder einschalte, dann kommt der "Scan-Sendebefehl", aber anschließend bricht die Arbitrierung wieder ab (s. IMG_1010). Das passiert ständig und bei allen Sendebefehlen.
Ich habe daraufhin mal die Z-Diode und den Darlington-Transistor mit einem Multimeter gemessen (wie hier im Thread empfohlen), die scheinen (laut Multimeter) in Ordnung zu sein (die Messwerte kann ich auch an noch nicht verbauten Bauteilen nachvollziehen). Selbst Optokoppler und NAND-Gatter habe ich schon getauscht (ohne Erfolg). Zudem habe ich den Versuch mit dem 10K statt 22K Widerstand an der Basis des Transistors unternommen. Alles erfolglos. Irgendwo hier im Forum habe ich gelesen, dass man ggfs. einen CNY17-4 statt 17-1 verwenden solle (wegen der Flankensteilheit?). Das habe ich im Sendeweg versucht, klappte aber nicht.
Nun habe ich mal alles wieder auf Originalzustand mit neuen Bauteilen zurückgebaut und die Spannungen im Sendeweg (wie von Reinhart sehr gut beschrieben) gemessen (s. IMG_1011). Die Einspeisung habe ich über einen 330Ohm, 5Watt Widerstand auf 24V gelegt. Spannungen bei mir liegen ab dem Optokoppler alle etwas höher, allerdings in der Tendenz gleich, wie in der Beschreibung von Reinhart. Zudem habe ich in der eBus Spezifikation gelesen, dass der High-Pegel von 15 bis 24V geht, sollte also kein Problem sein, oder?
Der eBus der Heizung hat - mit einem Multimeter gemessen und bei angeschlossenem ebusd - so um die 20V, die Spannung fällt nie komplett ab.

Ich bin jetzt irgendwie mit meinem Latein am Ende. Es hat den Anschein, als ob der Adapter senden will, aber die Arbitrierung immer wieder fehlschlägt (so als ob da ein Türsteher ist, der sagt "Du kommst hier nicht rein").

Ach ja:
- ebusd-Version:
pi@Raspi-EBus:~ $ ebusd --version
ebusd 22.3.p20220508
- Keine lokalen Konfig-Dateien
- Adapter 1.6
- Diverse FTDI-Adapter ausprobiert (alle funktionieren mit ESPs)
- Raspi 3B+
- Latzenzzeit: 0 (ich habe auch mit anderen Latenzzeiten "rumgespielt", konnte aber keine Veränderung bzgl. der Arbitrierung erkennen)

Hat vielleicht irgendjemand von Euch noch einen Tipp für mich? Ich bin wirklich ratlos...

Viele Grüße,
Willi

baumhous3

Zitat von: john30 am 16 April 2022, 07:37:50
im Protokoll ist zu sehen, dass ebusd.service fehlschlägt, nicht -2 und nicht -3, also musst Du schon in der Datei nachschauen und editieren.

Ich bin nun auf die ebusd.service gegangen, die liegt untern /lib/systemd/system/ebusd.service
Aktuell ist der Inhalt wie folgt:

[Unit]
Description=ebusd, the daemon for communication with eBUS heating systems.
After=network-online.target
ConditionPathExists=/var/log

[Service]
Type=forking
Restart=always
RestartSec=30
PIDFile=/var/run/ebusd.pid
EnvironmentFile=-/etc/default/ebusd
ExecStart=/usr/bin/ebusd $EBUSD_OPTS

[Install]
WantedBy=multi-user.target


Was muss ich dort denn dann konkret ändern?
Sorry für das blöd nachfragen, habe dort aber nicht so viel Ahnung von. Hoffe ihr könnt mich dort weiter unterstützen, dass ich es ans laufen bekomme.

Danke und ein schönes Wochenende :)

DS_Starter

#1851
Hallo,

eine Frage an die Adapter- bzw. eBusd-Entwickler des eBUS Adapter 3 (https://adapter.ebusd.eu/).
Kann es sein, dass die Adressierung von der Koppelart (LAN bzw. USB) abhängig ist ? (siehe https://forum.fhem.de/index.php/topic,128085.msg1226648.html#msg1226648)

Es ist aufgefallen, dass bei dem TEM Steuergerät statt z.B. der Adresse "0AF5" die "A0F5" zu verwenden ist, d.h. beim LOW-Byte ist die Reihenfolgen der ersten vier Bits gegen die zweiten vier Bits zu tauschen. Je nachdem ob man mit USB bzw. LAN arbeitet.

Es ist auch nicht auszuschließen dass es von der Firmware des verwendeten TEM abhängt, aber in dem dargestellten Fall sind die gemeldeten Hardware / Software Daten (SW/HW)  zwischen meinem TEM und dem eines anderen Users identisch:


address fc: slave #20, scanned "MF=TEM;ID=PS551;SW=3178;HW=7878"


Lediglich die Koppleart ist bei mir LAN und bei ihm USB.

Könnt ihr dazu etwas erhellendes beitragen ?

LG und einen schönen Sonntag,
Heiko
ESXi@NUC+Debian+MariaDB, PV: SMA, Victron MPII+Pylontech+CerboGX
Maintainer: SSCam, SSChatBot, SSCal, SSFile, DbLog/DbRep, Log2Syslog, SolarForecast,Watches, Dashboard, PylonLowVoltage
Kaffeekasse: https://www.paypal.me/HMaaz
Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/DS_Starter

denni

#1852
Hallo,

ich habe die Platine V1.6 (zentis666) in Verwendung (bei Ebay) und habe die Bauteile (bei Reichelt) über den Warenkorbvorschlag gekauft.

Anbei ein paar Bilder von der gelöteten Platine. (Vorder/Rückseite)

Jetzt bei der Inbetriebnahme habe ich den R1 gemessen. R1 sollte eigentlich 1,047 V haben - Bei mir hat er aber 1,8 V.
Hat jemand eine Idee woran das liegen kann?

Anbei das Bild von meinem Messaufbau. Seht ihr einen Fehler?

danke euch. Grüße

Willi_70

Ich glaube, das war es jetzt. Das ist die erste Schaltung, vor der ich kapituliere.
Nachdem ich nun so ziemlich alles, was ich irgendwie und irgendwo an Informationen bekommen konnte ausprobiert habe, strecke ich die Waffen. Das System ist mir einfach über (man muss wissen, wann man verloren hat).
Ich hatte nochmal bei Null begonnen (s. Post #1849) und dann klappte es ja auch mit dem Lesen. Allerdings funzt das blöde Schreiben auf den Bus nach wie vor immer noch nicht. Die Meßwerte der "Sende-Seite" hatte ich auch schonmal gepostet, aber dazu hatte niemand einen Tipp.
Von John habe ich den Hinweis bekommen, dass ggfs. die Z-Diode oder der Darlington Transistor defekt sein könnten. Deshalb habe ich mir nochmal aus einer komplett anderen Quelle jeweils einen Transistor und eine Z-Diode besorgt (um Chargenfehler auszuschließen). Das, obwohl die Bauteile nach dem Durchmessen eigentlich in Ordnung sein müssten (was macht man nicht alles aus Verzweiflung...).
Allerdings hat das ebenfalls nicht dazu geführt, dass die "arbitration lost" Einträge verschwanden. Fazit: mein Adapter kann immer noch nicht auf den Bus schreiben.
Aus meiner Sicht sind zwei Monate Frustration (für meinen Geschmack) eindeutig genug, ich werde die Schaltung nun lesend weiter mitlaufen lassen, darauf hoffen, dass irgendwann (vermutlich - wenn man die aktuelle Lage anschaut - wohl in sehr sehr ferner Zukunft) mal wieder die 3-er Version verfügbar ist (reserviert habe ich ihn schon) und dann mein Glück damit erneut versuchen.
Ich möchte mich bei allen bedanken, die mir bis hierher weitergeholfen haben. Das hat mir jedesmal wieder geholfen, nicht schon viel früher "die Flinte ins Korn" zu werfen. Jetzt möchte ich Eure Hilfsbereitschaft und Geduld aber nicht weiter strapazieren.

Viele Grüße,
Willi

Schuldig

#1854
Moin,

ich habe seit fast 2 Jahren erfolgreich einen ebud Adapter V2 am RPi für meine Vaillantheizung am Laufen.

Seit heute Mittag 12:38 Uhr (siehe log) geht nicht mehr viel.

2022-08-28 12:38:06.338 [main notice] ebusd 3.4.v3.3-51-g57eae05 started with auto scan
2022-08-28 12:38:09.419 [main error] error reading config files from http://ebusd.eu/config/: ERR: element not found, last error:
2022-08-28 12:38:09.456 [bus notice] bus started with own address 31/36
2022-08-28 12:38:09.456 [bus notice] signal acquired
2022-08-28 12:38:09.602 [mqtt notice] connection established
2022-08-28 12:38:12.627 [bus notice] new master 10, master count 2
2022-08-28 12:38:12.687 [bus notice] new master 03, master count 3
2022-08-28 12:38:12.688 [update notice] received unknown MS cmd: 1008b5110101 / 093c3d101542380000ff
2022-08-28 12:38:12.982 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008000806401c87d01
2022-08-28 12:38:13.248 [update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
2022-08-28 12:38:14.029 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2022-08-28 12:38:14.277 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
2022-08-28 12:38:19.689 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2022-08-28 12:38:19.689 [update notice] store 08 ident: done
2022-08-28 12:38:19.690 [update notice] sent scan-read scan.08  QQ=31: Vaillant;BAI00;0202;9602
2022-08-28 12:38:19.690 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2022-08-28 12:38:22.762 [main error] unable to load scan config 08: list files in vaillant ERR: element not found
2022-08-28 12:38:22.762 [main error] scan config 08: ERR: element not found
2022-08-28 12:38:22.772 [update notice] received unknown MS cmd: 1008b5110101 / 093c3d101542380000ff
2022-08-28 12:38:23.067 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008000806301c87d01
2022-08-28 12:38:23.337 [update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
2022-08-28 12:38:24.116 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2022-08-28 12:38:24.363 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
2022-08-28 12:38:24.888 [bus notice] scan 15: ;Vaillant;70000;0510;6403
2022-08-28 12:38:24.888 [update notice] store 15 ident: done
2022-08-28 12:38:24.889 [update notice] sent scan-read scan.15  QQ=31: Vaillant;70000;0510;6403
2022-08-28 12:38:24.889 [bus notice] scan 15: ;Vaillant;70000;0510;6403
2022-08-28 12:38:27.958 [main error] unable to load scan config 15: list files in vaillant ERR: element not found
2022-08-28 12:38:27.958 [main error] scan config 15: ERR: element not found
2022-08-28 12:38:30.089 [bus notice] scan 52: ;Vaillant;VR_70;0109;2903
2022-08-28 12:38:30.089 [update notice] store 52 ident: done
2022-08-28 12:38:30.089 [update notice] sent scan-read scan.52  QQ=31: Vaillant;VR_70;0109;2903
2022-08-28 12:38:30.089 [bus notice] scan 52: ;Vaillant;VR_70;0109;2903
2022-08-28 12:38:32.826 [update notice] received unknown MS cmd: 1008b5110101 / 093c3d101542380000ff
2022-08-28 12:38:33.120 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008000806401c87d01
2022-08-28 12:38:33.159 [main error] unable to load scan config 52: list files in vaillant ERR: element not found
2022-08-28 12:38:33.159 [main error] scan config 52: ERR: element not found
2022-08-28 12:38:33.391 [update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
2022-08-28 12:38:33.647 [update notice] received unknown MS cmd: 1008b5110102 / 06033c82467e6e
2022-08-28 12:38:34.166 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101


Infos zum Adapter:

ebusctl info
version: ebusd 3.4.v3.3-51-g57eae05
access: *
signal: acquired
symbol rate: 23
max symbol rate: 112
min arbitration micros: 36
max arbitration micros: 56
min symbol latency: 4
max symbol latency: 4
reconnects: 0
masters: 3
messages: 3
conditional: 0
poll: 0
update: 0
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0202;HW=9602"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0510;HW=6403"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 52: slave, scanned "MF=Vaillant;ID=VR_70;SW=0109;HW=2903"


unter ebusctl find findet er nur noch drei Verzeichnisse:
scan.08  = Vaillant;BAI00;0202;9602
scan.15  = Vaillant;70000;0510;6403
scan.52  = Vaillant;VR_70;0109;2903

woran kann es liegen, dass nur noch diese drei Verzeichnisse gefunden werden und nicht wie sonst wesentlich mehr?

Ich habe weder einen Neustart gemacht, noch irgendwas am Pi verändert.

Hoffe, dass mir jemand helfen kann.

Grüße.

john30

Zitat von: Schuldig am 28 August 2022, 21:24:02
2022-08-28 12:38:06.338 [main notice] ebusd 3.4.v3.3-51-g57eae05 started with auto scan
2022-08-28 12:38:09.419 [main error] error reading config files from http://ebusd.eu/config/: ERR: element not found, last error:

habs gerade mit der uralten 3.4 probiert und kann das nicht nachvollziehen. Ist das immer noch so?
Und vielleicht magst Du mal die ebsud Version von 2019 aktualisieren...?
author of ebusd

BallaBalla

#1856
@Will_70 und Denni

Ändert mal den R6 von 22k auf 10k, das hatte bei mir nach langen "rumlaborieren" den Erfolg gebracht und der Adapter konnte endlich auch auf den Bus schreiben..
LG
Benno

Physman

#1857
Moin 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.
Nun habe ich selbiges Problem mit dem ESERA Adapter - und habe hier sehr sehr viele Seiten gelesen, als auch den Poti getrimmt bis er glühte, aber ich komme nicht weiter - leider:

Meine Ausstattung:
aurocompact VSC S 196/3-5 200 R3
Calormatic 470/3 direkt in der Therme installiert (das hat hinten 3 PINs zum einstecken in die Hauptplatine der aurpocompact
Solar auf dem Dach für Wasser
ebusd version 22.4
Bullyseye auf Raspberry PI
Esera ebusd USB adapter (ca 3m von der Therme Vaillant mit Kabel angeschlossen) mit Poti

Nach Start des ebusd und Neustart der Therme bekomme ich das Ergbniss unten.
Ohen Neustart fehlt die Adresse 15 (meine das ist die calormatic - habe es hier irgendwo gelesen).
Auch nach einer ganzen Nacht und einem Tag steht die immer noch auf "scanning".
Was kann ich noch machen?
Hat hier jemand bitte noch eine erlösende Idee für die ESERA?
ESERA habe ich angeschrieben - warte noch auf Feedback....
Ich meine hier auch gelesen zu haben, dass vermutet wurde, dass die eingesteckten Geräte gar nich sich an den ebus koppeln (war eine Vermutung). Sind ja auch 3 PINs anstatt 2. Allerdings sagt die Fachhandwerker Anleitung auch aus, dass man die calormatic 470 in den Wohnraum hängen kann, und einfach den ebus anklemmen sollte. Welche PINs wird nicht beschrieben....

root@raspberrypi:/home/raspberry.dirk# ebusctl info
version: ebusd 22.4.v22.4
device: /dev/ttyHZG
access: *
signal: acquired
symbol rate: 41
max symbol rate: 98
min arbitration micros: 583
max arbitration micros: 2648
min symbol latency: 5
max symbol latency: 6
reconnects: 1
masters: 3
messages: 225
conditional: 3
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "vaillant/bai.308523.inc" ([HW=7401]), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanning
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning


Physman

Hier mal meine "aa"s

2022-11-08 07:50:22.932 [bus notice] <aa
2022-11-08 07:50:22.976 [bus notice] <aa
2022-11-08 07:50:23.021 [bus notice] <aa
2022-11-08 07:50:23.065 [bus notice] <aa
2022-11-08 07:50:23.109 [bus notice] <aa
2022-11-08 07:50:23.154 [bus notice] <aa
2022-11-08 07:50:23.198 [bus notice] <aa
2022-11-08 07:50:23.243 [bus notice] <aa
2022-11-08 07:50:23.289 [bus notice] <aa
2022-11-08 07:50:23.332 [bus notice] <aa
2022-11-08 07:50:23.378 [bus notice] <aa
2022-11-08 07:50:23.425 [bus notice] <aa
2022-11-08 07:50:23.470 [bus notice] <aa
2022-11-08 07:50:23.518 [bus notice] <aa
2022-11-08 07:50:23.563 [bus notice] <aa
2022-11-08 07:50:23.566 [bus notice] <10
2022-11-08 07:50:23.571 [bus notice] <fe
2022-11-08 07:50:23.575 [bus notice] <b5
2022-11-08 07:50:23.581 [bus notice] <16
2022-11-08 07:50:23.585 [bus notice] <08
2022-11-08 07:50:23.590 [bus notice] <00
2022-11-08 07:50:23.593 [bus notice] <25
2022-11-08 07:50:23.598 [bus notice] <50
2022-11-08 07:50:23.603 [bus notice] <07
2022-11-08 07:50:23.608 [bus notice] <08
2022-11-08 07:50:23.613 [bus notice] <11
2022-11-08 07:50:23.616 [bus notice] <02
2022-11-08 07:50:23.621 [bus notice] <22
2022-11-08 07:50:23.626 [bus notice] <ea
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
2022-11-08 07:50:23.631 [bus notice] <aa
2022-11-08 07:50:23.679 [bus notice] <aa
2022-11-08 07:50:23.724 [bus notice] <aa
2022-11-08 07:50:23.769 [bus notice] <aa
2022-11-08 07:50:23.813 [bus notice] <aa
2022-11-08 07:50:23.817 [bus notice] <10
2022-11-08 07:50:23.822 [bus notice] <08
2022-11-08 07:50:23.826 [bus notice] <b5
2022-11-08 07:50:23.831 [bus notice] <12
2022-11-08 07:50:23.835 [bus notice] <02
2022-11-08 07:50:23.840 [bus notice] <00
2022-11-08 07:50:23.845 [bus notice] <64
2022-11-08 07:50:23.849 [bus notice] <ae
2022-11-08 07:50:23.853 [bus notice] <00
2022-11-08 07:50:23.873 [bus notice] <00
2022-11-08 07:50:23.877 [bus notice] <00
2022-11-08 07:50:23.882 [bus notice] <00
2022-11-08 07:50:23.882 [update info] received MS cmd: 1008b512020064 / 00
2022-11-08 07:50:23.882 [update notice] received unknown MS cmd: 1008b512020064 / 00
2022-11-08 07:50:23.886 [bus notice] <aa
2022-11-08 07:50:23.932 [bus notice] <aa
2022-11-08 07:50:23.976 [bus notice] <aa
2022-11-08 07:50:24.020 [bus notice] <aa
2022-11-08 07:50:24.066 [bus notice] <aa
2022-11-08 07:50:24.113 [bus notice] <aa
2022-11-08 07:50:24.157 [bus notice] <aa
2022-11-08 07:50:24.208 [bus notice] <aa
2022-11-08 07:50:24.253 [bus notice] <aa
2022-11-08 07:50:24.298 [bus notice] <aa
2022-11-08 07:50:24.343 [bus notice] <aa
2022-11-08 07:50:24.387 [bus notice] <aa
2022-11-08 07:50:24.432 [bus notice] <aa
2022-11-08 07:50:24.476 [bus notice] <aa
2022-11-08 07:50:24.520 [bus notice] <aa
2022-11-08 07:50:24.564 [bus notice] <aa
2022-11-08 07:50:24.609 [bus notice] <aa
2022-11-08 07:50:24.654 [bus notice] <aa
2022-11-08 07:50:24.701 [bus notice] <aa
2022-11-08 07:50:24.745 [bus notice] <aa
2022-11-08 07:50:24.794 [bus notice] <aa
2022-11-08 07:50:24.838 [bus notice] <aa
2022-11-08 07:50:24.886 [bus notice] <aa
2022-11-08 07:50:24.930 [bus notice] <aa
2022-11-08 07:50:24.974 [bus notice] <aa
2022-11-08 07:50:25.019 [bus notice] <aa
2022-11-08 07:50:25.064 [bus notice] <aa
2022-11-08 07:50:25.109 [bus notice] <aa
2022-11-08 07:50:25.155 [bus notice] <aa
2022-11-08 07:50:25.199 [bus notice] <aa
2022-11-08 07:50:25.244 [bus notice] <aa
2022-11-08 07:50:25.288 [bus notice] <aa
2022-11-08 07:50:25.333 [bus notice] <aa
2022-11-08 07:50:25.378 [bus notice] <aa
2022-11-08 07:50:25.422 [bus notice] <aa
2022-11-08 07:50:25.469 [bus notice] <aa
2022-11-08 07:50:25.513 [bus notice] <aa
2022-11-08 07:50:25.562 [bus notice] <aa
2022-11-08 07:50:25.567 [bus notice] <10
2022-11-08 07:50:25.571 [bus notice] <08
2022-11-08 07:50:25.576 [bus notice] <b5
2022-11-08 07:50:25.580 [bus notice] <10
2022-11-08 07:50:25.585 [bus notice] <09
2022-11-08 07:50:25.590 [bus notice] <00
2022-11-08 07:50:25.594 [bus notice] <00
2022-11-08 07:50:25.599 [bus notice] <3f
2022-11-08 07:50:25.604 [bus notice] <78
2022-11-08 07:50:25.610 [bus notice] <ff
2022-11-08 07:50:25.616 [bus notice] <ff
2022-11-08 07:50:25.619 [bus notice] <00
2022-11-08 07:50:25.625 [bus notice] <00
2022-11-08 07:50:25.628 [bus notice] <00
2022-11-08 07:50:25.631 [bus notice] <96
2022-11-08 07:50:25.635 [bus notice] <00
2022-11-08 07:50:25.663 [bus notice] <01
2022-11-08 07:50:25.667 [bus notice] <01
2022-11-08 07:50:25.671 [bus notice] <9a
2022-11-08 07:50:25.676 [bus notice] <00
2022-11-08 07:50:25.676 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:50:25.676 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:50:25.680 [bus notice] <aa


Hier mal ein paar Logs:
root@raspberrypi:/home/raspberry.dirk# ebusd -f -c --logareas=bus --loglevel debug -f -d /dev/ttyHZG
2022-11-08 07:53:42.349 [main notice] ebusd 22.4.v22.4 started on device /dev/ttyHZG
2022-11-08 07:53:42.349 [main info] loading configuration files from --logareas=bus/
2022-11-08 07:53:42.349 [main debug] reading directory --logareas=bus/
2022-11-08 07:53:42.349 [main error] error reading config files from --logareas=bus/: ERR: element not found, last error:
2022-11-08 07:53:42.395 [bus notice] bus started with own address 31/36
2022-11-08 07:53:42.395 [main info] registering data handlers
2022-11-08 07:53:42.395 [main info] registered data handlers
2022-11-08 07:53:42.424 [bus debug] ERR: SYN received during no signal, switching to ready
2022-11-08 07:53:42.424 [bus notice] signal acquired
2022-11-08 07:53:48.410 [bus notice] new master 10, master count 2
2022-11-08 07:53:48.481 [bus notice] new master 03, master count 3
2022-11-08 07:53:48.483 [update info] received MS cmd: 1008b5040100 / 0a0350530708110222a008
2022-11-08 07:53:48.484 [update notice] received unknown MS cmd: 1008b5040100 / 0a0350530708110222a008
2022-11-08 07:53:48.752 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:53:48.752 [update notice] received unknown MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:53:50.479 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:53:50.479 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:53:52.396 [main debug] performing regular tasks
2022-11-08 07:53:52.396 [main notice] found messages: 0 (0 conditional on 0 conditions, 0 poll, 0 update)
2022-11-08 07:53:56.509 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:53:56.509 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:53:58.507 [update info] received MS cmd: 1008b5110100 / 0818021432040f0081
2022-11-08 07:53:58.507 [update notice] received unknown MS cmd: 1008b5110100 / 0818021432040f0081
2022-11-08 07:53:58.735 [update info] received BC cmd: 10feb5160301a008
2022-11-08 07:53:58.735 [update notice] received unknown BC cmd: 10feb5160301a008
2022-11-08 07:54:00.512 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:00.512 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:02.396 [main debug] performing regular tasks
2022-11-08 07:54:06.533 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:06.533 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:08.517 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:54:08.517 [update notice] received unknown MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:54:10.562 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:10.563 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:12.396 [main debug] performing regular tasks
2022-11-08 07:54:16.581 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:16.581 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:18.587 [update info] received MS cmd: 1008b5040100 / 0a0319540708110222a008
2022-11-08 07:54:18.587 [update notice] received unknown MS cmd: 1008b5040100 / 0a0319540708110222a008
2022-11-08 07:54:20.588 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:20.588 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:22.396 [main debug] performing regular tasks
2022-11-08 07:54:26.580 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:26.581 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:28.592 [update info] received MS cmd: 1008b5100305ff01 / 00
2022-11-08 07:54:28.592 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 07:54:30.641 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:30.641 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:32.396 [main debug] performing regular tasks
2022-11-08 07:54:36.644 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:36.644 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:38.648 [update info] received BC cmd: 10feb516080040540708110222
2022-11-08 07:54:38.648 [update notice] received unknown BC cmd: 10feb516080040540708110222
2022-11-08 07:54:38.908 [update info] received MS cmd: 1008b512020064 / 00
2022-11-08 07:54:38.908 [update notice] received unknown MS cmd: 1008b512020064 / 00
2022-11-08 07:54:40.684 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:40.684 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:42.397 [main debug] performing regular tasks
2022-11-08 07:54:46.689 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:46.689 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:48.692 [update info] received MS cmd: 1008b5040100 / 0a0350540708110222a008
2022-11-08 07:54:48.692 [update notice] received unknown MS cmd: 1008b5040100 / 0a0350540708110222a008
2022-11-08 07:54:48.956 [update info] received MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:54:48.956 [update notice] received unknown MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 07:54:50.689 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:50.689 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:54:52.397 [main debug] performing regular tasks
2022-11-08 07:54:56.711 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:56.711 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:54:58.714 [update info] received MS cmd: 1008b5110100 / 0820021432040f0081
2022-11-08 07:54:58.714 [update notice] received unknown MS cmd: 1008b5110100 / 0820021432040f0081
2022-11-08 07:54:58.937 [update info] received BC cmd: 10feb5160301a008
2022-11-08 07:54:58.937 [update notice] received unknown BC cmd: 10feb5160301a008
2022-11-08 07:55:00.772 [update info] received MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:55:00.772 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 07:55:02.397 [main debug] performing regular tasks
^C2022-11-08 07:55:03.062 [main notice] SIGINT received
2022-11-08 07:55:06.739 [update info] received MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:55:06.739 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 07:55:07.515 [main notice] ebusd stopped


Hier die ebusd.log:
2022-11-08 07:43:33.099 [mqtt error] read bai DateTime: ERR: wrong symbol received
2022-11-08 07:43:33.189 [bus error] send to 08: ERR: SYN received, retry
2022-11-08 07:43:33.281 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 07:43:33.420 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 07:43:33.420 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 07:43:33.420 [mqtt error] read bai Status01: ERR: wrong symbol received
2022-11-08 07:43:33.509 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 07:43:33.597 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 07:43:33.687 [bus error] send to 08: ERR: SYN received
2022-11-08 07:43:33.687 [bus error] send message part 0: ERR: SYN received
2022-11-08 07:43:33.687 [mqtt error] read bai Status02: ERR: SYN received
2022-11-08 07:43:36.551 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 07:43:40.574 [update notice] received read bai Status01 QQ=10: 34.0;27.0;8.625;40.0;50.0;on
2022-11-08 07:43:42.569 [update notice] received unknown MS cmd: 1008b5110100 / 0820021432040f0081
2022-11-08 07:43:42.793 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 07:43:46.552 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 07:43:50.587 [update notice] received read bai Status01 QQ=10: 34.0;27.0;8.625;40.0;50.0;on
2022-11-08 07:43:52.574 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 07:43:56.655 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 07:44:00.639 [update notice] received read bai Status01 QQ=10: 34.0;27.0;8.625;40.0;50.0;on
2022-11-08 07:44:02.646 [update notice] received read bai DateTime QQ=10: valid;07:44:03;08.11.2022;8.625
2022-11-08 07:44:06.670 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 07:44:09.611 [main notice] SIGTERM received
2022-11-08 07:44:10.650 [update notice] received read bai Status01 QQ=10: 34.0;27.0;8.625;40.0;50.0;on
2022-11-08 07:44:10.842 [main notice] ebusd stopped
2022-11-08 08:02:08.892 [main notice] ebusd 22.4.v22.4 started with full scan on device /dev/ttyHZG
2022-11-08 08:02:08.924 [bus notice] bus started with own address 31/36
2022-11-08 08:02:08.934 [mqtt notice] connection established
2022-11-08 08:02:08.938 [bus notice] signal acquired
2022-11-08 08:02:11.169 [bus notice] new master 10, master count 2
2022-11-08 08:02:11.202 [bus notice] new master 03, master count 3
2022-11-08 08:02:11.202 [update notice] received unknown MS cmd: 1008b5100900003f78ffff000000 / 0101
2022-11-08 08:02:15.218 [update notice] received unknown MS cmd: 1008b5110101 / 094436a00850620100ff
2022-11-08 08:02:17.220 [update notice] received unknown MS cmd: 1008b5040100 / 0a01220208ffffffffa008
2022-11-08 08:02:18.926 [main notice] starting initial full scan
2022-11-08 08:02:25.146 [main error] scan config 08: ERR: wrong symbol received
2022-11-08 08:02:27.035 [bus error] signal lost
2022-11-08 08:02:27.307 [main error] scan config 15: ERR: no signal
2022-11-08 08:02:51.111 [main error] scan config 08: ERR: no signal
2022-11-08 08:03:11.352 [main error] scan config 15: ERR: no signal
2022-11-08 08:03:36.605 [bus notice] re-opened /dev/ttyHZG
2022-11-08 08:03:41.527 [main error] scan config 08: ERR: no signal
2022-11-08 08:03:42.015 [bus notice] signal acquired
2022-11-08 08:03:46.096 [bus notice] scan 08: ;Vaillant;BAI00;0518;7401
2022-11-08 08:03:46.096 [update notice] store 08 ident: done
2022-11-08 08:03:46.096 [update notice] received scan-read scan.08  QQ=10: Vaillant;BAI00;0518;7401
2022-11-08 08:03:52.350 [update notice] received unknown MS cmd: 1008b512020064 / 00
2022-11-08 08:03:54.763 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:04:00.246 [update notice] received unknown MS cmd: 1008b5040100 / 0a01210008ffffffff6008
2022-11-08 08:04:00.516 [update notice] received unknown MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 08:04:04.237 [update notice] received unknown MS cmd: 1008b51009000000000000000000 / 0101
2022-11-08 08:04:06.776 [main notice] read common config file vaillant/scan.csv
2022-11-08 08:04:06.777 [main notice] read common config file vaillant/general.csv
2022-11-08 08:04:06.779 [main notice] read common config file vaillant/broadcast.csv
2022-11-08 08:04:06.782 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0518, HW7401
2022-11-08 08:04:06.910 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:06.998 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.088 [bus error] send to 08: ERR: SYN received
2022-11-08 08:04:07.088 [bus error] send message part 0: ERR: SYN received
2022-11-08 08:04:07.088 [main error] error reading message scan.08 id: ERR: SYN received
2022-11-08 08:04:07.176 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.317 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.407 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:07.407 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:07.408 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:07.495 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.584 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.675 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:07.675 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:07.675 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:07.763 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.852 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:07.941 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:07.941 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:07.941 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:08.037 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:08.125 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:08.317 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:08.317 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:08.317 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:08.405 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:08.495 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:08.584 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:08.584 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:08.584 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:08.683 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:09.261 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:09.359 [bus error] send to 08: ERR: SYN received
2022-11-08 08:04:09.360 [bus error] send message part 0: ERR: SYN received
2022-11-08 08:04:09.360 [main error] error reading message scan.08 id: ERR: SYN received
2022-11-08 08:04:09.449 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:09.581 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:09.674 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:09.674 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:09.674 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:09.762 [bus error] send to 08: ERR: SYN received, retry
2022-11-08 08:04:09.849 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:09.983 [bus error] send to 08: ERR: SYN received
2022-11-08 08:04:09.983 [bus error] send message part 0: ERR: SYN received
2022-11-08 08:04:09.983 [main error] error reading message scan.08 id: ERR: SYN received
2022-11-08 08:04:10.079 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:10.299 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:10.389 [bus error] send to 08: ERR: SYN received
2022-11-08 08:04:10.389 [bus error] send message part 0: ERR: SYN received
2022-11-08 08:04:10.389 [main error] error reading message scan.08 id: ERR: SYN received
2022-11-08 08:04:10.542 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:10.683 [bus error] send to 08: ERR: read timeout, retry
2022-11-08 08:04:10.768 [update notice] received unknown MS cmd: 1008b5110102 / 05033c64506e
2022-11-08 08:04:10.817 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:10.817 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:10.817 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:10.908 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.011 [bus notice] max. symbols per second: 114
2022-11-08 08:04:11.019 [update notice] received unknown MS cmd: 1008b512020064 / 00
2022-11-08 08:04:11.069 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.161 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:11.161 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:11.161 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:11.246 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.338 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.430 [bus error] send to 08: ERR: SYN received
2022-11-08 08:04:11.430 [bus error] send message part 0: ERR: SYN received
2022-11-08 08:04:11.431 [main error] error reading message scan.08 id: ERR: SYN received
2022-11-08 08:04:11.519 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.654 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.743 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:11.743 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:11.743 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:11.832 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:11.920 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:12.011 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:12.011 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:12.011 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:12.105 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:12.194 [bus error] send to 08: ERR: wrong symbol received, retry
2022-11-08 08:04:12.284 [bus error] send to 08: ERR: wrong symbol received
2022-11-08 08:04:12.284 [bus error] send message part 0: ERR: wrong symbol received
2022-11-08 08:04:12.284 [main error] error reading message scan.08 id: ERR: wrong symbol received
2022-11-08 08:04:12.316 [main notice] found messages: 225 (3 conditional on 28 conditions, 0 poll, 10 update)
2022-11-08 08:04:14.731 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:04:18.303 [update notice] received read bai Status01 QQ=10: 30.0;28.0;8.375;37.0;49.0;off
2022-11-08 08:04:20.294 [update notice] received unknown MS cmd: 1008b5110100 / 08d801140007080082
2022-11-08 08:04:20.517 [update notice] received update-read broadcast outsidetemp QQ=10: 8.375
2022-11-08 08:04:24.314 [update notice] received update-write bai SetMode QQ=10: auto;0.0;0.0;0;0;0;0;0;0;0
2022-11-08 08:04:26.831 [main error] scan config 15: ERR: SYN received
2022-11-08 08:04:28.329 [update notice] received read bai Status01 QQ=10: 28.0;27.0;8.375;37.0;49.0;off
2022-11-08 08:04:30.565 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:04:30.818 [update notice] received unknown MS cmd: 1008b5120204ff / 0101
2022-11-08 08:04:34.351 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:04:38.373 [update notice] received read bai Status01 QQ=10: 27.0;27.0;8.375;37.0;49.0;off
2022-11-08 08:04:38.961 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:04:40.377 [update notice] received read bai DateTime QQ=10: sync;08:01:02;-.-.-;8.375
2022-11-08 08:04:43.226 [update notice] received unknown MS cmd: 0315b51303060000 / 0101
2022-11-08 08:04:43.341 [update notice] received unknown MS cmd: 0315b51303060000 / 0101
2022-11-08 08:04:43.450 [update notice] received unknown MS cmd: 0315b51303060000 / 0101
2022-11-08 08:04:43.513 [update notice] received unknown MS cmd: 0315b51303060000 / 0101
2022-11-08 08:04:44.386 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:04:48.403 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;49.0;off
2022-11-08 08:04:50.379 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:04:51.059 [main error] scan config 15: ERR: SYN received
2022-11-08 08:04:54.395 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:04:58.462 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:00.424 [update notice] received update-read broadcast vdatetime QQ=10: 09:01:18;01.01.2010
2022-11-08 08:05:00.676 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:05:03.151 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:05:04.461 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:08.469 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:10.474 [update notice] received read bai DateTime QQ=10: sync;08:01:33;-.-.-;8.375
2022-11-08 08:05:10.741 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:05:10.992 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:05:14.517 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:15.240 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:05:18.483 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:20.559 [update notice] received unknown MS cmd: 1008b5110100 / 08b001140007080083
2022-11-08 08:05:20.791 [update notice] received update-read broadcast outsidetemp QQ=10: 8.375
2022-11-08 08:05:22.559 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:27.329 [main error] scan config 15: ERR: SYN received
2022-11-08 08:05:28.562 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:30.536 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:05:32.578 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:38.582 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:39.439 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:05:40.627 [update notice] received read bai DateTime QQ=10: sync;08:02:04;-.-.-;8.375
2022-11-08 08:05:42.618 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:48.619 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:05:50.589 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:05:51.543 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:05:52.677 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:05:58.685 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;48.0;off
2022-11-08 08:06:00.644 [update notice] received update-read broadcast vdatetime QQ=10: 09:02:18;01.01.2010
2022-11-08 08:06:00.911 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:06:02.684 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:03.680 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:06:08.737 [update notice] received read bai Status01 QQ=10: 27.0;26.0;8.375;37.0;47.0;off
2022-11-08 08:06:10.747 [update notice] received read bai DateTime QQ=10: valid;08:06:11;08.11.2022;8.375
2022-11-08 08:06:11.014 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:06:12.711 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:15.781 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:06:18.772 [update notice] received read bai Status01 QQ=10: 26.0;26.0;8.375;37.0;47.0;off
2022-11-08 08:06:20.757 [update notice] received unknown MS cmd: 1008b5110100 / 08a801140007080083
2022-11-08 08:06:20.981 [update notice] received update-read broadcast outsidetemp QQ=10: 8.375
2022-11-08 08:06:22.759 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:27.908 [main error] scan config 15: ERR: SYN received
2022-11-08 08:06:28.776 [update notice] received read bai Status01 QQ=10: 26.0;26.0;8.375;37.0;47.0;off
2022-11-08 08:06:30.759 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:06:32.807 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:38.897 [update notice] received read bai Status01 QQ=10: 27.0;28.0;8.375;37.0;47.0;hwc
2022-11-08 08:06:40.031 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:06:40.941 [update notice] received read bai DateTime QQ=10: valid;08:06:42;08.11.2022;8.375
2022-11-08 08:06:42.858 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:48.883 [update notice] received read bai Status01 QQ=10: 45.0;39.0;8.375;37.0;46.0;hwc
2022-11-08 08:06:50.846 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:06:52.161 [main error] scan config 15: ERR: SYN received
2022-11-08 08:06:52.895 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:06:58.914 [update notice] received read bai Status01 QQ=10: 59.0;49.0;8.375;54.0;46.0;hwc
2022-11-08 08:07:00.865 [update notice] received update-read broadcast vdatetime QQ=10: 09:03:18;01.01.2010
2022-11-08 08:07:01.119 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:07:02.893 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:04.296 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:07:08.939 [update notice] received read bai Status01 QQ=10: 68.0;54.0;8.375;60.0;46.0;hwc
2022-11-08 08:07:10.945 [update notice] received read bai DateTime QQ=10: valid;08:07:12;08.11.2022;8.375
2022-11-08 08:07:11.216 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:07:12.986 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:16.417 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:07:18.956 [update notice] received read bai Status01 QQ=10: 70.0;55.0;8.625;58.0;46.0;hwc
2022-11-08 08:07:21.002 [update notice] received unknown MS cmd: 1008b5110100 / 08700413c8183f0083
2022-11-08 08:07:21.224 [update notice] received update-read broadcast outsidetemp QQ=10: 8.375
2022-11-08 08:07:23.001 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:28.536 [main error] scan config 15: ERR: SYN received
2022-11-08 08:07:29.046 [update notice] received read bai Status01 QQ=10: 70.0;54.0;8.375;56.0;46.0;hwc
2022-11-08 08:07:31.034 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:07:33.039 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:39.056 [update notice] received read bai Status01 QQ=10: 69.0;53.0;8.625;55.0;45.0;hwc
2022-11-08 08:07:40.639 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:07:41.064 [update notice] received read bai DateTime QQ=10: valid;08:07:42;08.11.2022;8.625
2022-11-08 08:07:43.063 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:49.123 [update notice] received read bai Status01 QQ=10: 69.0;53.0;8.625;55.0;45.0;hwc
2022-11-08 08:07:51.050 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:07:52.770 [main error] scan config 15: ERR: SYN received
2022-11-08 08:07:53.140 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:07:59.123 [update notice] received read bai Status01 QQ=10: 69.0;53.0;8.375;55.0;45.0;hwc
2022-11-08 08:08:01.131 [update notice] received update-read broadcast vdatetime QQ=10: 08:08:02;08.11.2022
2022-11-08 08:08:01.398 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:08:03.170 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:08:04.890 [main error] scan config 15: ERR: SYN received
2022-11-08 08:08:09.188 [update notice] received read bai Status01 QQ=10: 69.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:08:11.186 [update notice] received scan-read scan.08  QQ=10: Vaillant;BAI00;0518;7401
2022-11-08 08:08:14.581 [update notice] received read bai DateTime QQ=10: valid;08:08:16;08.11.2022;8.625
2022-11-08 08:08:14.848 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:08:16.990 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:08:25.261 [update notice] received read bai DateTime QQ=10: valid;08:08:27;08.11.2022;8.625
2022-11-08 08:08:25.528 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:08:29.089 [main error] scan config 15: ERR: SYN received
2022-11-08 08:08:29.283 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:08:33.269 [update notice] received read bai Status01 QQ=10: 69.0;54.0;8.625;56.0;45.0;hwc
2022-11-08 08:08:35.302 [update notice] received unknown MS cmd: 1008b5110100 / 08480413a4183f0083
2022-11-08 08:08:35.527 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:08:39.287 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:08:41.190 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:08:43.321 [update notice] received read bai Status01 QQ=10: 68.0;54.0;8.625;56.0;45.0;hwc
2022-11-08 08:08:45.299 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:08:49.376 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:08:53.368 [update notice] received read bai Status01 QQ=10: 67.0;54.0;8.625;56.0;45.0;hwc
2022-11-08 08:08:53.416 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:08:55.366 [update notice] received read bai DateTime QQ=10: valid;08:08:57;08.11.2022;8.625
2022-11-08 08:08:59.405 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:03.387 [update notice] received read bai Status01 QQ=10: 66.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:09:05.402 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:09:05.544 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:09:07.413 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:13.434 [update notice] received read bai Status01 QQ=10: 65.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:09:15.397 [update notice] received update-read broadcast vdatetime QQ=10: 08:09:16;08.11.2022
2022-11-08 08:09:15.652 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:09:17.436 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:17.662 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:09:23.465 [update notice] received read bai Status01 QQ=10: 64.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:09:25.468 [update notice] received read bai DateTime QQ=10: valid;08:09:27;08.11.2022;8.625
2022-11-08 08:09:25.737 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:09:27.468 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:29.768 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:09:33.490 [update notice] received read bai Status01 QQ=10: 63.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:09:35.489 [update notice] received unknown MS cmd: 1008b5110100 / 08fa03136a183f0083
2022-11-08 08:09:35.712 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:09:37.537 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:41.878 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:09:43.551 [update notice] received read bai Status01 QQ=10: 63.0;54.0;8.625;55.0;45.0;hwc
2022-11-08 08:09:45.587 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:09:47.590 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:09:53.609 [update notice] received read bai Status01 QQ=10: 62.0;53.0;8.625;55.0;46.0;hwc
2022-11-08 08:09:53.980 [main error] scan config 15: ERR: SYN received
2022-11-08 08:09:55.617 [update notice] received read bai DateTime QQ=10: valid;08:09:58;08.11.2022;8.625
2022-11-08 08:09:57.617 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:03.635 [update notice] received read bai Status01 QQ=10: 62.0;53.0;8.625;55.0;46.0;hwc
2022-11-08 08:10:05.610 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:10:06.381 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:10:07.655 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:13.668 [update notice] received read bai Status01 QQ=10: 61.0;53.0;8.625;55.0;46.0;hwc
2022-11-08 08:10:15.630 [update notice] received update-read broadcast vdatetime QQ=10: 08:10:16;08.11.2022
2022-11-08 08:10:15.878 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:10:17.698 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:18.512 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:10:23.710 [update notice] received read bai Status01 QQ=10: 61.0;53.0;8.625;55.0;47.0;hwc
2022-11-08 08:10:25.721 [update notice] received read bai DateTime QQ=10: valid;08:10:27;08.11.2022;8.625
2022-11-08 08:10:25.988 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:10:27.718 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:30.622 [main error] scan config 15: ERR: SYN received
2022-11-08 08:10:33.743 [update notice] received read bai Status01 QQ=10: 61.0;53.0;8.625;55.0;47.0;hwc
2022-11-08 08:10:35.741 [update notice] received unknown MS cmd: 1008b5110100 / 08d003134e183f0081
2022-11-08 08:10:35.967 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:10:37.746 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:42.721 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:10:43.770 [update notice] received read bai Status01 QQ=10: 60.0;53.0;8.625;55.0;48.0;hwc
2022-11-08 08:10:45.755 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:10:47.805 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:10:53.831 [update notice] received read bai Status01 QQ=10: 60.0;53.0;8.625;55.0;48.0;hwc
2022-11-08 08:10:54.831 [main error] scan config 15: ERR: ACK error
2022-11-08 08:10:55.838 [update notice] received read bai DateTime QQ=10: valid;08:10:58;08.11.2022;8.625
2022-11-08 08:10:57.838 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:03.856 [update notice] received read bai Status01 QQ=10: 59.0;54.0;8.625;55.0;48.0;hwc
2022-11-08 08:11:05.873 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:11:06.956 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:11:07.868 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:13.933 [update notice] received read bai Status01 QQ=10: 58.0;54.0;8.625;55.0;49.0;hwc
2022-11-08 08:11:15.899 [update notice] received update-read broadcast vdatetime QQ=10: 08:11:16;08.11.2022
2022-11-08 08:11:16.159 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:11:17.928 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:19.059 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:11:23.940 [update notice] received read bai Status01 QQ=10: 58.0;54.0;8.625;55.0;49.0;hwc
2022-11-08 08:11:25.942 [update notice] received read bai DateTime QQ=10: valid;08:11:27;08.11.2022;8.625
2022-11-08 08:11:26.212 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:11:27.955 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:31.159 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:11:33.972 [update notice] received read bai Status01 QQ=10: 59.0;54.0;8.625;56.0;49.0;hwc
2022-11-08 08:11:35.963 [update notice] received unknown MS cmd: 1008b5110100 / 08b0031332183f0081
2022-11-08 08:11:36.188 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:11:38.025 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:43.259 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:11:43.987 [update notice] received read bai Status01 QQ=10: 59.0;55.0;8.625;56.0;49.0;hwc
2022-11-08 08:11:46.012 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:11:48.076 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:11:54.096 [update notice] received read bai Status01 QQ=10: 59.0;55.0;8.625;57.0;50.0;hwc
2022-11-08 08:11:55.365 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:11:56.059 [update notice] received read bai DateTime QQ=10: valid;08:11:58;08.11.2022;8.625
2022-11-08 08:11:58.064 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:04.084 [update notice] received read bai Status01 QQ=10: 60.0;55.0;8.625;57.0;50.0;hwc
2022-11-08 08:12:06.054 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:12:07.501 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:12:08.102 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:14.117 [update notice] received read bai Status01 QQ=10: 60.0;56.0;8.625;57.0;50.0;hwc
2022-11-08 08:12:16.085 [update notice] received update-read broadcast vdatetime QQ=10: 08:12:17;08.11.2022
2022-11-08 08:12:16.346 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:12:18.165 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:19.611 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:12:24.186 [update notice] received read bai Status01 QQ=10: 61.0;56.0;8.625;58.0;51.0;hwc
2022-11-08 08:12:26.187 [update notice] received read bai DateTime QQ=10: valid;08:12:27;08.11.2022;8.625
2022-11-08 08:12:26.454 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:12:28.189 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:31.708 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:12:34.248 [update notice] received read bai Status01 QQ=10: 61.0;56.0;8.625;58.0;51.0;hwc
2022-11-08 08:12:36.201 [update notice] received unknown MS cmd: 1008b5110100 / 08d5031232183f0081
2022-11-08 08:12:36.425 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:12:38.250 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:43.838 [main error] scan config 15: ERR: SYN received
2022-11-08 08:12:44.252 [update notice] received read bai Status01 QQ=10: 61.0;56.0;8.625;58.0;51.0;hwc
2022-11-08 08:12:46.242 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:12:48.241 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:12:54.298 [update notice] received read bai Status01 QQ=10: 61.0;57.0;8.625;58.0;51.0;hwc
2022-11-08 08:12:55.931 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:12:56.305 [update notice] received read bai DateTime QQ=10: valid;08:12:58;08.11.2022;8.625
2022-11-08 08:12:58.316 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:02.306 [update notice] received read bai Status01 QQ=10: 61.0;57.0;8.625;58.0;51.0;hwc
2022-11-08 08:13:04.276 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:13:08.026 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:13:08.352 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:12.344 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;58.0;52.0;hwc
2022-11-08 08:13:14.368 [update notice] received update-read broadcast vdatetime QQ=10: 08:13:15;08.11.2022
2022-11-08 08:13:14.621 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:13:18.401 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:20.160 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:13:22.430 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;52.0;hwc
2022-11-08 08:13:24.438 [update notice] received read bai DateTime QQ=10: valid;08:13:25;08.11.2022;8.625
2022-11-08 08:13:24.704 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:13:28.431 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:32.271 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:13:32.467 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;52.0;hwc
2022-11-08 08:13:34.468 [update notice] received unknown MS cmd: 1008b5110100 / 08e4031232183f0081
2022-11-08 08:13:34.693 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:13:38.501 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:42.484 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;52.0;hwc
2022-11-08 08:13:44.391 [main error] scan config 15: ERR: SYN received
2022-11-08 08:13:48.502 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:13:52.534 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;52.0;hwc
2022-11-08 08:13:54.545 [update notice] received read bai DateTime QQ=10: valid;08:13:56;08.11.2022;8.625
2022-11-08 08:13:56.487 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:13:58.536 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:02.567 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;52.0;hwc
2022-11-08 08:14:04.546 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:14:08.561 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:08.610 [main error] scan config 15: ERR: SYN received
2022-11-08 08:14:12.632 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;53.0;hwc
2022-11-08 08:14:14.584 [update notice] received update-read broadcast vdatetime QQ=10: 08:14:15;08.11.2022
2022-11-08 08:14:14.839 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:14:18.647 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:20.721 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:14:22.634 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;53.0;hwc
2022-11-08 08:14:24.634 [update notice] received read bai DateTime QQ=10: valid;08:14:26;08.11.2022;8.625
2022-11-08 08:14:24.901 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:14:28.670 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:32.656 [update notice] received read bai Status01 QQ=10: 62.0;57.0;8.625;59.0;53.0;hwc
2022-11-08 08:14:32.841 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:14:34.694 [update notice] received unknown MS cmd: 1008b5110100 / 08e8031232183f0081
2022-11-08 08:14:34.923 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:14:38.690 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:42.725 [update notice] received read bai Status01 QQ=10: 62.0;58.0;8.625;59.0;53.0;hwc
2022-11-08 08:14:44.704 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:14:44.931 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:14:48.741 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:14:52.776 [update notice] received read bai Status01 QQ=10: 63.0;58.0;8.625;60.0;53.0;hwc
2022-11-08 08:14:54.780 [update notice] received read bai DateTime QQ=10: valid;08:14:56;08.11.2022;8.625
2022-11-08 08:14:57.038 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:14:58.810 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:15:02.802 [update notice] received read bai Status01 QQ=10: 63.0;58.0;8.625;60.0;54.0;hwc
2022-11-08 08:15:04.780 [update notice] received unknown MS cmd: 1008b5100305ff01 / 00
2022-11-08 08:15:08.809 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:15:09.131 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:15:12.835 [update notice] received read bai Status01 QQ=10: 62.0;58.0;8.625;59.0;54.0;off
2022-11-08 08:15:14.802 [update notice] received update-read broadcast vdatetime QQ=10: 08:15:15;08.11.2022
2022-11-08 08:15:15.058 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:15:18.864 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:15:21.264 [main error] scan config 15: ERR: SYN received
2022-11-08 08:15:22.893 [update notice] received read bai Status01 QQ=10: 59.0;57.0;8.625;58.0;54.0;off
2022-11-08 08:15:24.900 [update notice] received read bai DateTime QQ=10: valid;08:15:26;08.11.2022;8.625
2022-11-08 08:15:25.170 [update notice] received read bai Status02 QQ=10: auto;60;50.0;80;55.0
2022-11-08 08:15:25.430 [update notice] received update-write bai StatusCirPump QQ=10: on
2022-11-08 08:15:28.879 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:15:29.242 [main error] scan config 15: ERR: wrong symbol received
2022-11-08 08:15:32.899 [update notice] received read bai Status01 QQ=10: 57.0;56.0;8.625;57.0;54.0;off
2022-11-08 08:15:34.934 [update notice] received unknown MS cmd: 1008b5110100 / 08900312001b380081
2022-11-08 08:15:35.162 [update notice] received update-read broadcast outsidetemp QQ=10: 8.625
2022-11-08 08:15:38.969 [update notice] received update-write bai SetMode QQ=10: auto;31.5;60.0;-;0;0;0;0;0;0
2022-11-08 08:15:41.717 [main error] scan config 15: ERR: SYN received
2022-11-08 08:15:42.948 [update notice] received read bai Status01 QQ=10: 56.0;55.0;8.375;57.0;54.0;off

Physman

#1859
Und hier noch der sehr detaillierter DEBUG LOG.
Am Anfang lief die Therme, zwischendurch einmal Neustart der Therme.
Ist ziemlich lang - sorry....
Log anbei....