Neuigkeiten:

Am Sonntag den 8.12.2024 kann es ab ca. 8:00 Uhr zu kurzzeitigen Einschränkungen / Ausfällen bei den Diensten des FHEM Vereines kommen.
Die Server müssen mal gewartet und dabei neu gestartet werden ;)

Hauptmenü

Läuft: Heizung mit eBus-Schnittstelle

Begonnen von Prof. Dr. Peter Henning, 29 November 2014, 13:36:59

Vorheriges Thema - Nächstes Thema

john30

Zitat von: Rainer1 am 12 November 2023, 11:28:36Ich habe ständig Fehler auf dem Bus mit dem neuen Adapter V5. Das ist natürlich sehr unzuverlässig, da Werte fehlen um eine Grafik zu erzeugen, gerade wenn sich Werte schnell ändern. Sollte mit dem neuen Adapter nicht alles besser werden ?
Der Adapter hängt im WLAN, kann es sein, dass das zum Problem führt ?

Auch werden oft Werte per MQTT nicht geschrieben - ist der Bus überlastet ?

Die ebusd.log ist nach 1,5h bereits 250k groß, macht am Tag 4MB !!!

Der Fehler "[bus error] poll 470 YieldThisYear failed" tritt mit dem neuen Adapter V5 sehr viel häufiger auf, als mit dem TTL-Adapter (Poti-Version)
die WIFI Anbindung ist von je her schwierig, weil du für einen vernünftigen Betrieb Latenzzeiten unter 20ms bräuchtest. Das ist je nach Überlagerung benachbarter Netze oder mit entsprechender Auslastung des eigenen flott mal unmöglich.
author of ebusd

Rainer1

Der Adapter V5 ist Geschichte ! - keine Zeit und Nerven mehr um das irgendwie ans Laufen zu bekommen. Komisch dass der alte Adapter (habe auch noch 1 Ersatz ;) ) reibungslos, bis auf eine Ausnahme nach Umstellung auf MQTT, läuft.

Wie kann das Polling "poll 470 YieldThisYear" deaktiviert werden ? Das scheint erst in den neueren ebusd-Versionen umgesetzt worden zu sein ?

Prof. Dr. Peter Henning

ZitatHier ist ja gar nichts mehr los !
Nicht doch. Das ist eher ein Zeichen dafür, dass die Dinge problemlos laufen und gut dokumentiert sind.

pah

psifactory

Hallo Zusammen,

ich habe aktuell ein Problem meinen eBusd zum Laufen zu bringen.
Ich verstehe aktuell, dass mein Gateway wohl nicht schreiben kann? Ist der Ansatz richtig? Was kann ich hier dann tun um das Problem zu lösen?


Folgendes Setup:

  • Esera Eco ECO305_MCU3 Ebus Gateway
  • ebusd auf Ubuntu (ebusd 23.2.23.2-71-g53fcc90f)
  • Vaillant Gas Hybrid Heizungssystem mit:
  • - Vaillant AroTherm 125/5 WP
  • - Vaillant EcoVit VKK 476/4 Gasheizung
  • - Vaillant VR71 Mischermodul

Meine Ebusd Settings in /etc/default/ebusd
EBUSD_OPTS="--configpath=http://cfg.ebusd.eu -d 10.0.0.83:5001 -p 8888 --logareas all --loglevel debug -l /var/log/ebusd.log  --scanconfig=full  --httpport=8889 --htmlpath=/var/ebusd/html"
ebusctl info
version: ebusd 23.2.23.2-71-g53fcc90f
device: 10.0.0.83:5001, TCP
signal: acquired
symbol rate: 113
max symbol rate: 184
min arbitration micros: 1
max arbitration micros: 340
min symbol latency: 23
max symbol latency: 42
scan: finished, some messages pending
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning

