eBUS Adapter 3.0

[Pnemenz]

welche Pins hast Du denn gebrückt??

Wie in der Anleitung geschrieben J11 3 und 4
Ich befürchte ich habe den USB Chip ruiniert. Als ich den ebus angeschlossen habe, war der Adapter unter Strohm  . Es roch auch komisch
Auf alle Fälle: Am Jumper J12 ist 1-2 verbunden.

[skiworker]

Guten Abend,

ich hoffe Ihr hattet alle einen fleißigen Weihnachtsmann und ein paar besinnliche Feiertage.
Nun zum Thema...
Ich habe vor Kurzem den Adapter 3.1 RPI erhalten. Vielen Dank dafür und für Eure Arbeit.
Ich habe heute versucht, den Adapter in Betrieb zu nehmen. Dazu habe ich Ebusd auf dem RPI installiert und die Konfigueration geladen. Zudem habe ich die Schritte für den RPI abgearbeitet (Serial0 an ttyAMA0 usw.).
Allerdings sehe ich im Log von Ebusd folgendes:

Code Auswählen Erweitern

2022-12-30 20:31:58.809 [main notice] ebusd 22.4.v22.4 started with full scan on device /dev/ttyAMA0
2022-12-30 20:31:58.825 [bus notice] bus started with own address 31/36
2022-12-30 20:31:58.828 [mqtt notice] connection established
2022-12-30 20:34:07.347 [main notice] update check: OK


und bleibt bei "update check: OK" stehen.

Was ich allerdings nicht durchgeführt habe, ist die Einstellung der Variante (USB/RPI).
Nun wollte ich dies nachholen und habe es direkt über den RPI versucht. Der Befehl

Code Auswählen Erweitern

ebuspicloader --variant=U ttyAMA0

brachte mich zu der Erkenntnis, dass die Option "variant" nicht verfügbar ist. Dies belegt auch "ebuspicloader --help"

Code Auswählen Erweitern

Dennis@RPI-Ebusd:/var/log $ ebuspicloader --help
Usage: ebuspicloader [OPTION...] PORT
A tool for loading firmware to the eBUS adapter PIC.

  -a, --arbdel=US            set arbitration delay to US microseconds (0-620 in
                             steps of 10, default 200, since firmware
                             20211128)
  -d, --dhcp                 set dynamic IP address via DHCP
  -f, --flash=FILE           flash the FILE to the device
  -i, --ip=IP                set fix IP address (e.g. 192.168.0.10)
  -m, --mask=MASK            set fix IP mask (e.g. 24)
  -M, --macip                set the MAC address suffix from the IP address
  -r, --reset                reset the device at the end on success
  -s, --slow                 use low speed for transfer
  -v, --verbose              enable verbose output
  -?, --help                 Give this help list
      --usage                Give a short usage message
  -V, --version              Print program version

PORT is either the serial port to use (e.g./dev/ttyUSB0) that also supports a
trailing wildcard '*' for testing multiple ports, or a network port as
"ip:port" for use with e.g. socat.


Nun wollte ich es dann über Windows machen. Also habe ich die zip-Datei heruntergeladen und entpackt. Dann mit cmd.exe in den Ordner gewechselt und den Befehl

Code Auswählen Erweitern

ebuspicloader --variant=U COM1

eingegeben. Als Rückgabe bekomme ich, dass COM1 nicht geöffnet werden kann (Bootloader ist aktiviert).
Dann habe ich Cygwin installiert und den Inhalt des Ordners von der entpackten Zip-Datei in den Ordner "usr" kopiert.
In Cygwin bekomme ich die Meldung, dass der Befehl ebuspicloader nicht gefunden werden kann.

Code Auswählen Erweitern

techn@DESKTOP-215732Q /usr/ebuspicloader
$ ebuspicloader --variant=U ttyS0
-bash: ebuspicloader: command not found


Nun meine Frageen:
1. Ist die Variante bei Auslieferung schon eingestellt?
2. Kann ich den ebuspicloader auf den RPI irgendwie aktualisieren, damit die Option "variant" verfügbar ist?
3. Könnt Ihr mir vielleicht sagen, warum das in Windows (cmd.exe) und Cygwin (auf dem PC) nicht funktioniert?

Ich hoffe Ihr könnt mir hier weiterhelfen.
Ich wünsche Euch schon mal ein guten Rutsch in das Jahr 2023

Grüße
Dennis

[john30]

Allerdings sehe ich im Log von Ebusd folgendes:

Code Auswählen Erweitern

