[Modul] ebusdMQTT - Einbindung von Vaillant Geräten

Hallo bumaas,

Leider kann ich keine Anhänge hochladen als neuer Nutzer (Obwohl ich schon fast 10Jahre IP-Symcon Nutze :slight_smile: )
Im Zweiten bild in der Anleitung steht dass man für EEBUS im selben Netzwerk als das IP-Gateway sein muss. Daraus schließe ich eigentlich dass hier eine direktverbindung möglich sein sollte.

Das Log file finde ich wenig spannend, da ich hier noch keine daten eingegeben habe, ist quasi nicht konfiguriert. Was würdest du unter User und Passwort eintragen?
Auch Port ist eine gute frage da ich keine info vom hersteller habe.

Vielen Dank, Wolfgang

Hier noch die Anleitung:

Mein Logfile sieht so aus:

0.921 [device notice] transport opened
2025-01-22 18:19:50.921 [main info] registering data handlers
2025-01-22 18:19:50.921 [main info] registered data handlers
2025-01-22 18:19:50.922 [main notice] ebusd 24.1.24.1 started with full scan on device: 192.168.1.30:9999, TCP
2025-01-22 18:19:50.922 [main info] loading configuration files from /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/
2025-01-22 18:19:50.922 [main debug] reading directory /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/
2025-01-22 18:19:50.922 [main debug] file type of /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/_templates.csv is file
2025-01-22 18:19:50.922 [main debug] file type of /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/broadcast.csv is file
2025-01-22 18:19:50.922 [main debug] file type of /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/vaillant is dir
2025-01-22 18:19:50.922 [main debug] file type of /home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de/memory.csv is file
2025-01-22 18:19:50.922 [main info] reading templates /
2025-01-22 18:19:50.924 [main info] read templates in /
2025-01-22 18:19:50.924 [main info] reading file broadcast.csv
2025-01-22 18:19:50.927 [main info] successfully read file broadcast.csv
2025-01-22 18:19:50.927 [main info] reading file memory.csv
2025-01-22 18:19:50.928 [main info] successfully read file memory.csv
2025-01-22 18:19:50.929 [main info] read config files, got 11 messages
2025-01-22 18:19:50.929 [bus notice] bus started with own address ff/04
2025-01-22 18:19:50.935 [bus notice] signal acquired
2025-01-22 18:19:52.610 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:19:52.614 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:19:54.559 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:19:54.563 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:19:54.837 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:19:56.650 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:19:56.656 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:00.930 [main debug] performing regular tasks
2025-01-22 18:20:00.930 [main notice] starting initial full scan
2025-01-22 18:20:00.930 [bus info] scan 02 cmd: ff02070400
2025-01-22 18:20:00.948 [network info] [00001] client connection opened 127.0.0.1
2025-01-22 18:20:00.949 [network debug] [00001] wait for result
2025-01-22 18:20:00.949 [main debug] >>> info
2025-01-22 18:20:00.949 [main debug] <<< version: ebusd 24.1.24.1
device: 192.168.1.30:9999, TCP

Danach eine Art Dauerschleife …