Logfile nach Start des Ebusd
2023-12-25 10:09:47.078 [bus notice] device status: transport opened
2023-12-25 10:09:47.079 [main info] registering data handlers
2023-12-25 10:09:47.079 [main info] registered data handlers
2023-12-25 10:09:47.079 [main notice] ebusd 23.2.23.2-71-g53fcc90f started with full scan on device: 10.0.0.83:5001, TCP
2023-12-25 10:09:47.079 [main info] loading configuration files from http://cfg.ebusd.eu/
2023-12-25 10:09:47.107 [main info] reading templates /
2023-12-25 10:09:47.135 [main info] read templates in /
2023-12-25 10:09:47.135 [main info] reading file broadcast.csv
2023-12-25 10:09:47.161 [main info] successfully read file broadcast.csv
2023-12-25 10:09:47.161 [main info] reading file memory.csv
2023-12-25 10:09:47.190 [main info] successfully read file memory.csv
2023-12-25 10:09:47.190 [main info] read config files, got 11 messages
2023-12-25 10:09:47.190 [bus notice] bus started with own address 31/36
2023-12-25 10:09:47.191 [bus notice] signal acquired
2023-12-25 10:09:47.729 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:48.207 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:48.842 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:49.337 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:49.438 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:09:49.810 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:49.812 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:49.823 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:49.919 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:50.050 [bus notice] max. symbols per second: 133
2023-12-25 10:09:50.132 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:50.138 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:50.407 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:50.502 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:50.757 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:51.008 [bus notice] max. symbols per second: 156
2023-12-25 10:09:51.026 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:51.136 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:51.386 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:51.389 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:51.495 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:51.583 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:51.586 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:51.807 [bus debug] ERR: read timeout during receive command CRC, switching to skip
2023-12-25 10:09:52.006 [bus notice] max. symbols per second: 184
2023-12-25 10:09:52.015 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:52.019 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:52.184 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:52.300 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:52.547 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:52.733 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:52.845 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:53.096 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:53.279 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:53.819 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:53.945 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:53.951 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:54.631 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:55.569 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:09:57.191 [main debug] performing regular tasks
2023-12-25 10:09:57.191 [main notice] starting initial full scan
2023-12-25 10:09:57.191 [bus info] scan 02 cmd: 3102070400
2023-12-25 10:09:57.367 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:57.371 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:57.375 [bus debug] start request 31
2023-12-25 10:09:57.375 [bus debug] arbitration start with 31
2023-12-25 10:09:57.444 [bus debug] arbitration won
2023-12-25 10:09:57.444 [bus debug] arbitration delay 1 micros
2023-12-25 10:09:57.444 [bus info] arbitration delay 1 - 1 micros
2023-12-25 10:09:57.444 [bus debug] switching from ready to send command
2023-12-25 10:09:57.471 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:09:57.471 [bus info] send/receive symbol latency 27 - 27 ms
2023-12-25 10:09:57.499 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:09:57.525 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:09:57.525 [bus info] send/receive symbol latency 25 - 27 ms
2023-12-25 10:09:57.553 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:09:57.553 [bus info] send/receive symbol latency 25 - 28 ms
2023-12-25 10:09:57.553 [bus debug] switching from send command to send command CRC
2023-12-25 10:09:57.580 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:09:57.580 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:09:57.645 [bus debug] notify request: ERR: read timeout
2023-12-25 10:09:57.645 [bus info] scan 04 cmd: 3104070400
2023-12-25 10:09:57.645 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:09:58.083 [bus debug] start request 31
2023-12-25 10:09:58.083 [bus debug] arbitration start with 31
2023-12-25 10:09:58.152 [bus debug] arbitration won
2023-12-25 10:09:58.152 [bus debug] arbitration delay 1 micros
2023-12-25 10:09:58.152 [bus debug] switching from ready to send command
2023-12-25 10:09:58.179 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:09:58.206 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:09:58.231 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:09:58.231 [bus info] send/receive symbol latency 24 - 28 ms
2023-12-25 10:09:58.256 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:09:58.256 [bus debug] switching from send command to send command CRC
2023-12-25 10:09:58.281 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:09:58.281 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:09:58.289 [bus debug] switching from receive command ACK to receive response
2023-12-25 10:09:58.380 [bus debug] notify request: ERR: read timeout
2023-12-25 10:09:58.380 [bus info] scan 05 cmd: 3105070400
2023-12-25 10:09:58.380 [bus debug] ERR: read timeout during receive response, switching to skip
2023-12-25 10:09:58.789 [bus debug] start request 31
2023-12-25 10:09:58.789 [bus debug] arbitration start with 31
2023-12-25 10:09:58.874 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:09:58.879 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:09:58.932 [bus debug] arbitration won
2023-12-25 10:09:58.932 [bus debug] arbitration delay 2 micros
2023-12-25 10:09:58.932 [bus info] arbitration delay 1 - 2 micros
2023-12-25 10:09:58.932 [bus debug] switching from ready to send command
2023-12-25 10:09:58.958 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:09:58.984 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:09:59.009 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:09:59.035 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:09:59.035 [bus debug] switching from send command to send command CRC
2023-12-25 10:09:59.061 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:09:59.061 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:09:59.066 [bus debug] switching from receive command ACK to receive response
2023-12-25 10:09:59.157 [bus debug] notify request: ERR: read timeout
2023-12-25 10:09:59.157 [bus info] scan 06 cmd: 3106070400
2023-12-25 10:09:59.157 [bus debug] ERR: read timeout during receive response, switching to skip
2023-12-25 10:09:59.157 [bus debug] start request 31
2023-12-25 10:09:59.157 [bus debug] arbitration start with 31
2023-12-25 10:09:59.576 [bus debug] arbitration lost
2023-12-25 10:09:59.576 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:09:59.664 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:09:59.664 [bus debug] start request 31
2023-12-25 10:09:59.664 [bus debug] arbitration start with 31
2023-12-25 10:10:00.110 [bus debug] arbitration lost
2023-12-25 10:10:00.110 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:00.199 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:00.199 [bus debug] start request 31
2023-12-25 10:10:00.199 [bus debug] arbitration start with 31
2023-12-25 10:10:00.667 [bus debug] arbitration won
2023-12-25 10:10:00.667 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:00.667 [bus debug] switching from ready to send command
2023-12-25 10:10:00.693 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:00.728 [bus debug] send/receive symbol latency 35 ms
2023-12-25 10:10:00.728 [bus info] send/receive symbol latency 24 - 35 ms
2023-12-25 10:10:00.754 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:00.779 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:00.779 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:00.829 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:00.829 [bus info] scan 08 cmd: 3108070400
2023-12-25 10:10:00.829 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:00.829 [bus debug] start request 31
2023-12-25 10:10:00.829 [bus debug] arbitration start with 31
2023-12-25 10:10:01.288 [bus debug] arbitration lost
2023-12-25 10:10:01.288 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:01.377 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:01.377 [bus debug] start request 31
2023-12-25 10:10:01.377 [bus debug] arbitration start with 31
2023-12-25 10:10:01.847 [bus debug] arbitration won
2023-12-25 10:10:01.847 [bus debug] arbitration delay 1 micros
2023-12-25 10:10:01.847 [bus debug] switching from ready to send command
2023-12-25 10:10:01.873 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:01.900 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:01.925 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:01.951 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:01.951 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:02.001 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:02.001 [bus info] scan 09 cmd: 3109070400
2023-12-25 10:10:02.001 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:02.002 [bus debug] start request 31
2023-12-25 10:10:02.002 [bus debug] arbitration start with 31
2023-12-25 10:10:02.460 [bus debug] arbitration lost
2023-12-25 10:10:02.460 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:02.563 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:10:02.564 [bus debug] start request 31
2023-12-25 10:10:02.564 [bus debug] arbitration start with 31
2023-12-25 10:10:02.609 [bus debug] arbitration lost
2023-12-25 10:10:02.610 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:02.702 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:03.141 [bus debug] start request 31
2023-12-25 10:10:03.141 [bus debug] arbitration start with 31
2023-12-25 10:10:03.248 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:10:03.272 [bus debug] arbitration won
2023-12-25 10:10:03.272 [bus debug] arbitration delay 301 micros
2023-12-25 10:10:03.273 [bus info] arbitration delay 1 - 301 micros
2023-12-25 10:10:03.273 [bus debug] switching from ready to send command
2023-12-25 10:10:03.302 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:03.332 [bus debug] send/receive symbol latency 30 ms
2023-12-25 10:10:03.359 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:03.385 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:03.385 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:03.435 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:03.435 [bus info] scan 0a cmd: 310a070400
2023-12-25 10:10:03.435 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:03.435 [bus debug] start request 31
2023-12-25 10:10:03.435 [bus debug] arbitration start with 31
2023-12-25 10:10:03.920 [bus debug] arbitration won
2023-12-25 10:10:03.920 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:03.920 [bus debug] switching from ready to send command
2023-12-25 10:10:03.947 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:03.972 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:03.998 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:04.023 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:04.023 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:04.052 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:04.052 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:04.117 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:04.117 [bus info] scan 0b cmd: 310b070400
2023-12-25 10:10:04.117 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:04.117 [bus debug] start request 31
2023-12-25 10:10:04.117 [bus debug] arbitration start with 31
2023-12-25 10:10:04.661 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:10:04.666 [bus debug] arbitration lost
2023-12-25 10:10:04.666 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:04.758 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:04.758 [bus debug] start request 31
2023-12-25 10:10:04.758 [bus debug] arbitration start with 31
2023-12-25 10:10:05.229 [bus debug] arbitration won
2023-12-25 10:10:05.229 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:05.229 [bus debug] switching from ready to send command
2023-12-25 10:10:05.254 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:05.281 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:05.308 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:05.339 [bus debug] send/receive symbol latency 29 ms
2023-12-25 10:10:05.339 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:05.365 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:05.365 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:05.430 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:05.430 [bus info] scan 0c cmd: 310c070400
2023-12-25 10:10:05.430 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:05.431 [bus debug] start request 31
2023-12-25 10:10:05.431 [bus debug] arbitration start with 31
2023-12-25 10:10:05.971 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:10:05.998 [bus debug] arbitration won
2023-12-25 10:10:05.998 [bus debug] arbitration delay 76 micros
2023-12-25 10:10:05.998 [bus debug] switching from ready to send command
2023-12-25 10:10:06.023 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:06.048 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:06.074 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:06.101 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:06.101 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:06.128 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:06.128 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:06.193 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:06.193 [bus info] scan 0d cmd: 310d070400
2023-12-25 10:10:06.193 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:06.193 [bus debug] start request 31
2023-12-25 10:10:06.193 [bus debug] arbitration start with 31
2023-12-25 10:10:06.655 [bus debug] arbitration won
2023-12-25 10:10:06.655 [bus debug] arbitration delay 1 micros
2023-12-25 10:10:06.655 [bus debug] switching from ready to send command
2023-12-25 10:10:06.686 [bus debug] send/receive symbol latency 31 ms
2023-12-25 10:10:06.721 [bus debug] send/receive symbol latency 34 ms
2023-12-25 10:10:06.746 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:06.772 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:06.772 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:06.797 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:06.797 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:06.862 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:06.863 [bus info] scan 0e cmd: 310e070400
2023-12-25 10:10:06.863 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:06.863 [bus debug] start request 31
2023-12-25 10:10:06.863 [bus debug] arbitration start with 31
2023-12-25 10:10:07.191 [main debug] performing regular tasks
2023-12-25 10:10:07.305 [bus debug] arbitration lost
2023-12-25 10:10:07.305 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:07.388 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:07.388 [bus debug] start request 31
2023-12-25 10:10:07.388 [bus debug] arbitration start with 31
2023-12-25 10:10:07.840 [bus debug] arbitration lost
2023-12-25 10:10:07.840 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:07.922 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:07.925 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:07.925 [bus debug] start request 31
2023-12-25 10:10:07.925 [bus debug] arbitration start with 31
2023-12-25 10:10:07.967 [bus debug] arbitration lost
2023-12-25 10:10:07.967 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:08.096 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:08.096 [bus debug] start request 31
2023-12-25 10:10:08.096 [bus debug] arbitration start with 31
2023-12-25 10:10:08.560 [bus debug] arbitration won
2023-12-25 10:10:08.560 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:08.560 [bus debug] switching from ready to send command
2023-12-25 10:10:08.586 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:08.613 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:08.639 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:08.665 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:08.665 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:08.715 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:08.715 [bus info] scan 12 cmd: 3112070400
2023-12-25 10:10:08.715 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:08.715 [bus debug] start request 31
2023-12-25 10:10:08.715 [bus debug] arbitration start with 31
2023-12-25 10:10:09.171 [bus debug] arbitration lost
2023-12-25 10:10:09.171 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:09.254 [bus debug] ERR: read timeout during receive command, switching to skip
2023-12-25 10:10:09.254 [bus debug] start request 31
2023-12-25 10:10:09.254 [bus debug] arbitration start with 31
2023-12-25 10:10:09.735 [bus debug] arbitration won
2023-12-25 10:10:09.735 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:09.735 [bus debug] switching from ready to send command
2023-12-25 10:10:09.759 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:09.787 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:09.816 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:09.843 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:09.843 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:09.893 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:09.893 [bus info] scan 14 cmd: 3114070400
2023-12-25 10:10:09.893 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:09.893 [bus debug] start request 31
2023-12-25 10:10:09.893 [bus debug] arbitration start with 31
2023-12-25 10:10:10.348 [bus debug] arbitration lost
2023-12-25 10:10:10.349 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:10.426 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:10.431 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:10.431 [bus debug] start request 31
2023-12-25 10:10:10.431 [bus debug] arbitration start with 31
2023-12-25 10:10:10.484 [bus debug] arbitration won
2023-12-25 10:10:10.484 [bus debug] arbitration delay 3 micros
2023-12-25 10:10:10.484 [bus debug] switching from ready to send command
2023-12-25 10:10:10.510 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:10.538 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:10.565 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:10.592 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:10.592 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:10.642 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:10.642 [bus info] scan 15 cmd: 3115070400
2023-12-25 10:10:10.642 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:10.642 [bus debug] start request 31
2023-12-25 10:10:10.642 [bus debug] arbitration start with 31
2023-12-25 10:10:11.120 [bus debug] arbitration won
2023-12-25 10:10:11.120 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:11.120 [bus debug] switching from ready to send command
2023-12-25 10:10:11.147 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:11.179 [bus debug] send/receive symbol latency 31 ms
2023-12-25 10:10:11.206 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:11.231 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:11.232 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:11.282 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:11.282 [bus info] scan 16 cmd: 3116070400
2023-12-25 10:10:11.282 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:11.282 [bus debug] start request 31
2023-12-25 10:10:11.282 [bus debug] arbitration start with 31
2023-12-25 10:10:11.761 [bus debug] arbitration won
2023-12-25 10:10:11.762 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:11.762 [bus debug] switching from ready to send command
2023-12-25 10:10:11.787 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:11.814 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:11.839 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:11.864 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:11.864 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:11.893 [bus debug] send/receive symbol latency 29 ms
2023-12-25 10:10:11.893 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:11.958 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:11.959 [bus info] scan 18 cmd: 3118070400
2023-12-25 10:10:11.959 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:11.959 [bus debug] start request 31
2023-12-25 10:10:11.959 [bus debug] arbitration start with 31
2023-12-25 10:10:12.399 [bus debug] arbitration lost
2023-12-25 10:10:12.399 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:12.471 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:12.477 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:12.477 [bus debug] start request 31
2023-12-25 10:10:12.477 [bus debug] arbitration start with 31
2023-12-25 10:10:12.484 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-25 10:10:12.488 [bus debug] arbitration lost
2023-12-25 10:10:12.488 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:12.564 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:12.570 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:12.570 [bus debug] start request 31
2023-12-25 10:10:12.570 [bus debug] arbitration start with 31
2023-12-25 10:10:12.640 [bus debug] arbitration won
2023-12-25 10:10:12.640 [bus debug] arbitration delay 1 micros
2023-12-25 10:10:12.640 [bus debug] switching from ready to send command
2023-12-25 10:10:12.666 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:12.693 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:12.727 [bus debug] send/receive symbol latency 33 ms
2023-12-25 10:10:12.754 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:12.754 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:12.782 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:12.782 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:12.786 [bus debug] switching from receive command ACK to receive response
2023-12-25 10:10:12.830 [bus debug] switching from receive response to receive response CRC
2023-12-25 10:10:12.834 [bus debug] notify request: ERR: CRC error
2023-12-25 10:10:12.834 [bus info] scan 19 cmd: 3119070400
2023-12-25 10:10:12.834 [bus debug] ERR: CRC error during receive response CRC, switching to send response ACK
2023-12-25 10:10:12.926 [bus debug] ERR: read timeout during send response ACK, switching to skip
2023-12-25 10:10:12.926 [bus debug] start request 31
2023-12-25 10:10:12.926 [bus debug] arbitration start with 31
2023-12-25 10:10:13.370 [bus debug] arbitration won
2023-12-25 10:10:13.370 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:13.370 [bus debug] switching from ready to send command
2023-12-25 10:10:13.400 [bus debug] send/receive symbol latency 29 ms
2023-12-25 10:10:13.425 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:13.450 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:13.479 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:13.479 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:13.504 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:13.504 [bus debug] switching from send command CRC to receive command ACK
2023-12-25 10:10:13.570 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:13.570 [bus info] scan 1a cmd: 311a070400
2023-12-25 10:10:13.570 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-25 10:10:13.570 [bus debug] start request 31
2023-12-25 10:10:13.570 [bus debug] arbitration start with 31
2023-12-25 10:10:14.036 [bus debug] arbitration won
2023-12-25 10:10:14.036 [bus debug] arbitration delay 1 micros
2023-12-25 10:10:14.036 [bus debug] switching from ready to send command
2023-12-25 10:10:14.064 [bus debug] send/receive symbol latency 27 ms
2023-12-25 10:10:14.089 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:14.114 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:14.143 [bus debug] send/receive symbol latency 29 ms
2023-12-25 10:10:14.143 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:14.194 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:14.194 [bus info] scan 1b cmd: 311b070400
2023-12-25 10:10:14.194 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:14.194 [bus debug] start request 31
2023-12-25 10:10:14.194 [bus debug] arbitration start with 31
2023-12-25 10:10:14.647 [bus debug] arbitration lost
2023-12-25 10:10:14.648 [bus debug] ERR: arbitration lost during ready, retry
2023-12-25 10:10:14.730 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:14.736 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:14.736 [bus debug] start request 31
2023-12-25 10:10:14.736 [bus debug] arbitration start with 31
2023-12-25 10:10:14.854 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2023-12-25 10:10:14.859 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2023-12-25 10:10:14.890 [bus debug] arbitration won
2023-12-25 10:10:14.890 [bus debug] arbitration delay 3 micros
2023-12-25 10:10:14.890 [bus debug] switching from ready to send command
2023-12-25 10:10:14.916 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:14.941 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:14.967 [bus debug] send/receive symbol latency 25 ms
2023-12-25 10:10:14.992 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:14.992 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:15.042 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:15.042 [bus info] scan 1c cmd: 311c070400
2023-12-25 10:10:15.042 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:15.042 [bus debug] start request 31
2023-12-25 10:10:15.042 [bus debug] arbitration start with 31
2023-12-25 10:10:15.518 [bus debug] arbitration won
2023-12-25 10:10:15.518 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:15.518 [bus debug] switching from ready to send command
2023-12-25 10:10:15.543 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:15.572 [bus debug] send/receive symbol latency 29 ms
2023-12-25 10:10:15.602 [bus debug] send/receive symbol latency 30 ms
2023-12-25 10:10:15.628 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:15.629 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:15.679 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:15.679 [bus info] scan 1d cmd: 311d070400
2023-12-25 10:10:15.679 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:15.679 [bus debug] start request 31
2023-12-25 10:10:15.679 [bus debug] arbitration start with 31
2023-12-25 10:10:16.154 [bus debug] arbitration won
2023-12-25 10:10:16.154 [bus debug] arbitration delay 2 micros
2023-12-25 10:10:16.154 [bus debug] switching from ready to send command
2023-12-25 10:10:16.179 [bus debug] send/receive symbol latency 24 ms
2023-12-25 10:10:16.209 [bus debug] send/receive symbol latency 30 ms
2023-12-25 10:10:16.235 [bus debug] send/receive symbol latency 26 ms
2023-12-25 10:10:16.264 [bus debug] send/receive symbol latency 28 ms
2023-12-25 10:10:16.264 [bus debug] switching from send command to send command CRC
2023-12-25 10:10:16.314 [bus debug] notify request: ERR: read timeout
2023-12-25 10:10:16.314 [bus info] scan 1e cmd: 311e070400
2023-12-25 10:10:16.314 [bus debug] ERR: read timeout during send command CRC, switching to skip
2023-12-25 10:10:16.314 [bus debug] start request 31
2023-12-25 10:10:16.314 [bus debug] arbitration start with 31
2023-12-25 10:10:16.770 [bus debug] arbitration lost