2022-12-30 20:31:58.809 [main notice] ebusd 22.4.v22.4 started with full scan on device /dev/ttyAMA0


hier fehlt dir sicher noch der Präfix "ens:" zum device string, also insgesamt "-d ens:/dev/ttyAMA0" wie dokumentiert.

Nun wollte ich es dann über Windows machen. Also habe ich die zip-Datei heruntergeladen und entpackt. Dann mit cmd.exe in den Ordner gewechselt und den Befehl

Code Auswählen Erweitern

ebuspicloader --variant=U COM1

eingegeben. Als Rückgabe bekomme ich, dass COM1 nicht geöffnet werden kann (Bootloader ist aktiviert).

naja, das ist ja cygwin basiert, d.h. die Windows COM Ports werden auf /dev/ttySX gemappt, wobei X immer 1 kleiner ist als die COM Portnummer, also bspw. /dev/ttyS3 für COM4.

1. Ist die Variante bei Auslieferung schon eingestellt?

ja

2. Kann ich den ebuspicloader auf den RPI irgendwie aktualisieren, damit die Option "variant" verfügbar ist?

ja: repo clonen und compilieren

3. Könnt Ihr mir vielleicht sagen, warum das in Windows (cmd.exe) und Cygwin (auf dem PC) nicht funktioniert?

weil das ein Binary basierend auf den aktuellen Source im repo ist.

Ich wünsche Euch schon mal ein guten Rutsch in das Jahr 2023

merci, ebenso!

[skiworker]

Hallo John30,

Asche auf mein Haupt. Ja der Zusatz "ens" hatte gefehlt. Danke für den Hinweis.
Allerdings erkannt er zwar die Beiden Regler scan.08 (Vaillant; BAI00;0205;9602) und scan.15 (Vaillant;7000;0614;6903) aber ich bekomme keine Werte über Mqtt.

Meine Config sieht so aus:

Code Auswählen Erweitern

EBUSD_OPTS="--configpath=/etc/ebusd/ -d ens:/dev/ttyAMA0 -p 8888 --scanconfig=full --enablehex --latency=50 --receivetimeout=10000 -l /var/log/ebusd.log --httpport=8889 --htmlpath=/var/ebusd/html --mqtttopic=ebusd/%circuit/%name --mqtthost=192.168.168.26 --mqttport=1883 --mqttuser=openhabian --mqttpass=XXXXXXXXXXXX --accesslevel=*"

Der ebusd log sieht so aus:

Code Auswählen Erweitern