2025-01-22 18:20:00.950 [network info] [00001] connection closed
2025-01-22 18:20:01.949 [network debug] dead connection removed - 0
2025-01-22 18:20:02.719 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:02.724 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:06.704 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:06.709 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:06.721 [bus debug] start request ff
2025-01-22 18:20:06.721 [bus debug] arbitration start with ff
2025-01-22 18:20:06.811 [bus debug] arbitration lost
2025-01-22 18:20:06.811 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:10.789 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:10.793 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:10.949 [main debug] performing regular tasks
2025-01-22 18:20:12.801 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:12.802 [bus debug] start request ff
2025-01-22 18:20:12.802 [bus debug] arbitration start with ff
2025-01-22 18:20:12.891 [bus debug] arbitration lost
2025-01-22 18:20:12.892 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:13.053 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:13.053 [bus debug] start request ff
2025-01-22 18:20:13.053 [bus debug] arbitration start with ff
2025-01-22 18:20:13.146 [bus debug] arbitration lost
2025-01-22 18:20:13.146 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:13.922 [network info] [00002] client connection opened 127.0.0.1
2025-01-22 18:20:13.923 [network debug] [00002] wait for result
2025-01-22 18:20:13.923 [main debug] >>> info
2025-01-22 18:20:13.923 [main debug] <<< version: ebusd 24.1.24.1
device: 192.168.1.30:9999, TCP
access: *
signal: acquired
symbol rate: 64
m ...
2025-01-22 18:20:13.925 [network info] [00002] connection closed
2025-01-22 18:20:14.924 [network debug] dead connection removed - 0
2025-01-22 18:20:16.850 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:16.854 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:16.866 [bus debug] start request ff
2025-01-22 18:20:16.867 [bus debug] arbitration start with ff
2025-01-22 18:20:16.960 [bus debug] arbitration lost
2025-01-22 18:20:16.960 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:20:16.960 [bus info] scan 04 cmd: ff04070400
2025-01-22 18:20:18.923 [main debug] performing regular tasks
2025-01-22 18:20:20.899 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:20.903 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:22.849 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:22.853 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:22.903 [bus debug] start request ff
2025-01-22 18:20:22.903 [bus debug] arbitration start with ff
2025-01-22 18:20:22.995 [bus debug] arbitration lost
2025-01-22 18:20:22.995 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:23.169 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:23.169 [bus debug] start request ff
2025-01-22 18:20:23.169 [bus debug] arbitration start with ff
2025-01-22 18:20:23.259 [bus debug] arbitration lost
2025-01-22 18:20:23.259 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:26.926 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:26.930 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:26.943 [bus debug] start request ff
2025-01-22 18:20:26.943 [bus debug] arbitration start with ff
2025-01-22 18:20:27.032 [bus debug] arbitration lost
2025-01-22 18:20:27.033 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:28.924 [main debug] performing regular tasks
2025-01-22 18:20:30.970 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:30.970 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:32.953 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:32.953 [bus debug] start request ff
2025-01-22 18:20:32.953 [bus debug] arbitration start with ff
2025-01-22 18:20:33.050 [bus debug] arbitration lost
2025-01-22 18:20:33.050 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:20:33.050 [bus info] scan 05 cmd: ff05070400
2025-01-22 18:20:37.026 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:37.030 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:37.044 [bus debug] start request ff
2025-01-22 18:20:37.044 [bus debug] arbitration start with ff
2025-01-22 18:20:37.137 [bus debug] arbitration lost
2025-01-22 18:20:37.137 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:38.924 [main debug] performing regular tasks
2025-01-22 18:20:41.123 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:41.127 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:43.111 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:43.111 [bus debug] start request ff
2025-01-22 18:20:43.111 [bus debug] arbitration start with ff
2025-01-22 18:20:43.203 [bus debug] arbitration lost
2025-01-22 18:20:43.204 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:45.139 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:45.143 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:45.156 [bus debug] start request ff
2025-01-22 18:20:45.156 [bus debug] arbitration start with ff
2025-01-22 18:20:45.247 [bus debug] arbitration lost
2025-01-22 18:20:45.247 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:48.924 [main debug] performing regular tasks
2025-01-22 18:20:51.165 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:51.169 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:53.162 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:53.166 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:53.217 [bus debug] start request ff
2025-01-22 18:20:53.217 [bus debug] arbitration start with ff
2025-01-22 18:20:53.306 [bus debug] arbitration lost
2025-01-22 18:20:53.306 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:20:53.306 [bus info] scan 06 cmd: ff06070400
2025-01-22 18:20:53.437 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:20:53.437 [bus debug] start request ff
2025-01-22 18:20:53.438 [bus debug] arbitration start with ff
2025-01-22 18:20:53.527 [bus debug] arbitration lost
2025-01-22 18:20:53.527 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:55.197 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:20:55.201 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:20:55.214 [bus debug] start request ff
2025-01-22 18:20:55.214 [bus debug] arbitration start with ff
2025-01-22 18:20:55.309 [bus debug] arbitration lost
2025-01-22 18:20:55.309 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:20:58.925 [main debug] performing regular tasks
2025-01-22 18:21:01.312 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:01.317 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:01.325 [bus debug] start request ff
2025-01-22 18:21:01.325 [bus debug] arbitration start with ff
2025-01-22 18:21:01.412 [bus debug] arbitration lost
2025-01-22 18:21:01.412 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:05.343 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:05.347 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:05.360 [bus debug] start request ff
2025-01-22 18:21:05.360 [bus debug] arbitration start with ff
2025-01-22 18:21:05.453 [bus debug] arbitration lost
2025-01-22 18:21:05.454 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:21:05.454 [bus info] scan 08 cmd: ff08070400
2025-01-22 18:21:08.925 [main debug] performing regular tasks
2025-01-22 18:21:08.925 [main notice] scan completed 1 time(s), check again
2025-01-22 18:21:11.372 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:11.376 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:11.381 [bus debug] start request ff
2025-01-22 18:21:11.381 [bus debug] arbitration start with ff
2025-01-22 18:21:11.472 [bus debug] arbitration lost
2025-01-22 18:21:11.472 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:13.435 [bus debug] ERR: invalid escape sequence during receive command, switching to skip
2025-01-22 18:21:13.690 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:21:13.690 [bus debug] start request ff
2025-01-22 18:21:13.690 [bus debug] arbitration start with ff
2025-01-22 18:21:13.779 [bus debug] arbitration lost
2025-01-22 18:21:13.779 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:15.404 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:15.408 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:15.420 [bus debug] start request ff
2025-01-22 18:21:15.420 [bus debug] arbitration start with ff
2025-01-22 18:21:15.508 [bus debug] arbitration lost
2025-01-22 18:21:15.508 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:18.926 [main debug] performing regular tasks
2025-01-22 18:21:19.451 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:19.455 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:19.459 [bus debug] start request ff
2025-01-22 18:21:19.459 [bus debug] arbitration start with ff
2025-01-22 18:21:19.547 [bus debug] arbitration lost
2025-01-22 18:21:19.547 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:21:19.547 [bus info] scan 09 cmd: ff09070400
2025-01-22 18:21:21.462 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:21.467 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:21.516 [bus debug] start request ff
2025-01-22 18:21:21.516 [bus debug] arbitration start with ff
2025-01-22 18:21:21.606 [bus debug] arbitration lost
2025-01-22 18:21:21.606 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:21.784 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:21:21.784 [bus debug] start request ff
2025-01-22 18:21:21.784 [bus debug] arbitration start with ff
2025-01-22 18:21:21.874 [bus debug] arbitration lost
2025-01-22 18:21:21.875 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:25.545 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:25.549 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:25.562 [bus debug] start request ff
2025-01-22 18:21:25.562 [bus debug] arbitration start with ff
2025-01-22 18:21:25.652 [bus debug] arbitration lost
2025-01-22 18:21:25.652 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:28.926 [main debug] performing regular tasks
2025-01-22 18:21:29.579 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:29.583 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:29.588 [bus debug] start request ff
2025-01-22 18:21:29.588 [bus debug] arbitration start with ff
2025-01-22 18:21:29.677 [bus debug] arbitration lost
2025-01-22 18:21:29.677 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:21:29.677 [bus info] scan 0a cmd: ff0a070400
2025-01-22 18:21:31.532 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:21:31.532 [bus debug] start request ff
2025-01-22 18:21:31.532 [bus debug] arbitration start with ff
2025-01-22 18:21:31.624 [bus debug] arbitration lost
2025-01-22 18:21:31.624 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:35.604 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:35.608 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:35.617 [bus debug] start request ff
2025-01-22 18:21:35.618 [bus debug] arbitration start with ff
2025-01-22 18:21:35.706 [bus debug] arbitration lost
2025-01-22 18:21:35.706 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:38.927 [main debug] performing regular tasks
2025-01-22 18:21:39.692 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:39.697 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:39.701 [bus debug] start request ff
2025-01-22 18:21:39.701 [bus debug] arbitration start with ff
2025-01-22 18:21:39.790 [bus debug] arbitration lost
2025-01-22 18:21:39.790 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:41.685 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:21:41.685 [bus debug] start request ff
2025-01-22 18:21:41.685 [bus debug] arbitration start with ff
2025-01-22 18:21:41.773 [bus debug] arbitration lost
2025-01-22 18:21:41.773 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:21:41.773 [bus info] scan 0b cmd: ff0b070400
2025-01-22 18:21:45.751 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:45.755 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:45.768 [bus debug] start request ff
2025-01-22 18:21:45.768 [bus debug] arbitration start with ff
2025-01-22 18:21:45.858 [bus debug] arbitration lost
2025-01-22 18:21:45.858 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:48.927 [main debug] performing regular tasks
2025-01-22 18:21:49.786 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:49.791 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:49.795 [bus debug] start request ff
2025-01-22 18:21:49.795 [bus debug] arbitration start with ff
2025-01-22 18:21:49.891 [bus debug] arbitration lost
2025-01-22 18:21:49.891 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:51.748 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:51.752 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:51.802 [bus debug] start request ff
2025-01-22 18:21:51.802 [bus debug] arbitration start with ff
2025-01-22 18:21:51.895 [bus debug] arbitration lost
2025-01-22 18:21:51.895 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:52.025 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:21:52.025 [bus debug] start request ff
2025-01-22 18:21:52.025 [bus debug] arbitration start with ff
2025-01-22 18:21:52.123 [bus debug] arbitration lost
2025-01-22 18:21:52.123 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:21:52.123 [bus info] scan 0c cmd: ff0c070400
2025-01-22 18:21:53.838 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:53.843 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:53.855 [bus debug] start request ff
2025-01-22 18:21:53.855 [bus debug] arbitration start with ff
2025-01-22 18:21:53.949 [bus debug] arbitration lost
2025-01-22 18:21:53.950 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:21:58.927 [main debug] performing regular tasks
2025-01-22 18:21:58.930 [network debug] SSL state 0=before SSL initialization: type 0x10=start, val 1=?
2025-01-22 18:21:58.930 [network debug] SSL state 0=before SSL initialization: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:58.932 [network debug] SSL BIO state 2 res -1
2025-01-22 18:21:58.936 [network debug] SSL BIO state 3 res 1
2025-01-22 18:21:58.937 [network debug] SSL BIO state 4 res 6
2025-01-22 18:21:58.937 [network debug] SSL BIO state 6 res 0
2025-01-22 18:21:58.937 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1002=exit,connect, val -1=?
2025-01-22 18:21:58.957 [network debug] SSL BIO state 5 res -1
2025-01-22 18:21:58.957 [network debug] SSL BIO state 5 res 1
2025-01-22 18:21:58.957 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1002=exit,connect, val -1=?
2025-01-22 18:21:58.978 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:58.978 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1002=exit,connect, val -1=?
2025-01-22 18:21:58.998 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1002=exit,connect, val -1=?
2025-01-22 18:21:59.018 [network debug] SSL state 12=SSLv3/TLS write client hello: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.021 [network debug] SSL state 3=SSLv3/TLS read server hello: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.022 [network debug] SSL state 38=TLSv1.3 read encrypted extensions: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.032 [network debug] SSL state 4=SSLv3/TLS read server certificate: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.037 [network debug] SSL state 39=TLSv1.3 read server certificate verify: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.038 [network debug] SSL state 11=SSLv3/TLS read finished: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.038 [network debug] SSL state 16=SSLv3/TLS write change cipher spec: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.039 [network debug] SSL state 18=SSLv3/TLS write finished: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.039 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x20=done, val 1=?
2025-01-22 18:21:59.039 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1002=exit,connect, val 1=?
2025-01-22 18:21:59.080 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.080 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.080 [network debug] SSL state 9=SSLv3/TLS read server session ticket: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.080 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1002=exit,connect, val 1=?
2025-01-22 18:21:59.100 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.101 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.101 [network debug] SSL state 9=SSLv3/TLS read server session ticket: type 0x1001=loop,connect, val 1=?
2025-01-22 18:21:59.101 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x1002=exit,connect, val 1=?
2025-01-22 18:21:59.121 [network debug] SSL state 1=SSL negotiation finished successfully: type 0x4008=write,alert, val 256=close notify
2025-01-22 18:21:59.122 [main notice] update check: OK
2025-01-22 18:21:59.876 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:21:59.883 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:21:59.886 [bus debug] start request ff
2025-01-22 18:21:59.887 [bus debug] arbitration start with ff
2025-01-22 18:21:59.975 [bus debug] arbitration lost
2025-01-22 18:21:59.975 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:03.927 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:03.931 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:03.943 [bus debug] start request ff
2025-01-22 18:22:03.943 [bus debug] arbitration start with ff
2025-01-22 18:22:04.032 [bus debug] arbitration lost
2025-01-22 18:22:04.032 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:09.122 [main debug] performing regular tasks
2025-01-22 18:22:09.998 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:10.002 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:10.006 [bus debug] start request ff
2025-01-22 18:22:10.006 [bus debug] arbitration start with ff
2025-01-22 18:22:10.097 [bus debug] arbitration lost
2025-01-22 18:22:10.097 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:10.098 [bus info] scan 0d cmd: ff0d070400
2025-01-22 18:22:11.971 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:11.971 [bus debug] start request ff
2025-01-22 18:22:11.971 [bus debug] arbitration start with ff
2025-01-22 18:22:12.064 [bus debug] arbitration lost
2025-01-22 18:22:12.064 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:12.234 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:12.234 [bus debug] start request ff
2025-01-22 18:22:12.234 [bus debug] arbitration start with ff
2025-01-22 18:22:12.319 [bus debug] arbitration lost
2025-01-22 18:22:12.319 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:14.035 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:14.040 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:14.052 [bus debug] start request ff
2025-01-22 18:22:14.052 [bus debug] arbitration start with ff
2025-01-22 18:22:14.145 [bus debug] arbitration lost
2025-01-22 18:22:14.145 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:19.122 [main debug] performing regular tasks
2025-01-22 18:22:19.123 [main notice] scan completed 2 time(s), check again
2025-01-22 18:22:20.063 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:20.068 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:20.071 [bus debug] start request ff
2025-01-22 18:22:20.071 [bus debug] arbitration start with ff
2025-01-22 18:22:20.160 [bus debug] arbitration lost
2025-01-22 18:22:20.160 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:20.161 [bus info] scan 0e cmd: ff0e070400
2025-01-22 18:22:22.071 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:22.073 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:22.124 [bus debug] start request ff
2025-01-22 18:22:22.124 [bus debug] arbitration start with ff
2025-01-22 18:22:22.217 [bus debug] arbitration lost
2025-01-22 18:22:22.217 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:22.399 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:22.399 [bus debug] start request ff
2025-01-22 18:22:22.399 [bus debug] arbitration start with ff
2025-01-22 18:22:22.491 [bus debug] arbitration lost
2025-01-22 18:22:22.491 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:24.108 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:24.112 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:24.125 [bus debug] start request ff
2025-01-22 18:22:24.125 [bus debug] arbitration start with ff
2025-01-22 18:22:24.216 [bus debug] arbitration lost
2025-01-22 18:22:24.216 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:28.157 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:28.162 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:28.166 [bus debug] start request ff
2025-01-22 18:22:28.166 [bus debug] arbitration start with ff
2025-01-22 18:22:28.255 [bus debug] arbitration lost
2025-01-22 18:22:28.255 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:28.255 [bus info] scan 12 cmd: ff12070400
2025-01-22 18:22:29.123 [main debug] performing regular tasks
2025-01-22 18:22:30.195 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:30.195 [bus debug] start request ff
2025-01-22 18:22:30.195 [bus debug] arbitration start with ff
2025-01-22 18:22:30.286 [bus debug] arbitration lost
2025-01-22 18:22:30.286 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:34.254 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:34.258 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:34.271 [bus debug] start request ff
2025-01-22 18:22:34.271 [bus debug] arbitration start with ff
2025-01-22 18:22:34.633 [bus debug] arbitration lost
2025-01-22 18:22:34.633 [bus debug] ERR: arbitration lost during skip, retry
2025-01-22 18:22:34.633 [bus debug] start request ff
2025-01-22 18:22:34.633 [bus debug] arbitration start with ff
2025-01-22 18:22:34.906 [bus debug] arbitration lost
2025-01-22 18:22:34.906 [bus debug] ERR: arbitration lost during skip, retry
2025-01-22 18:22:34.906 [bus debug] start request ff
2025-01-22 18:22:34.906 [bus debug] arbitration start with ff
2025-01-22 18:22:35.085 [bus debug] arbitration lost
2025-01-22 18:22:35.086 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:35.086 [bus info] scan 14 cmd: ff14070400
2025-01-22 18:22:38.298 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:38.303 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:38.307 [bus debug] start request ff
2025-01-22 18:22:38.307 [bus debug] arbitration start with ff
2025-01-22 18:22:38.396 [bus debug] arbitration lost
2025-01-22 18:22:38.396 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:39.123 [main debug] performing regular tasks
2025-01-22 18:22:40.286 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:40.286 [bus debug] start request ff
2025-01-22 18:22:40.286 [bus debug] arbitration start with ff
2025-01-22 18:22:40.375 [bus debug] arbitration lost
2025-01-22 18:22:40.375 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:42.823 [bus debug] start request ff
2025-01-22 18:22:42.823 [bus debug] arbitration start with ff
2025-01-22 18:22:43.098 [bus debug] arbitration lost
2025-01-22 18:22:43.098 [bus debug] ERR: arbitration lost during skip, retry
2025-01-22 18:22:43.098 [bus debug] start request ff
2025-01-22 18:22:43.098 [bus debug] arbitration start with ff
2025-01-22 18:22:43.268 [bus debug] arbitration lost
2025-01-22 18:22:43.268 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:43.268 [bus info] scan 15 cmd: ff15070400
2025-01-22 18:22:44.356 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:44.360 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:44.373 [bus debug] start request ff
2025-01-22 18:22:44.373 [bus debug] arbitration start with ff
2025-01-22 18:22:44.462 [bus debug] arbitration lost
2025-01-22 18:22:44.462 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:44.785 [bus debug] start request ff
2025-01-22 18:22:44.785 [bus debug] arbitration start with ff
2025-01-22 18:22:45.062 [bus debug] arbitration lost
2025-01-22 18:22:45.062 [bus debug] ERR: arbitration lost during skip, retry
2025-01-22 18:22:48.405 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:48.410 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:48.414 [bus debug] start request ff
2025-01-22 18:22:48.414 [bus debug] arbitration start with ff
2025-01-22 18:22:48.506 [bus debug] arbitration lost
2025-01-22 18:22:48.507 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:49.124 [main debug] performing regular tasks
2025-01-22 18:22:50.414 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:50.418 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:50.468 [bus debug] start request ff
2025-01-22 18:22:50.468 [bus debug] arbitration start with ff
2025-01-22 18:22:50.560 [bus debug] arbitration lost
2025-01-22 18:22:50.560 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:22:50.560 [bus info] scan 16 cmd: ff16070400
2025-01-22 18:22:50.690 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:22:50.690 [bus debug] start request ff
2025-01-22 18:22:50.690 [bus debug] arbitration start with ff
2025-01-22 18:22:50.781 [bus debug] arbitration lost
2025-01-22 18:22:50.781 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:54.482 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:54.485 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:54.498 [bus debug] start request ff
2025-01-22 18:22:54.498 [bus debug] arbitration start with ff
2025-01-22 18:22:54.587 [bus debug] arbitration lost
2025-01-22 18:22:54.587 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:58.524 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:22:58.541 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:22:58.544 [bus debug] start request ff
2025-01-22 18:22:58.544 [bus debug] arbitration start with ff
2025-01-22 18:22:58.621 [bus debug] arbitration lost
2025-01-22 18:22:58.622 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:22:59.124 [main debug] performing regular tasks
2025-01-22 18:23:02.562 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:02.566 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:02.579 [bus debug] start request ff
2025-01-22 18:23:02.579 [bus debug] arbitration start with ff
2025-01-22 18:23:02.669 [bus debug] arbitration lost
2025-01-22 18:23:02.669 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:23:02.669 [bus info] scan 18 cmd: ff18070400
2025-01-22 18:23:05.253 [bus debug] ERR: read timeout during receive command, switching to skip
2025-01-22 18:23:05.593 [bus debug] start request ff
2025-01-22 18:23:05.593 [bus debug] arbitration start with ff
2025-01-22 18:23:05.682 [bus debug] arbitration lost
2025-01-22 18:23:05.682 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:08.580 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:08.584 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:08.588 [bus debug] start request ff
2025-01-22 18:23:08.588 [bus debug] arbitration start with ff
2025-01-22 18:23:08.684 [bus debug] arbitration lost
2025-01-22 18:23:08.684 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:09.124 [main debug] performing regular tasks
2025-01-22 18:23:10.550 [bus debug] ERR: read timeout during receive command, switching to skip
2025-01-22 18:23:10.901 [bus debug] start request ff
2025-01-22 18:23:10.901 [bus debug] arbitration start with ff
2025-01-22 18:23:10.968 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:23:11.014 [bus debug] arbitration lost
2025-01-22 18:23:11.014 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:11.219 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:23:11.219 [bus debug] start request ff
2025-01-22 18:23:11.219 [bus debug] arbitration start with ff
2025-01-22 18:23:11.307 [bus debug] arbitration lost
2025-01-22 18:23:11.307 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:23:11.307 [bus info] scan 19 cmd: ff19070400
2025-01-22 18:23:12.618 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:12.624 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:12.634 [bus debug] start request ff
2025-01-22 18:23:12.635 [bus debug] arbitration start with ff
2025-01-22 18:23:12.726 [bus debug] arbitration lost
2025-01-22 18:23:12.726 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:15.895 [bus debug] ERR: read timeout during receive command, switching to skip
2025-01-22 18:23:16.243 [bus debug] start request ff
2025-01-22 18:23:16.243 [bus debug] arbitration start with ff
2025-01-22 18:23:16.331 [bus debug] arbitration lost
2025-01-22 18:23:16.331 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:18.735 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:18.740 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:18.744 [bus debug] start request ff
2025-01-22 18:23:18.745 [bus debug] arbitration start with ff
2025-01-22 18:23:18.833 [bus debug] arbitration lost
2025-01-22 18:23:18.833 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:19.125 [main debug] performing regular tasks
2025-01-22 18:23:20.652 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:20.654 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:20.705 [bus debug] start request ff
2025-01-22 18:23:20.705 [bus debug] arbitration start with ff
2025-01-22 18:23:20.795 [bus debug] arbitration lost
2025-01-22 18:23:20.795 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:23:20.795 [bus info] scan 1a cmd: ff1a070400
2025-01-22 18:23:20.972 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:23:20.973 [bus debug] start request ff
2025-01-22 18:23:20.973 [bus debug] arbitration start with ff
2025-01-22 18:23:21.024 [bus debug] arbitration lost
2025-01-22 18:23:21.024 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:21.213 [bus debug] ERR: read timeout during receive command, switching to skip
2025-01-22 18:23:21.561 [bus debug] start request ff
2025-01-22 18:23:21.562 [bus debug] arbitration start with ff
2025-01-22 18:23:21.652 [bus debug] arbitration lost
2025-01-22 18:23:21.652 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:22.774 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:22.778 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:22.787 [bus debug] start request ff
2025-01-22 18:23:22.787 [bus debug] arbitration start with ff
2025-01-22 18:23:22.876 [bus debug] arbitration lost
2025-01-22 18:23:22.876 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:28.795 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2025-01-22 18:23:28.800 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2025-01-22 18:23:28.805 [bus debug] start request ff
2025-01-22 18:23:28.805 [bus debug] arbitration start with ff
2025-01-22 18:23:28.896 [bus debug] arbitration lost
2025-01-22 18:23:28.896 [bus debug] notify request: ERR: arbitration lost
2025-01-22 18:23:28.896 [bus info] scan 1b cmd: ff1b070400
2025-01-22 18:23:29.125 [main debug] performing regular tasks
2025-01-22 18:23:29.125 [main notice] scan completed 3 time(s), check again
2025-01-22 18:23:30.791 [bus debug] ERR: SYN received during receive command, switching to ready
2025-01-22 18:23:30.791 [bus debug] start request ff
2025-01-22 18:23:30.791 [bus debug] arbitration start with ff
2025-01-22 18:23:30.882 [bus debug] arbitration lost
2025-01-22 18:23:30.882 [bus debug] ERR: arbitration lost during ready, retry
2025-01-22 18:23:30.914 [network debug] [00003] wait for result
2025-01-22 18:23:30.914 [main debug] >>> info
2025-01-22 18:23:30.914 [main debug] <<< version: ebusd 24.1.24.1
update check: OK
device: 192.168.1.30:9999, TCP
access: *
signal: acquired
 ...