jkriegl

Versuche auf ein neues OS zu wechseln.
Alles klappt nur der ebusd will nicht starten. Bekomme die Fehlermeldung
Process: 1738 ExecStart=/usr/bin/ebusd $EBUSD_OPTS (code=exited, status=22)
mit meinen alten EBUSD_OPTS
EBUSD_OPTS="--logfile /var/log/ebusd.log --loglevel error -d /dev/ttyUSB0"
funktionieren also nicht mehr.
Mit dem alten wheezy und einem esera lief das ganze viele Jahre lang. Was ist dabei exited oder fehlt?
Rpi 3, Fhem, Cul 868, HM-CC-RT-DN, HM-Sec-Sco, HM-ES-PMSw1-Pl, ebus (Vaillant), ECMD, Telegram, HTTPMOD, Xiaomi, Shelly

tonyf

ich vermute, /dev/ttyUSB0 ist evtl. anderweitig belegt.
Ich verwende immer "by-id": hier bei mir z.Bsp. -d /dev/serial/by-id/usb-ESERA_GmbH_eBus_Coupler_12001_AL7Q1H71-if00-port0
INTEL DN2820FYKH NUC: 4 gb, 250 ssd hd als nas, fhem 5.6
cul 433 - IT aktoren - relaiskarte an raspberry pi