2022-12-31 10:04:18.014 [main notice] ebusd 22.4.v22.4 started with full scan on enhanced device /dev/ttyAMA0
2022-12-31 10:04:18.025 [bus notice] device status: resetting
2022-12-31 10:04:18.026 [bus notice] bus started with own address 31/36
2022-12-31 10:04:18.030 [mqtt notice] connection established
2022-12-31 10:04:18.041 [bus error] device status: unexpected available enhanced following byte 1
2022-12-31 10:04:18.041 [bus notice] signal acquired
2022-12-31 10:04:18.041 [bus error] device status: unexpected available enhanced byte 2
2022-12-31 10:04:18.318 [bus notice] device status: reset, supports info
2022-12-31 10:04:26.460 [bus notice] new master 10, master count 2
2022-12-31 10:04:26.519 [bus notice] new master 03, master count 3
2022-12-31 10:04:26.519 [update notice] received unknown MS cmd: 1008b5110101 / 094d39200e3f680100ff
2022-12-31 10:04:26.787 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:04:27.061 [update notice] received unknown MS cmd: 1008b5040100 / 0a0313071031120622200e
2022-12-31 10:04:27.317 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:04:27.554 [update notice] received unknown BC cmd: 10feb516080011071031120622
2022-12-31 10:04:27.818 [update notice] received unknown MS cmd: 1008b5110100 / 0870020f20040f0081
2022-12-31 10:04:28.030 [main notice] starting initial full scan
2022-12-31 10:04:28.035 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:04:30.269 [bus notice] scan 08: ;Vaillant;BAI00;0205;9602
2022-12-31 10:04:30.465 [update notice] store 08 ident: done
2022-12-31 10:04:30.465 [update notice] sent scan-read scan.08  QQ=31: Vaillant;BAI00;0205;9602
2022-12-31 10:04:30.465 [bus notice] scan 08: ;Vaillant;BAI00;0205;9602
2022-12-31 10:07:18.113 [main error] unable to load scan config 08: list files in vaillant ERR: element not found
2022-12-31 10:07:18.113 [main error] scan config 08: ERR: element not found
2022-12-31 10:07:18.195 [bus error] signal lost
2022-12-31 10:07:18.286 [bus notice] signal acquired
2022-12-31 10:07:18.290 [bus notice] arbitration won in invalid state ready
2022-12-31 10:07:20.281 [bus notice] scan 15: ;Vaillant;70000;0614;6903
2022-12-31 10:07:20.281 [update notice] store 15 ident: done
2022-12-31 10:07:20.281 [update notice] sent scan-read scan.15  QQ=31: Vaillant;70000;0614;6903
2022-12-31 10:07:20.281 [bus notice] scan 15: ;Vaillant;70000;0614;6903
2022-12-31 10:07:20.281 [main error] unable to load scan config 15: list files in vaillant ERR: element not found
2022-12-31 10:07:20.281 [main error] scan config 15: ERR: element not found
2022-12-31 10:07:22.151 [update notice] received unknown MS cmd: 1008b5110101 / 095039200e3f680100ff
2022-12-31 10:07:22.419 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:07:32.198 [update notice] received unknown MS cmd: 1008b5110101 / 09513a200e3f680100ff
2022-12-31 10:07:32.466 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:07:42.241 [update notice] received unknown MS cmd: 1008b5110101 / 094a39200e3f680000ff
2022-12-31 10:07:42.509 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:07:42.762 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:07:52.285 [update notice] received unknown MS cmd: 1008b5110101 / 093d37200e3f680000ff
2022-12-31 10:07:52.552 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:02.328 [update notice] received unknown MS cmd: 1008b5110101 / 093935200e3f680000ff
2022-12-31 10:08:02.596 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:12.332 [update notice] received unknown MS cmd: 1008b5110101 / 093635200e3f680000ff
2022-12-31 10:08:12.599 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:12.873 [update notice] received unknown MS cmd: 1008b5040100 / 0a0313081031120622200e
2022-12-31 10:08:13.129 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:08:13.365 [update notice] received unknown BC cmd: 10feb516080012081031120622
2022-12-31 10:08:13.627 [update notice] received unknown MS cmd: 1008b5110100 / 08b0010f0007080083
2022-12-31 10:08:13.842 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:08:22.367 [update notice] received unknown MS cmd: 1008b5110101 / 093534200e3f680000ff
2022-12-31 10:08:22.634 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:32.419 [update notice] received unknown MS cmd: 1008b5110101 / 093433200e3f680000ff
2022-12-31 10:08:32.686 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:42.462 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:08:42.730 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:08:42.987 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:08:52.511 [update notice] received unknown MS cmd: 1008b5110101 / 093334200e3f680000ff
2022-12-31 10:08:52.779 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:02.519 [update notice] received unknown MS cmd: 1008b5110101 / 093334200e3f680000ff
2022-12-31 10:09:02.786 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:12.571 [update notice] received unknown MS cmd: 1008b5110101 / 093435200e3f680000ff
2022-12-31 10:09:12.838 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:13.108 [update notice] received unknown MS cmd: 1008b5040100 / 0a0313091031120622200e
2022-12-31 10:09:13.364 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:09:13.599 [update notice] received unknown BC cmd: 10feb516080012091031120622
2022-12-31 10:09:13.862 [update notice] received unknown MS cmd: 1008b5110100 / 08a0010f0007080083
2022-12-31 10:09:14.077 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:09:22.477 [main notice] update check: OK
2022-12-31 10:09:22.603 [update notice] received unknown MS cmd: 1008b5110101 / 093435200e3f680000ff
2022-12-31 10:09:22.870 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:32.651 [update notice] received unknown MS cmd: 1008b5110101 / 093435200e3f680000ff
2022-12-31 10:09:32.918 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:42.699 [update notice] received unknown MS cmd: 1008b5110101 / 093535200e3f680000ff
2022-12-31 10:09:42.965 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:09:43.219 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:09:52.731 [update notice] received unknown MS cmd: 1008b5110101 / 093535200e3f680000ff
2022-12-31 10:09:52.998 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:02.746 [update notice] received unknown MS cmd: 1008b5110101 / 093535200e3f680000ff
2022-12-31 10:10:03.013 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:10.371 [update notice] received scan-read scan.15  QQ=03: Vaillant;70000;0614;6903
2022-12-31 10:10:12.801 [update notice] received unknown MS cmd: 1008b5110101 / 093434200e3f680000ff
2022-12-31 10:10:13.069 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:13.338 [update notice] received unknown MS cmd: 1008b5040100 / 0a0315101031120622200e
2022-12-31 10:10:13.594 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:10:13.831 [update notice] received unknown BC cmd: 10feb516080012101031120622
2022-12-31 10:10:14.096 [update notice] received unknown MS cmd: 1008b5110100 / 08a5010f0007080083
2022-12-31 10:10:14.311 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:10:22.841 [update notice] received unknown MS cmd: 1008b5110101 / 093434200e3f680000ff
2022-12-31 10:10:23.112 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:32.853 [update notice] received unknown MS cmd: 1008b5110101 / 093334200e3f680000ff
2022-12-31 10:10:33.120 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:42.901 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:10:43.168 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:10:43.422 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:10:52.946 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:10:53.212 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:02.994 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:11:03.261 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:12.999 [update notice] received unknown MS cmd: 1008b5110101 / 093233200e3f680000ff
2022-12-31 10:11:13.266 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:13.540 [update notice] received unknown MS cmd: 1008b5040100 / 0a0315111031120622200e
2022-12-31 10:11:13.796 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:11:14.033 [update notice] received unknown BC cmd: 10feb516080014111031120622
2022-12-31 10:11:14.297 [update notice] received unknown MS cmd: 1008b5110100 / 0896010f0007080083
2022-12-31 10:11:14.512 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:11:14.758 [update notice] received unknown MS cmd: 1008b5100305ff01 / 0101
2022-12-31 10:11:14.990 [update notice] received unknown MS cmd: 1008b512020064 / 00
2022-12-31 10:11:15.230 [update notice] received unknown MS cmd: 1008b5120204ff / 0101
2022-12-31 10:11:15.468 [update notice] received unknown MS cmd: 1008b513020508 / 00
2022-12-31 10:11:15.680 [update notice] received unknown BC cmd: 10feb510020601
2022-12-31 10:11:23.039 [update notice] received unknown MS cmd: 1008b5110101 / 093233200e3f680000ff
2022-12-31 10:11:23.306 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:33.087 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:11:33.355 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:43.131 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:11:43.398 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:11:43.656 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:11:53.175 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:11:53.443 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:03.183 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:12:03.450 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:13.226 [update notice] received unknown MS cmd: 1008b5110101 / 093333200e3f680000ff
2022-12-31 10:12:13.494 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:13.768 [update notice] received unknown MS cmd: 1008b5040100 / 0a0315121031120622200e
2022-12-31 10:12:14.023 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:12:14.260 [update notice] received unknown BC cmd: 10feb516080014121031120622
2022-12-31 10:12:14.525 [update notice] received unknown MS cmd: 1008b5110100 / 0898010f0007080083
2022-12-31 10:12:14.740 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:12:23.267 [update notice] received unknown MS cmd: 1008b5110101 / 093233200e3f680000ff
2022-12-31 10:12:23.534 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:33.322 [update notice] received unknown MS cmd: 1008b5110101 / 093232200e3f680000ff
2022-12-31 10:12:33.590 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:43.323 [update notice] received unknown MS cmd: 1008b5110101 / 093232200e3f680000ff
2022-12-31 10:12:43.590 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:12:43.848 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:12:53.367 [update notice] received unknown MS cmd: 1008b5110101 / 093131200e3f680000ff
2022-12-31 10:12:53.635 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:03.415 [update notice] received unknown MS cmd: 1008b5110101 / 093832200e3f680100ff
2022-12-31 10:13:03.682 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:13.475 [update notice] received unknown MS cmd: 1008b5110101 / 094936200e3f680100ff
2022-12-31 10:13:13.742 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:14.012 [update notice] received unknown MS cmd: 1008b5040100 / 0a0315131031120622200e
2022-12-31 10:13:14.268 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:13:14.510 [update notice] received unknown BC cmd: 10feb516080014131031120622
2022-12-31 10:13:14.774 [update notice] received unknown MS cmd: 1008b5110100 / 0852020f20040f0081
2022-12-31 10:13:14.989 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:13:23.475 [update notice] received unknown MS cmd: 1008b5110101 / 094b37500e3f680100ff
2022-12-31 10:13:23.742 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:33.535 [update notice] received unknown MS cmd: 1008b5110101 / 094f38200e3f680100ff
2022-12-31 10:13:33.806 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:43.542 [update notice] received unknown MS cmd: 1008b5110101 / 095039500e3f680100ff
2022-12-31 10:13:43.813 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:13:44.067 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:13:53.585 [update notice] received unknown MS cmd: 1008b5110101 / 094c39200e3f680000ff
2022-12-31 10:13:53.852 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:14:03.628 [update notice] received unknown MS cmd: 1008b5110101 / 093e37200e3f680000ff
2022-12-31 10:14:03.896 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:14:13.676 [update notice] received unknown MS cmd: 1008b5110101 / 093935200e3f680000ff
2022-12-31 10:14:13.944 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:14:14.217 [update notice] received unknown MS cmd: 1008b5040100 / 0a0315141031120622200e
2022-12-31 10:14:14.473 [update notice] received unknown MS cmd: 1008b5110102 / 06033c8246826e
2022-12-31 10:14:14.710 [update notice] received unknown BC cmd: 10feb516080015141031120622
2022-12-31 10:14:14.975 [update notice] received unknown MS cmd: 1008b5110100 / 08cb010f0007080083
2022-12-31 10:14:15.192 [update notice] received unknown BC cmd: 10feb5160301200e
2022-12-31 10:14:23.717 [update notice] received unknown MS cmd: 1008b5110101 / 093634200e3f680000ff
2022-12-31 10:14:23.987 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101
2022-12-31 10:14:33.727 [update notice] received unknown MS cmd: 1008b5110101 / 093534500e3f680000ff
2022-12-31 10:14:33.994 [update notice] received unknown MS cmd: 1008b5100900003dffffff000000 / 0101