Danke für Deine Hilfe

EEBUS ist nicht Ebus.
Sorry aber damit wird das hier nix.
Schau mal hier:

Michael

Hallo Nall-chan,

Vielen Dank für die Info, dann kann ich jetzt aufhören zu suchen, das ist wohl genau das was ich nicht hören wollte.

Danke trotzdem!
Wolfgang

Da scheint hardwaremäßig etwas nicht zu stimmen.

Welchen Adapter setzt du denn ein. Ist er in der Liste der unterstützten Geräte?

Ein Beitrag wurde in ein existierendes Thema verschoben: Symcon + EEBUS

Das könnte es sein…

Meine Hardware:
Ich habe einen eBUS Adapter Shield C6 per WLAN und Ebus an der Heizung angeschlossen.

Der C6 ist die Weiterentwicklung vom V5. Ich kann ja mal fragen, wann er aufgenommen wird.
Danke für Deine Hilfe.

Ich denke, er wird schon unterstützt. Darauf wird ja hier Bezug genommen:

Hast du auch alle Hinweise dort befolgt?

Aber stelle dein Problem mal direkt dort vor.

Ich habe bei git.hub einen direkten Support von John30 erhalten und er konnte mir super schnell weiterhelfen.

Zunächst deutlich vorweg: der Shield C6 wird hardwaretechnisch unterstützt!!!