jkriegl

[gelöst]
nach 2.x ist -c, --configpath=PATH zwingend notwendig, falls eine eigene Konfiguration benutzt wird.
Rpi 3, Fhem, Cul 868, HM-CC-RT-DN, HM-Sec-Sco, HM-ES-PMSw1-Pl, ebus (Vaillant), ECMD, Telegram, HTTPMOD, Xiaomi, Shelly

SMWMK

Hallo,

wir suchen nach der Beschreibung einer Schnittstelle für Vaillant Wärmepumpen.

Wir wollen diverse Sachen machen:
1) Rauslesen der Vorlauf-, Rücklauftemeperatur, der Temperatur im Warmwasserkessel und evtl. auch der Außentemperatur
2) Steuerung des Einschalten oder Abschalten der Wärmepumpe

Kann uns jemand dabei behilflich sein? Wir sind auch bereit für diese Leistung zu bezahlen.

Danke und viele Grüße



theotherhalf

#3413
Hallo!

Nachdem ich mein komplettes System nach SD Kartencrash wieder neu einrichten musste (Backup war 1.5 Jahre alt...), habe ich alles wieder soweit zum Laufen gebracht.
Die Verbindung zu meiner Vaillant Therme und meinem Regler jedoch läuft noch nicht ganz rund.
Eigentlich möchte ich beide per mqtt anbinden. Im Moment läuft es noch über GAEBUS. Ausserdem stirbt so langsam das Display meines Reglers sodaß es schön wäre zukünftig auch den einen oder anderen Parameter von FHEM ändern zu können. Derzeit lese ich nur.
Etwas seltsam ist, das ich über GAEBUS mehr Daten empfange als über mqtt. Hier liste ich einmal die Therme auf.