Im Mqtt-Explorer sieht es so aus:

Code Auswählen Erweitern

ebusd
global
version = ebusd 22.4.v22.4
running = true
scan = finished
signal = true
updatecheck = OK
uptime = 1923
scan.08
= Vaillant;BAI00;0205;9602
scan.15
= Vaillant;70000;0614;6903

Hast Du eine Idee, waron das liegen kann?

Gruß
Dennis

[john30]

Code Auswählen Erweitern

EBUSD_OPTS="--configpath=/etc/ebusd/ -d ens:/dev/ttyAMA0 -p 8888 --scanconfig=full --enablehex --latency=50 --receivetimeout=10000 -l /var/log/ebusd.log --httpport=8889 --htmlpath=/var/ebusd/html --mqtttopic=ebusd/%circuit/%name --mqtthost=192.168.168.26 --mqttport=1883 --mqttuser=openhabian --mqttpass=XXXXXXXXXXXX --accesslevel=*"

Code Auswählen Erweitern


...
2022-12-31 10:07:18.113 [main error] unable to load scan config 08: list files in vaillant ERR: element not found


Hast Du eine Idee, waron das liegen kann?

Du hast die configs auf /etc/ebusd/ gesetzt und dort scheinen keine Dateien drin zu sein

[skiworker]