Bei mir war der Device nicht korrekt eingestellt: Die Bezeichnung der Schnittstelle muss in meinem Fall „–device=ens:192.168.1.30:9999“ heißen. Das steht auch so auf der Web-Oberfläche des Adapters. Das hatte ich anfangs auch so in die Config geschrieben, aber dann aufgrund von Hilflosigkeit und nichtwissendem Probieren geändert. Da ich aber vom Adapter ja Rückmeldungen bekam, ging ich davon aus, dass er auch mit der IP-Config so funktioniert. Das ist aber eine Fehlinterpretation meinerseits gewesen. Also in meinem Fall muss die Config so sein, wie oben beschrieben. Dann sieht das Ergebnis so aus:

Jetzt schaue ich weiter…
Vielen Dank soweit …

Weiter gehts…
Aktueller Status wie oben ich kann zudem die http-Seite aufrufen und sehe Daten. Teilauszug:
image

Ich kann einzelne Befehle an den ebusd senden und bekomme Antworten.

Wenn ich jetzt den mqtt-Config-Part ergänze bekomme ich folgende Fehlermeldung auf journalctl -xe:


Das System sagt: invalid argument --mqtthost=192.168.1.50

Die Ip ist aber das Symcon-System. Ein Ping darauf funktioniert ebenfalls. Meine Config in ebusd sieht nun so aus:


EBUSD_OPTS="--scanconfig=full --configpath=/home/pi/ebusd-config/ebusd-configuration/ebusd-2.1.x/de --accesslevel=* --latency=10 --device=ens:192.168.1.30:9999 --logfile=/var/log/ebusd.log --loglevel=error --address=ff --receivetimeout=100000 --httpport=8082 --pollinterval=30 --mqtthost=192.168.1.50 --mqttport=1024 --mqttuser=XXXX --mqttpass=XXXX --mqttjson"

Auf der Gegenseite in Symcon habe ich alles angelegt:

Etwas irritiert bin ich über den Eintrag 0.0.0.0:1024. Ist das korrekt? Die IP kann ich ja selbst nicht einstellen.

Irgendwo hängt die Verbindung… Danke für Eure Hinweise im Voraus.

Ergänzung: Das Auslesen/Anlegen der Variablen über die http-Ebene funktioniert auch. Nur kommen keine Werte, vermutlich wegen der fehlenden Kommunikation über die mqtt-Ebene.

Kann leider erst Montag weiterhelfen. Aber prüfe nochmal, ob die doppelten Bindestriche richtig sind.
Ich habe in Erinnerung, dass es mal einer, mal zwei sein müssen.

Danke. Habe ich gemacht. Das mit den doppelten Strichen scheint richtig. In einer früheren Version gab es mal die Definition des Devices mit -d=ENS:192… usw. Jetzt ist es --device=…
Das scheint aber auch nicht am Eintrag --mqtthost=… zu liegen. Ich bekomme das auch mit dem --pollintervall hin.
Merkwürdig!