GAEBUS:
define EcoTec196VC3_5_GAEBUS GAEBUS 192.168.178.10:8889 60
attr EcoTec196VC3_5_GAEBUS userattr r_bai_AITemp r_bai_FanSpeed r_bai_FlowTemp r_bai_Gasvalve r_bai_PartloadHcKW r_bai_PartloadHwcKW r_bai_PositionValveSet r_bai_PowerValue r_bai_ReturnTemp r_bai_StorageTemp r_bai_StorageTempDesired r_bai_TargetFanSpeed r_bai_WP r_bai_WaterPressure r_bai_externalFlowTempDesired
attr EcoTec196VC3_5_GAEBUS icon usb
attr EcoTec196VC3_5_GAEBUS mapVar maintenancedata_HwcTempMax|expertlevel_ReturnTemp
attr EcoTec196VC3_5_GAEBUS r_bai_AITemp Abgastemperatur
attr EcoTec196VC3_5_GAEBUS r_bai_FanSpeed Luefterdrehzahl_Ist
attr EcoTec196VC3_5_GAEBUS r_bai_FlowTemp Vorlauftemperatur
attr EcoTec196VC3_5_GAEBUS r_bai_Gasvalve Gasventil
attr EcoTec196VC3_5_GAEBUS r_bai_PartloadHcKW Heizungsteillast
attr EcoTec196VC3_5_GAEBUS r_bai_PartloadHwcKW Speicherteillast
attr EcoTec196VC3_5_GAEBUS r_bai_PositionValveSet Umschaltventil
attr EcoTec196VC3_5_GAEBUS r_bai_PowerValue Leistungsdaten
attr EcoTec196VC3_5_GAEBUS r_bai_ReturnTemp Ruecklauftemperatur
attr EcoTec196VC3_5_GAEBUS r_bai_StorageTemp Brauchwasserspeicher_Temperatur_Ist
attr EcoTec196VC3_5_GAEBUS r_bai_StorageTempDesired Brauchwasserspeicher_Temperatur_Soll
attr EcoTec196VC3_5_GAEBUS r_bai_TargetFanSpeed Luefterdrehzahl_Soll
attr EcoTec196VC3_5_GAEBUS r_bai_WP Zirkulationspumpe
attr EcoTec196VC3_5_GAEBUS r_bai_WaterPressure Wasserdruck
attr EcoTec196VC3_5_GAEBUS r_bai_externalFlowTempDesired Vorlauf_Soll_von_7-8-9
attr EcoTec196VC3_5_GAEBUS room Heizung
#   DEF        192.168.178.10:8889 60
#   DevType    EBUSD
#   DeviceAddress 192.168.178.10:8889
#   DeviceName EcoTec196VC3_5_GAEBUS
#   FD         17
#   FUUID      634d2250-f33f-0f31-80b0-6dfa84af667088d4
#   Interval   60
#   NAME       EcoTec196VC3_5_GAEBUS
#   NR         260
#   PARTIAL   
#   STATE      Connected
#   TYPE       GAEBUS
#   UpdateCnt  10
#   eventCount 10
#   READINGS:
#     2024-10-19 21:24:47   Abgastemperatur 0.00
#     2024-10-19 21:24:47   Brauchwasserspeicher_Temperatur_Ist 54.62
#     2024-10-19 21:24:47   Brauchwasserspeicher_Temperatur_Soll 57.00
#     2024-10-19 21:24:47   Gasventil       off
#     2024-10-19 21:24:47   Heizungsteillast 14
#     2024-10-19 21:24:47   Leistungsdaten  19 06 53 13 64 17
#     2024-10-19 21:24:47   Luefterdrehzahl_Ist 0
#     2024-10-19 21:24:47   Luefterdrehzahl_Soll 0
#     2024-10-19 21:24:47   Ruecklauftemperatur 34.50
#     2024-10-19 21:24:47   Speicherteillast 23
#     2024-10-19 21:24:47   Umschaltventil  100
#     2024-10-19 21:24:47   Vorlauf_Soll_von_7-8-9 0.00
#     2024-10-19 21:24:47   Vorlauftemperatur 36.19
#     2024-10-19 21:24:47   Wasserdruck     1.178
#     2024-10-19 21:24:47   Zirkulationspumpe off
#     2024-10-11 18:46:30   lasterror       ERR: element not found
#     2024-10-19 21:24:47   state_ebus      signal acquired
#   helper:
#     ebus:
#       r_bai_AITemp:
#         class      bai
#         io         r
#         var        AITemp
#       r_bai_FanSpeed:
#         class      bai
#         io         r
#         var        FanSpeed
#       r_bai_FlowTemp:
#         class      bai
#         io         r
#         var        FlowTemp
#       r_bai_Gasvalve:
#         class      bai
#         io         r
#         var        Gasvalve
#       r_bai_PartloadHcKW:
#         class      bai
#         io         r
#         var        PartloadHcKW
#       r_bai_PartloadHwcKW:
#         class      bai
#         io         r
#         var        PartloadHwcKW
#       r_bai_PositionValveSet:
#         class      bai
#         io         r
#         var        PositionValveSet
#       r_bai_PowerValue:
#         class      bai
#         io         r
#         var        PowerValue
#       r_bai_ReturnTemp:
#         class      bai
#         io         r
#         var        ReturnTemp
#       r_bai_StorageTemp:
#         class      bai
#         io         r
#         var        StorageTemp
#       r_bai_StorageTempDesired:
#         class      bai
#         io         r
#         var        StorageTempDesired
#       r_bai_TargetFanSpeed:
#         class      bai
#         io         r
#         var        TargetFanSpeed
#       r_bai_WP:
#         class      bai
#         io         r
#         var        WP
#       r_bai_WaterPressure:
#         class      bai
#         io         r
#         var        WaterPressure
#       r_bai_externalFlowTempDesired:
#         class      bai
#         io         r
#         var        externalFlowTempDesired
#
setstate EcoTec196VC3_5_GAEBUS Connected
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Abgastemperatur 0.00
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Brauchwasserspeicher_Temperatur_Ist 54.62
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Brauchwasserspeicher_Temperatur_Soll 57.00
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Gasventil off
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Heizungsteillast 14
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Leistungsdaten 19 06 53 13 64 17
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Luefterdrehzahl_Ist 0
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Luefterdrehzahl_Soll 0
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Ruecklauftemperatur 34.50
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Speicherteillast 23
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Umschaltventil 100
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Vorlauf_Soll_von_7-8-9 0.00
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Vorlauftemperatur 36.19
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Wasserdruck 1.178
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 Zirkulationspumpe off
setstate EcoTec196VC3_5_GAEBUS 2024-10-11 18:46:30 lasterror ERR: element not found
setstate EcoTec196VC3_5_GAEBUS 2024-10-19 21:24:47 state_ebus signal acquired
MQTT:
define MQTT2_ebusd_23.3_1123 MQTT2_DEVICE ebusd_23.3_1123
attr MQTT2_ebusd_23.3_1123 readingList ebusd_23.3_1123:ebusd/global/version:.* version\
ebusd_23.3_1123:ebusd/global/running:.* running\
ebusd_23.3_1123:ebusd/global/uptime:.* uptime\
ebusd_23.3_1123:ebusd/global/signal:.* signal\
ebusd_23.3_1123:ebusd/broadcast/queryexistence:.* queryexistence\
ebusd_23.3_1123:ebusd/global/scan:.* scan\
ebusd_23.3_1123:ebusd/global/updatecheck:.* updatecheck\
ebusd_23.3_1123:ebusd/scan\x2e08/:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/scan\x2e08/id:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/FlowTemp:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/AITemp:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/FanSpeed:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/PartloadHcKW:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/PartloadHwcKW:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/PositionValveSet:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/Gasvalve:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/StorageTemp:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/ReturnTemp:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/PowerValue:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/WaterPressure:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/StorageTempDesired:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/TargetFanSpeed:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/externalFlowTempDesired:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/bai/WP:.* { json2nameValue($EVENT) }\
ebusd_23.3_1123:ebusd/broadcast/error:.* { json2nameValue($EVENT) }
attr MQTT2_ebusd_23.3_1123 room MQTT2_DEVICE
#   CID        ebusd_23.3_1123
#   DEF        ebusd_23.3_1123
#   FUUID      67095581-f33f-0f31-723b-d2644016721e3dae
#   IODev      myBroker
#   LASTInputDev myBroker
#   MSGCNT     254
#   NAME       MQTT2_ebusd_23.3_1123
#   NR         403
#   STATE      ???
#   TYPE       MQTT2_DEVICE
#   eventCount 254
#   myBroker_CONN myBroker_192.168.178.10_40024
#   myBroker_MSGCNT 254
#   myBroker_TIME 2024-10-19 21:29:10
#   READINGS:
#     2024-10-19 21:29:10   0_name         
#     2024-10-19 21:29:10   0_value         0
#     2024-10-11 18:46:59   HW_value        7401
#     2024-10-11 18:46:59   ID_value        BAI00
#     2024-10-19 21:14:27   IODev           myBroker
#     2024-10-11 18:46:59   MF_value        Vaillant
#     2024-10-11 18:46:59   SW_value        0518
#     2024-10-11 18:47:01   counter_value   
#     2024-10-13 15:09:53   error_value     BAI
#     2024-10-19 21:29:10   onoff_value     off
#     2024-10-19 21:29:04   power_value     23
#     2024-10-11 18:47:01   prefix_value   
#     2024-10-19 21:29:10   press_value     1.178
#     2024-10-11 18:47:01   product_value   
#     2024-10-11 18:42:56   queryexistence 
#     2024-10-19 21:15:28   running         true
#     2024-10-11 18:47:01   scan            "finished"
#     2024-10-19 21:29:10   sensor_value    ok
#     2024-10-19 21:15:03   signal          true
#     2024-10-19 21:15:28   subscriptions   ebusd/#
#     2024-10-11 18:47:01   suffix_value   
#     2024-10-11 18:47:01   supplier_value 
#     2024-10-19 21:29:10   temp_value      0.00
#     2024-10-19 21:29:04   tempmirror_value 64986
#     2024-10-11 18:44:46   updatecheck     "OK"
#     2024-10-19 21:29:07   uptime          701187
#     2024-10-19 21:15:28   version         "ebusd 23.3.23.3"
#     2024-10-11 18:47:01   week_value     
#     2024-10-11 18:47:01   year_value     
#
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 0_name
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 0_value 0
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:46:59 HW_value 7401
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:46:59 ID_value BAI00
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:14:27 IODev myBroker
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:46:59 MF_value Vaillant
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:46:59 SW_value 0518
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 counter_value
setstate MQTT2_ebusd_23.3_1123 2024-10-13 15:09:53 error_value BAI
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 onoff_value off
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:04 power_value 23
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 prefix_value
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 press_value 1.178
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 product_value
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:42:56 queryexistence
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:15:28 running true
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 scan "finished"
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 sensor_value ok
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:15:03 signal true
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:15:28 subscriptions ebusd/#
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 suffix_value
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 supplier_value
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:10 temp_value 0.00
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:04 tempmirror_value 64986
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:44:46 updatecheck "OK"
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:29:07 uptime 701187
setstate MQTT2_ebusd_23.3_1123 2024-10-19 21:15:28 version "ebusd 23.3.23.3"
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 week_value
setstate MQTT2_ebusd_23.3_1123 2024-10-11 18:47:01 year_value