Hallo John30,

habe den Fehler gefunden. Der angegebene Configparth war natürlich falsch. Habe diesen in "https://cfg.ebusd.eu" geändert.
Jetzt bekomme ich zumindest ein paar Werte.

Grüße
Dennis

[Citrus91]

Hallo John,

ich habe den EBUSD-Adapater erhalten. Vielen Dank, auch für die geleistete Arbeit bzgl. Software und Dokumentation. Ich habe mich bis jetzt gut zurecht gefunden. Allerdings bin ich jetzt auf eine Problem gestoßen. Folgendes habe ich getan:

1. Ich habe mich (vorläufig) jetzt doch für einen Anschluss via USB an den Raspberry entschieden. Hierfür habe ich den Ethernet-Adapter abgesteckt und im Bootloader variant=U eingestellt.

2. Im Raspberry habe das USB-Gerät gesucht, gefunden und in "/dev/ebusdUSB" umbenannt.

3. Ebenfalls habe ich "ebusd_debian" installiert (Repo eingefügt & apt-get install).

3. Bei der Konfiguration habe ich die "Default"-Zeile auskommentiert und folgende Zeile hinzugefügt:

Code Auswählen Erweitern

EBUSD_OPTS="--scanconfig -d ens:/dev/ebusdUSB"

4. Dann den Daemon gestartet und ins Logfile geschaut.

Code Auswählen Erweitern