Hast du auch die ebusd Variante mit mqtt Support installiert?

Ich denke schon… Ich habe das Gesamt-Paket wie folgt installiert …

https://github.com/john30/ebusd-debian/blob/master/README.md

Dann noch mittels…
sudo apt-get update
sudo apt-get install libmosquitto1

Eine aktuelle Prüfung ergibt:

Ich installiere die Pakete aber nochmal drüber…

So… das ging schnell… es läuft! Zumindest startet ebusd nun ohne Fehlermeldung. Es scheint als hätte die mqtt-variante nicht ordnungsgemäß installiert oder ich habe etwas hinterher geschoben, was hier dazu geführt hat.

Vielen Dank !!!

Wenn ich jetzt allerdings in Symcon auf das mqtt-device gehe und die Daten auslesen lassen möchte…

Dann bekomme ich folgende Fehlermeldung:

Was könnte das auf sich haben?

Nimm mal bitte die Beta-Version des Moduls, die unterstützt IPS 7.x

Der Wechsel auf die Beta war ein guter Hinweis. Danke.
Ich konnte die Werte lesen.


Ich bekomme auch plausible Werte. Nur wenn ich dann in die Baumstruktur schaue, werden die eigentlichen Werte nicht übertragen:

Muss ich hier noch einen Trigger oder ein Ereignis setzen?
Meine Verbindungseinstellungen lauten:

Über den Schaltkreis „Bai“ bekomme ich mittlerweile Werte.

Über den Schaltkreis „430“ leider nicht. Wo ist da eigentlich der Unterschied?

Kann ich die beiden mqtt-devices auf ein Server-Socket adressieren? Oder gibt das Probleme?

Das Modul kennt da keinen unterschied.

Meiner Meinung nach musst du das sogar, da du in der Config-Datei ja nur einen Server/Port adressieren kannst.

Vielleicht liegt da schon dein Problem. Die 430er Instanz ist vermutlich mit dem falschen Port verbunden.