Derzeit sehe ich nicht, warum nicht die kompletten Daten übertragen werden.
Welche Übertragungsart wäre grundsätzlich besser geeignet Parameter von FHEM zu den Geräten zu senden?
FHEM Anfänger
HM CCU2 mit diversen Komponenten als Steuerung
FHEM mit Floorplan auf Raspi 3 (Raspbian Jessie)  zur Visualisierung (Heizung, Zustände, etc.) und angeschlossenen One-Wire Sensoren
Schnittstelle CCU2 - FHEM mit HMCCU
EBUSD Applikation auf Raspi 2 mit Anbindung an Vaillant Heizung

theotherhalf

Kann mir jemand zu diesem Thema helfen?
FHEM Anfänger
HM CCU2 mit diversen Komponenten als Steuerung
FHEM mit Floorplan auf Raspi 3 (Raspbian Jessie)  zur Visualisierung (Heizung, Zustände, etc.) und angeschlossenen One-Wire Sensoren
Schnittstelle CCU2 - FHEM mit HMCCU
EBUSD Applikation auf Raspi 2 mit Anbindung an Vaillant Heizung

Prof. Dr. Peter Henning

Sinnlose Frage. Beides führt auf den ebusd, der kommuniziert mit der Therme.

LG

pah

theotherhalf