2023-01-07 14:13:06.589 [main notice] ebusd 23.1.23.1 started with auto scan on enhanced device /dev/ebusdUSB
2023-01-07 14:13:07.299 [bus error] unable to open /dev/ebusdUSB: ERR: element not found
2023-01-07 14:13:07.300 [bus notice] bus started with own address 31/36
2023-01-07 14:13:07.300 [bus notice] device invalid
2023-01-07 14:13:12.300 [bus error] unable to open /dev/ebusdUSB: ERR: element not found
2023-01-07 14:13:12.300 [bus notice] device invalid
2023-01-07 14:13:17.300 [bus error] unable to open /dev/ebusdUSB: ERR: element not found
2023-01-07 14:13:17.300 [bus notice] device invalid
2023-01-07 14:13:22.301 [bus error] unable to open /dev/ebusdUSB: ERR: element not found
2023-01-07 14:13:22.301 [bus notice] device invalid


Hast du eine Idee was schief läuft?
Das EBUS-Kabel habe ich noch nicht angeschlossen.

Gruß Eric

[john30]

Hast du eine Idee was schief läuft?
Das EBUS-Kabel habe ich noch nicht angeschlossen.

vermutlich ein Rechte-Problem. Schau mal was

Code Auswählen Erweitern

ls -la /dev/ebusdUSB ausgibt. Lösen lässt es sich höchstwahrscheinlich mittels

Code Auswählen Erweitern

chmod a+rw /dev/ebusdUSB. Das wäre aber nach Reboot wieder weg und insofern müsstest Du mal schauen, das zu persistieren

[Citrus91]

vermutlich ein Rechte-Problem. Schau mal was

Code Auswählen Erweitern

ls -la /dev/ebusdUSB ausgibt.

Sieht aber eigentlich alles okay aus:

Code Auswählen Erweitern


pi@raspberrypi:~ $ ls -la /dev/ebusdUSB
lrwxrwxrwx 1 root root 15 Jan  7 14:45 /dev/ebusdUSB -> bus/usb/001/003


Ich habe in der Konfigdatei noch von "ens" auf "enh" umgestellt, da ich ja 'variant=U' habe, oder? Brachte aber keinen Erfolg.

[john30]

Code Auswählen Erweitern


pi@raspberrypi:~ $ ls -la /dev/ebusdUSB
lrwxrwxrwx 1 root root 15 Jan  7 14:45 /dev/ebusdUSB -> bus/usb/001/003


nö, das ist nicht richtig. es muss auf ein serial device verlinken, also sowas wie /dev/ttyS0 oder /dev/ttyUSB0 oder /dev/ttyAMA0

[Citrus91]

Wenn ich es nicht linke, dann funktioniert es. Das ist schon mal gut.

Aber was mache ich falsch?

Code Auswählen Erweitern

pi@raspberrypi:~ $ udevadm info -a -p  $(udevadm info -q path -n /dev/ttyUSB0)

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/ttyUSB0/tty/ttyUSB0':
    KERNEL=="ttyUSB0"
    SUBSYSTEM=="tty"
    DRIVER==""
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/ttyUSB0':
    KERNELS=="ttyUSB0"
    SUBSYSTEMS=="usb-serial"
    DRIVERS=="cp210x"
    ATTRS{port_number}=="0"
    ATTRS{power/control}=="auto"
    ATTRS{power/runtime_active_time}=="0"
    ATTRS{power/runtime_status}=="unsupported"
    ATTRS{power/runtime_suspended_time}=="0"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0':
    KERNELS=="1-1.3:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="cp210x"
    ATTRS{authorized}=="1"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceClass}=="ff"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceProtocol}=="00"
    ATTRS{bInterfaceSubClass}=="00"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3':
    KERNELS=="1-1.3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0100"
    ATTRS{bmAttributes}=="80"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="3"
    ATTRS{devpath}=="1.3"
    ATTRS{devspec}=="(null)"
   ATTRS{idProduct}=="ea60"        <---------
    ATTRS{idVendor}=="10c4"        <---------
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="Silicon Labs"
    ATTRS{maxchild}=="0"
    ATTRS{power/active_duration}=="138640"
    ATTRS{power/autosuspend}=="2"
    ATTRS{power/autosuspend_delay_ms}=="2000"
    ATTRS{power/connected_duration}=="138640"
    ATTRS{power/control}=="on"
    ATTRS{power/level}=="on"
    ATTRS{power/persist}=="1"
    ATTRS{power/runtime_active_time}=="138413"
    ATTRS{power/runtime_status}=="active"
    ATTRS{power/runtime_suspended_time}=="0"
    ATTRS{product}=="CP2102N USB to UART Bridge Controller"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{rx_lanes}=="1"
    ATTRS{serial}=="6e4dcde89fdeea11b47832d299583cc7"         <---------
    ATTRS{speed}=="12"
    ATTRS{tx_lanes}=="1"
    ATTRS{urbnum}=="29"
    ATTRS{version}==" 2.00"