Meine Frage war ja, warum ich mit MQTT2 nicht die gleichen Readings erhalte wie mit GAEBUS
FHEM Anfänger
HM CCU2 mit diversen Komponenten als Steuerung
FHEM mit Floorplan auf Raspi 3 (Raspbian Jessie)  zur Visualisierung (Heizung, Zustände, etc.) und angeschlossenen One-Wire Sensoren
Schnittstelle CCU2 - FHEM mit HMCCU
EBUSD Applikation auf Raspi 2 mit Anbindung an Vaillant Heizung

m8haben

Moin zusammen,
nachdem meine Heizungssteuerung immer problemlos lief, und ich auch mit GAEBUS meinen ecoVit prima steuern konnte, wenn ich mal die Teillast erhöhen wollte, muss ich jetzt feststellen, dass es nicht mehr funktioniert. Was ist passiert? Ich habe nach langer Zeit ein update auf meinem raspi vorgenommen und auch gleich mal ein update von FHEM und jetzt kann ich die Teillast nicht mehr verändern. Von der Konsole aus geht es nicht und mit GAEBUS auch nicht mehr. Egal welchen Wert ich eintrage und setze es passiert am Kessel nichts. Warum??? Der Befehl PartloadHcKW verändert nichts. Mache ich einen read sehe ich z.B. den Wert 15. Schreibe ich dann z.B. 8 lese ich auch 8 aber an dem Kessel tut sich gar nichts. Was ist los???
Gruß Roland
Rpi 2, Fhem, ebus (Vaillant), ECMD

Prof. Dr. Peter Henning

Zitat von: theotherhalf am 13 November 2024, 19:35:56Meine Frage war ja, warum ich mit MQTT2 nicht die gleichen Readings erhalte wie mit GAEBUS
Weil das unterschiedliche Systeme sind, um auf den ebusd zuzugreifen.  ::)

LG

pah