Und die Regel unter '/etc/udev/rules.d/10-local.rules' sieht so aus:

Code Auswählen Erweitern

ACTION=="add", ATTRS{idVendor}=="10c4", ATTR{idProduct}=="ea60", ATTR{serial}=="6e4dcde89fdeea11b47832d299583cc7", SYMLINK+="ebusdUSB"


[chris371]

Aber was mache ich falsch?

Ich würde sagen, Du hast udev angewiesen, einen Link auf das Raw-USB-Device zu setzen. Damit umgehst Du den cp210x Treiber und die Standard-Implementierung des Kernels für Usb-Seriell-Wandler.

Also muss die Regel beim tty-Device triggern, und mit "ATTRS" statt "ATTR" sagst Du udev, dass er auch in den Parent-Devices schauen darf.
Probier mal folgendes (ohne Gewähr )

Code Auswählen Erweitern

ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="6e4dcde89fdeea11b47832d299583cc7", SYMLINK+="ebusdUSB"


[Citrus91]

Ja, die gleiche Idee ist mir gestern beim Einschlafen auch gekommen. 

Und jetzt funktioniert es. Wichtig sei noch erwähnt, dass man anschließend nicht nur ein...

Code Auswählen Erweitern

sudo udevadm trigger
...macht, sondern auch ein Reboot.

Ich habe jetzt das BUS-Kabel angeschlossen. Im Log läuft jetzt folgendes immer durch:

Code Auswählen Erweitern

2023-01-08 13:15:01.240 [bus error] device status: missing enhanced byte 2


Ich würde mal von "enh" zurück auf "ens" wechseln.
Dann kommen im Log schon Nachrichten rein:

Code Auswählen Erweitern


2023-01-08 13:20:54.505 [main notice] ebusd 23.1.23.1 started with auto scan on enhanced device /dev/ebusdUSB
2023-01-08 13:20:55.205 [bus notice] device status: resetting
2023-01-08 13:20:55.208 [bus notice] bus started with own address 31/36
2023-01-08 13:20:55.253 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:55.295 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:55.314 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:55.338 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:56.707 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:56.750 [bus notice] signal acquired
2023-01-08 13:20:59.702 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:59.830 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:20:59.958 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:00.172 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:00.643 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:00.857 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:00.985 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:01.114 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:01.143 [bus notice] new master 10, master count 2
2023-01-08 13:21:01.203 [bus notice] new master 03, master count 3
2023-01-08 13:21:01.203 [update notice] received unknown MS cmd: 1008b5110101 / 093b316008ff4c0100ff
2023-01-08 13:21:01.469 [bus notice] new master 71, master count 4
2023-01-08 13:21:01.470 [update notice] received unknown MS cmd: 1076b5110101 / 09ff316008ff4c0000ff
2023-01-08 13:21:01.646 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:01.736 [update notice] received unknown MS cmd: 1076b512030f0001 / 0762020000800f03
2023-01-08 13:21:02.001 [update notice] received unknown MS cmd: 1008b51009000033ffffff060000 / 0101
2023-01-08 13:21:02.091 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:02.444 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:04.625 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:04.882 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:05.097 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:05.800 [main error] scan config 08: ERR: SYN received
2023-01-08 13:21:06.143 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:06.485 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:06.699 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:06.913 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:07.127 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:07.340 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:07.683 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:07.964 [bus notice] scan 15: ;Vaillant;72000;0118;7703
2023-01-08 13:21:07.965 [update notice] store 15 ident: done
2023-01-08 13:21:07.965 [update notice] sent scan-read scan.15  QQ=31: Vaillant;72000;0118;7703
2023-01-08 13:21:07.965 [bus notice] scan 15: ;Vaillant;72000;0118;7703
2023-01-08 13:21:08.020 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.063 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.619 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.662 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.676 [main notice] read common config file vaillant/broadcast.csv
2023-01-08 13:21:08.704 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.747 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.790 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.833 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.851 [main notice] read common config file vaillant/scan.csv
2023-01-08 13:21:08.876 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.918 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:08.961 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.004 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.029 [main notice] read common config file vaillant/general.csv
2023-01-08 13:21:09.047 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.080 [bus error] signal lost
2023-01-08 13:21:09.089 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.132 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.175 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.218 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.261 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.303 [main notice] read scan config file vaillant/15.720.csv for ID "72000", SW0118, HW7703
2023-01-08 13:21:09.303 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.346 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.389 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.432 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:09.474 [main notice] found messages: 457 (0 conditional on 0 conditions, 0 poll, 8 update)
2023-01-08 13:21:09.474 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:10.031 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:10.159 [bus notice] signal acquired
2023-01-08 13:21:10.202 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:10.245 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:12.032 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:12.037 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:12.053 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:12.600 [main error] scan config 76: ERR: SYN received
2023-01-08 13:21:12.686 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:15.358 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:15.494 [bus notice] new master 00, master count 5
2023-01-08 13:21:15.542 [update notice] received read 720 Time QQ=00: 13:21:17
2023-01-08 13:21:15.847 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:16.074 [update notice] received read 720 Date QQ=00: 08.01.2023
2023-01-08 13:21:16.292 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:16.420 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:16.784 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:17.088 [update notice] received read 720 GlobalSystemOff QQ=00: no
2023-01-08 13:21:17.610 [update notice] received read 720 HwcSFMode QQ=00: auto
2023-01-08 13:21:17.871 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:18.000 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:18.188 [update notice] received read 720 HwcStorageTemp QQ=00: 38
2023-01-08 13:21:18.448 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:21.094 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:21.182 [update notice] received unknown MS cmd: 1008b5110101 / 093b316008ff4c0100ff
2023-01-08 13:21:21.230 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:21.273 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:21.316 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:24.402 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:24.445 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:24.488 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:24.752 [update notice] received read 720 Hc1CircuitType QQ=00: mixer
2023-01-08 13:21:24.925 [bus notice] scan 05: ;Vaillant;VR921;2706;5703
2023-01-08 13:21:24.925 [update notice] store 05 ident: done
2023-01-08 13:21:24.926 [update notice] sent scan-read scan.05  QQ=31: Vaillant;VR921;2706;5703
2023-01-08 13:21:24.926 [bus notice] scan 05: ;Vaillant;VR921;2706;5703
2023-01-08 13:21:25.108 [update notice] sent unknown MS cmd: 3105b5090124 / 09003231323031383030
2023-01-08 13:21:25.473 [main error] unable to load scan config 05: no file from vaillant with prefix 05 matches ID "vr921", SW2706, HW5703
2023-01-08 13:21:25.473 [main error] scan config 05: ERR: read timeout
2023-01-08 13:21:25.946 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:26.383 [update notice] received read 720 z1OpMode QQ=00: day
2023-01-08 13:21:26.601 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:28.302 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:28.345 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:28.611 [main error] scan config 08: ERR: read timeout
2023-01-08 13:21:29.131 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:29.931 [bus error] device status: unexpected enhanced byte 2
2023-01-08 13:21:29.973 [bus error] device status: unexpected enhanced byte 2

Wie bekomme ich den "BUS Error" weg?


PS: Damit ich nicht jedes Mal fragen muss: Gibt es irgendwo eine Übersicht über Fehlermeldung und was man dagegen tun kann? Im Wiki habe ich irgendwie nichts gefunden.
PS: Ich habe ein paar Zeilen "BUS ERROR" aus dem gezeigten Logfile gelöscht.




Noch eine Verständnisfrage. Wenn ich den Daemon gestartet habe, dann kann ich mit "ebusctl" weiterarbeiten, oder? "ebusctl find" funktioniert, aber "ebusctl read hmu DateTime" (oder andere) bringt nur "ERR: element not found", obwohl es in der Liste steht, die mir "ebusctl find" ausgegeben hat.

[john30]

Code Auswählen Erweitern


2023-01-08 13:21:29.973 [bus error] device status: unexpected enhanced byte 2

ist das Log von nach dem Wechsel auf ens: oder davor?

Noch eine Verständnisfrage. Wenn ich den Daemon gestartet habe, dann kann ich mit "ebusctl" weiterarbeiten, oder? "ebusctl find" funktioniert, aber "ebusctl read hmu DateTime" (oder andere) bringt nur "ERR: element not found", obwohl es in der Liste steht, die mir "ebusctl find" ausgegeben hat.

"ebusctl read hmu DateTime" funktioniert nicht, aber "ebusctl read -c hmu DateTime" sollte

[Citrus91]

ist das Log von nach dem Wechsel auf ens: oder davor?

bei 'enh': "....missing enhanced byte 2"
bei 'ens': "...unexpected enhanced byte 2"

"ebusctl read hmu DateTime" funktioniert nicht, aber "ebusctl read -c hmu DateTime" sollte

Korrekt, jetzt kommt ein Wert. Danke.