eBus Schaltung in Betrieb nehmen

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

Vorheriges Thema - Nächstes Thema

theotherhalf

Ich hatte das mit Anleitung aus dem WIKI gemacht, da sich auf dem Bus gar nichts tat.

Beim Absetzen bekomme ich diese Meldung:
pi@raspberrypi:~ $ ebusctl info
version: ebusd 3.2.v3.2-21-g7d10104
update check: revision v3.2-12-g45b9bad available, broadcast.csv: different version available
signal: acquired
symbol rate: 30
max symbol rate: 308
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd


In /etc/default/ebusd habe ich folgende Parameter eingetragen:

EBUSD_OPTS="-d /dev/ttyUSB0 -p 8888 -l /var/log/ebusd.log  --scanconfig --latency=20000"

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

Reinhart

ob sich am Bus was tut siehst du ja an den Leds und die blinken bei dir. Du hast ebusctl i sehr schnell am Anfang gemacht, da hat der Dämon noch keinen Scan durchführen können. Warte 2-3 Minuten und schaue dann nochmals. Aber wichtiger sind dann gleich die Einträge im Log ( /var/log/ebusd.log ) , da siehst du dann was sich tatsächlich am Bus so tut.

LG
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

theotherhalf

Habe eben mal das Board getauscht. Habe 2 hier, aber das Ergebnis ist das gleiche.

Im Log findet sich folgendes:
018-12-14 21:44:19.018 [bus error] signal lost
2018-12-14 21:44:22.404 [bus notice] signal acquired
2018-12-14 21:44:32.001 [bus error] signal lost
2018-12-14 21:44:35.526 [bus notice] signal acquired
2018-12-14 21:44:40.049 [bus error] signal lost
2018-12-14 21:44:43.805 [bus notice] signal acquired
2018-12-14 21:44:45.039 [bus error] signal lost
2018-12-14 21:44:47.288 [bus notice] signal acquired
2018-12-14 21:44:50.049 [bus error] signal lost
2018-12-14 21:44:53.141 [bus notice] signal acquired
2018-12-14 21:44:56.036 [bus error] signal lost
2018-12-14 21:44:57.346 [bus notice] signal acquired
2018-12-14 21:45:00.058 [bus error] signal lost
2018-12-14 21:45:03.515 [bus notice] signal acquired
2018-12-14 21:45:06.034 [bus error] signal lost
2018-12-14 21:45:07.362 [bus notice] signal acquired
2018-12-14 21:45:09.066 [bus error] signal lost
2018-12-14 21:45:09.270 [bus notice] signal acquired
2018-12-14 21:45:22.006 [bus error] signal lost
2018-12-14 21:45:25.764 [bus notice] signal acquired
2018-12-14 21:45:30.023 [bus error] signal lost
2018-12-14 21:45:33.556 [bus notice] signal acquired
2018-12-14 21:45:36.034 [bus error] signal lost
2018-12-14 21:45:38.079 [bus notice] signal acquired
2018-12-14 21:45:40.009 [bus error] signal lost
2018-12-14 21:45:43.131 [bus notice] signal acquired
2018-12-14 21:45:47.052 [bus error] signal lost
2018-12-14 21:45:48.090 [bus notice] signal acquired
2018-12-14 21:45:51.070 [bus error] signal lost
2018-12-14 21:45:54.023 [bus notice] signal acquired
2018-12-14 21:45:58.031 [bus error] signal lost
2018-12-14 21:45:58.154 [bus notice] signal acquired
2018-12-14 21:46:00.017 [bus error] signal lost
2018-12-14 21:46:02.038 [bus notice] signal acquired


Eben ging ich zur Therme runter und die hatte sich aufgehangen...
Die Kommunikationsparameter werden nirgends angepasst. Baudrate etc.?
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

Zitat von: Reinhart am 14 Dezember 2018, 21:58:55
ob sich am Bus was tut siehst du ja an den Leds und die blinken bei dir. Du hast ebusctl i sehr schnell am Anfang gemacht, da hat der Dämon noch keinen Scan durchführen können. Warte 2-3 Minuten und schaue dann nochmals. Aber wichtiger sind dann gleich die Einträge im Log ( /var/log/ebusd.log ) , da siehst du dann was sich tatsächlich am Bus so tut.

LG

Gelb ist dauerhaft an, grün blinkt, aber rot bleibt aus.
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

Reinhart

#1414
das mit den Leds passt, rot ist die Sendeled.

Schau doch bitte einmal mit ps ax|grep ebusd ob der Dämon wirklich nur einmal läuft.

pi@raspberrypi:~ $ ps ax|grep ebusd
7287 ?        Ssl   90:56 /usr/bin/ebusd -d /dev/ttyebus --pollinterval=60 -p 8888 -l /var/log/ebusd.log --scanconfig -c http://ebusd.eu/config/ --accesslevel=* --httpport=8080 --htmlpath=/var/ebusd/html --mqttport=1883 --mqttjson --mqtthost=10.0.0.5 --mqtttopic=sonoff_ebusd/%circuit/%name
14707 pts/0    S+     0:00 grep --color=auto ebusd

so etwa

Dein Adapter verliert laut Log ständig die Verbindung, das muss einen Grund haben.
Immer zuerst den Adapter anschließen und dann erst den Dämon starten (sudo Service ebusd start).

LG

FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

theotherhalf

Zitat von: Reinhart am 14 Dezember 2018, 22:14:15
das mit den Leds passt, rot ist die Sendeled.

Schau doch bitte einmal mit ps ax|grep ebusd ob der Dämon wirklich nur einmal läuft.

pi@raspberrypi:~ $ ps ax|grep ebusd
7287 ?        Ssl   90:56 /usr/bin/ebusd -d /dev/ttyebus --pollinterval=60 -p 8888 -l /var/log/ebusd.log --scanconfig -c http://ebusd.eu/config/ --accesslevel=* --httpport=8080 --htmlpath=/var/ebusd/html --mqttport=1883 --mqttjson --mqtthost=10.0.0.5 --mqtttopic=sonoff_ebusd/%circuit/%name
14707 pts/0    S+     0:00 grep --color=auto ebusd

so etwa

Dein Adapter verliert laut Log ständig die Verbindung, das muss einen Grund haben.
Immer zuerst den Adapter anschließen und dann erst den Dämon starten (sudo Service ebusd start).

LG

pi@raspberrypi:~ $ ps ax|grep ebusd
1098 ?        Ssl    0:00 /usr/bin/ebusd -d /dev/ttyUSB0 -p 8888 -l /var/log/ebusd.log --scanconfig --latency=20000
1147 pts/1    S+     0:00 grep --color=auto ebusd


VRS620/3 hatte sich eben wieder aufgehangen.
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

Zitat von: Reinhart am 14 Dezember 2018, 22:14:15

Immer zuerst den Adapter anschließen und dann erst den Dämon starten (sudo Service ebusd start).



So mache ich es, ja.
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

Seltsam, in das Log wird schon seit 40min nichts mehr geschrieben.

2018-12-14 21:45:36.034 [bus error] signal lost
2018-12-14 21:45:38.079 [bus notice] signal acquired
2018-12-14 21:45:40.009 [bus error] signal lost
2018-12-14 21:45:43.131 [bus notice] signal acquired
2018-12-14 21:45:47.052 [bus error] signal lost
2018-12-14 21:45:48.090 [bus notice] signal acquired
2018-12-14 21:45:51.070 [bus error] signal lost
2018-12-14 21:45:54.023 [bus notice] signal acquired
2018-12-14 21:45:58.031 [bus error] signal lost
2018-12-14 21:45:58.154 [bus notice] signal acquired
2018-12-14 21:46:00.017 [bus error] signal lost
2018-12-14 21:46:02.038 [bus notice] signal acquired
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

Schlauer Det

Moin liebe Leute,

bin dabei, die Vorbereitungen zu treffen um eine Vaillant VR 70 über eine RPi-Platine an mein Heimnetz anzuschliessen.
Dazu möchte ich, damit ich keine Gewährleistungsansprüche verliere, den eBus über den Diagnosestecker an der VR 70 anzapfen.

Bisher habe ich herausgekriegt, dass es sich bei der Buchse um eine RJ10 handelt.
Leider habe ich keine Information über die Kontaktbelegung dieses Anschlusses.

Nun meine Fragen:

  • Wird der eBus über diese Diagnosebuchse geleitet?
  • Wie ist die Belegung der Buchse?
  • Ist diese Diagnosebuchse vielleicht ein RS232-Interface?
  • Gibt es noch Besonderheiten zu beachten?

Für sachdienliche Hinweise wäre ich sehr dankbar.


Grüße von der kalten Küste
Det  :)

jkriegl

Habe folgende Info aus dem Forum und meine 620 über die Leitung eines alten Tefeonhörers (Wertstoffhof) an einen kommerziellem ebus-Adapter angeschlossen. Läuft seit mehreren Jahren.
ZitatJa, es ist egal, ob an die Buchse oder die Klemme. Problem ist, dass diese Modularbuchse sehr schmal ist: 4p4c bedeutet, dass man eben keine Standard-Telefonleitung nehmen kann (6 Kontakte breit), sondern z.B. eine alte Anschlussleitung eines Telefonhörers verwenden muss (oder einen neuen 4er Stecker mit der Crimpzange an ein neues Kabel setzen darf).
Rpi 3, Fhem, Cul 868, HM-CC-RT-DN, HM-Sec-Sco, HM-ES-PMSw1-Pl, ebus (Vaillant), ECMD, Telegram, HTTPMOD, Xiaomi, Shelly

Reinhart

@theotheralf

erweitere deine Config um diesen Eintrag und starte den Dämon neu. Dann poste nach ein 1-2 Minuten das Log.
--loglevel=debug

und poste doch einmal "ps ax|grep ebusd"

LG
Reinhart
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

americanium

#1421
Hallo Leute,

eine kleine Erfolgsgeschichte und auch ein neues Problem:

1.) Ich habe nun ebusd auf einem frischen, eigenen RPi3 installiert und der MQTT Server läuft auf einem anderen RPi, siehe da nun scheint die MQTT Geschichte zu funktionieren.

2.) Aber ich habe jetzt grobe Signalprobleme. Ich bekomme immer nach einem reboot ein Signal und er findet die Configfiles. Aber nach einigen Sekunden bis maximal Minuten verliert er das Signal und alles steht wieder. Der Adapter hängt an der selben Leitung wie vorher, am selben Platz nur an nem Pi3 statt Pi2....

Gleich nach dem Neustart:
pi@raspberrypi:~ $ ebusctl i
version: ebusd 3.3.v3.3
signal: acquired
symbol rate: 24
max symbol rate: 43
reconnects: 0
masters: 4
messages: 11
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11
address 10: master #2
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9


Dann läufts mal:

pi@raspberrypi:~ $ ebusctl i
version: ebusd 3.3.v3.3
signal: acquired
symbol rate: 10
max symbol rate: 61
min arbitration micros: 3240
max arbitration micros: 3252
min symbol latency: 5
max symbol latency: 5
reconnects: 0
masters: 4
messages: 64
conditional: 0
poll: 0
update: 9
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0305;HW=0403", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0419;HW=4603"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0305;HW=0403"


Und zum Schluss:

version: ebusd 3.3.v3.3
update check: revision v3.3-4-g212b22d available, broadcast.csv: different versi                                                                                                                                                             on available, vaillant/15.700.csv: different version available, vaillant/broadca                                                                                                                                                             st.csv: different version available, vaillant/errors.inc: different version avai                                                                                                                                                             lable, vaillant/hcmode.inc: different version available
signal: no signal
reconnects: 1
masters: 4
messages: 462
conditional: 0
poll: 0
update: 9
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0305;HW=0403", loaded "v                                                                                                                                                             aillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0419;HW=4603", loaded "va                                                                                                                                                             illant/15.700.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0305;HW=0403"


Any ideas ?

Was mir auffällt:

- die Symbolrate ist sehr niedrig, oder ?
- die Rx LED des Adapter blinkt schnell (Daten werden empfangen?)
- die Tx LED rührt sich gar nicht

Danke!

Reinhart

Schau doch mal in die Logs ob hier ein Hinweis zu sehen ist.
Wenn bei "no Signal" die Led noch blinkt, liegt das Problem irgendwo in der Software und nicht in der Hardware.

LG
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

americanium

#1423
Zitat von: americanium am 30 Dezember 2018, 06:32:25
Hier ein Auszug

2018-12-30 06:28:05.273 [bus debug] arbitration delay 3234 micros
2018-12-30 06:28:05.273 [bus debug] switching from ready to send command
2018-12-30 06:28:05.282 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.291 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.300 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.309 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.309 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:05.318 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.318 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:05.346 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:05.346 [bus info] scan 2a cmd: 312a070400
2018-12-30 06:28:05.346 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:05.516 [network debug] dead connection removed - 0
2018-12-30 06:28:05.828 [bus debug] arbitration delay 3232 micros
2018-12-30 06:28:05.828 [bus debug] switching from ready to send command
2018-12-30 06:28:05.837 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.846 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.854 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.863 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.863 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:05.872 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:05.872 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:05.900 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:05.901 [bus info] scan 2b cmd: 312b070400
2018-12-30 06:28:05.901 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:06.383 [bus debug] ERR: arbitration lost during ready, retry
2018-12-30 06:28:06.438 [bus debug] ERR: read timeout during receive command, switching to skip
2018-12-30 06:28:07.004 [bus debug] arbitration delay 3259 micros
2018-12-30 06:28:07.004 [bus info] arbitration delay 3214 - 3259 micros
2018-12-30 06:28:07.004 [bus debug] switching from ready to send command
2018-12-30 06:28:07.013 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.021 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.030 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.039 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.039 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:07.048 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.048 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:07.076 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:07.077 [bus info] scan 2c cmd: 312c070400
2018-12-30 06:28:07.077 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:07.558 [bus debug] arbitration delay 3235 micros
2018-12-30 06:28:07.558 [bus debug] switching from ready to send command
2018-12-30 06:28:07.567 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.576 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.585 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.594 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.594 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:07.603 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:07.603 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:07.631 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:07.631 [bus info] scan 2d cmd: 312d070400
2018-12-30 06:28:07.631 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:08.113 [bus debug] arbitration delay 3233 micros
2018-12-30 06:28:08.113 [bus debug] switching from ready to send command
2018-12-30 06:28:08.122 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:08.131 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:08.140 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:08.148 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:08.148 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:08.156 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:08.156 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:08.184 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:08.184 [bus info] scan 2e cmd: 312e070400
2018-12-30 06:28:08.184 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:08.664 [bus debug] ERR: arbitration lost during ready, retry
2018-12-30 06:28:08.691 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2018-12-30 06:28:08.719 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:08.976 [mqtt debug] publish loxberry/global/uptime 32
2018-12-30 06:28:09.284 [bus debug] arbitration delay 3247 micros
2018-12-30 06:28:09.284 [bus debug] switching from ready to send command
2018-12-30 06:28:09.293 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.302 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.311 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.319 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.319 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:09.328 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.328 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:09.357 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:09.357 [bus info] scan 2f cmd: 312f070400
2018-12-30 06:28:09.357 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:09.839 [bus debug] arbitration delay 3233 micros
2018-12-30 06:28:09.839 [bus debug] switching from ready to send command
2018-12-30 06:28:09.847 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.856 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.865 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.874 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.874 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:09.883 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:09.883 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:09.911 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:09.911 [bus info] scan 32 cmd: 3132070400
2018-12-30 06:28:09.911 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:10.393 [bus debug] arbitration delay 3238 micros
2018-12-30 06:28:10.393 [bus debug] switching from ready to send command
2018-12-30 06:28:10.402 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:10.411 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:10.420 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:10.429 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:10.429 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:10.438 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:10.438 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:10.466 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:10.466 [bus info] scan 34 cmd: 3134070400
2018-12-30 06:28:10.466 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:10.948 [bus debug] ERR: arbitration lost during ready, retry
2018-12-30 06:28:10.987 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2018-12-30 06:28:10.991 [bus debug] ERR: NAK received during receive command ACK, switching to receive command
2018-12-30 06:28:11.082 [bus notice] new master 71, master count 4
2018-12-30 06:28:11.082 [update info] received MS cmd: 1076b512030f0001 / 07be020000801301
2018-12-30 06:28:11.082 [update notice] received unknown MS cmd: 1076b512030f0001 / 07be020000801301
2018-12-30 06:28:11.174 [bus debug] arbitration delay 3230 micros
2018-12-30 06:28:11.175 [bus debug] switching from ready to send command
2018-12-30 06:28:11.183 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.192 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.201 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.210 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.210 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:11.219 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.219 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:11.248 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:11.248 [bus info] scan 35 cmd: 3135070400
2018-12-30 06:28:11.248 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:11.730 [bus debug] arbitration delay 3234 micros
2018-12-30 06:28:11.730 [bus debug] switching from ready to send command
2018-12-30 06:28:11.739 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.748 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.757 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.766 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.766 [bus debug] switching from send command to send command CRC
2018-12-30 06:28:11.775 [bus debug] send/receive symbol latency 5 ms
2018-12-30 06:28:11.775 [bus debug] switching from send command CRC to receive command ACK
2018-12-30 06:28:11.803 [bus debug] notify request: ERR: read timeout
2018-12-30 06:28:11.803 [bus info] scan 36 cmd: 3136070400
2018-12-30 06:28:11.803 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2018-12-30 06:28:12.285 [bus debug] ERR: arbitration lost during ready, retry
2018-12-30 06:28:12.362 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2018-12-30 06:28:12.366 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2018-12-30 06:28:12.690 [bus notice] device invalid
2018-12-30 06:28:14.518 [main debug] performing regular tasks
2018-12-30 06:28:14.519 [bus info] scan 76 cmd: 3176070400
2018-12-30 06:28:14.716 [network debug] [00009] wait for result
2018-12-30 06:28:14.716 [network info] [00009] client connection opened 127.0.0.1
2018-12-30 06:28:17.703 [bus notice] re-opened /dev/ttyUSB0
2018-12-30 06:28:17.757 [bus info] scan 38 cmd: 3138070400
2018-12-30 06:28:17.757 [bus info] scan 39 cmd: 3139070400
2018-12-30 06:28:17.757 [bus info] scan 3a cmd: 313a070400
2018-12-30 06:28:17.757 [bus info] scan 3b cmd: 313b070400
2018-12-30 06:28:17.757 [bus info] scan 3c cmd: 313c070400
2018-12-30 06:28:17.757 [bus info] scan 3d cmd: 313d070400
2018-12-30 06:28:17.757 [bus info] scan 3e cmd: 313e070400
2018-12-30 06:28:17.757 [bus info] scan 40 cmd: 3140070400
2018-12-30 06:28:17.757 [bus info] scan 41 cmd: 3141070400
2018-12-30 06:28:17.757 [bus info] scan 42 cmd: 3142070400
2018-12-30 06:28:17.757 [bus info] scan 43 cmd: 3143070400
2018-12-30 06:28:17.758 [bus info] scan 44 cmd: 3144070400
2018-12-30 06:28:17.758 [bus info] scan 45 cmd: 3145070400
2018-12-30 06:28:17.758 [bus info] scan 46 cmd: 3146070400
2018-12-30 06:28:17.758 [bus info] scan 47 cmd: 3147070400
2018-12-30 06:28:17.758 [bus info] scan 48 cmd: 3148070400
2018-12-30 06:28:17.758 [bus info] scan 49 cmd: 3149070400
2018-12-30 06:28:17.758 [bus info] scan 4a cmd: 314a070400
2018-12-30 06:28:17.758 [bus info] scan 4b cmd: 314b070400
2018-12-30 06:28:17.758 [bus info] scan 4c cmd: 314c070400
2018-12-30 06:28:17.758 [bus info] scan 4d cmd: 314d070400
2018-12-30 06:28:17.758 [bus info] scan 4e cmd: 314e070400
2018-12-30 06:28:17.758 [bus info] scan 4f cmd: 314f070400
2018-12-30 06:28:17.758 [bus info] scan 50 cmd: 3150070400
2018-12-30 06:28:17.758 [bus info] scan 51 cmd: 3151070400
2018-12-30 06:28:17.758 [bus info] scan 52 cmd: 3152070400
2018-12-30 06:28:17.758 [bus info] scan 53 cmd: 3153070400
2018-12-30 06:28:17.758 [bus info] scan 54 cmd: 3154070400
2018-12-30 06:28:17.758 [bus info] scan 55 cmd: 3155070400
2018-12-30 06:28:17.758 [bus info] scan 56 cmd: 3156070400
2018-12-30 06:28:17.758 [bus info] scan 57 cmd: 3157070400
2018-12-30 06:28:17.758 [bus info] scan 58 cmd: 3158070400
2018-12-30 06:28:17.758 [bus info] scan 59 cmd: 3159070400
2018-12-30 06:28:17.758 [bus info] scan 5a cmd: 315a070400
2018-12-30 06:28:17.758 [bus info] scan 5b cmd: 315b070400
2018-12-30 06:28:17.758 [bus info] scan 5c cmd: 315c070400
2018-12-30 06:28:17.758 [bus info] scan 5d cmd: 315d070400
2018-12-30 06:28:17.758 [bus info] scan 5e cmd: 315e070400
2018-12-30 06:28:17.758 [bus info] scan 5f cmd: 315f070400
2018-12-30 06:28:17.758 [bus info] scan 60 cmd: 3160070400
2018-12-30 06:28:17.758 [bus info] scan 61 cmd: 3161070400
2018-12-30 06:28:17.758 [bus info] scan 62 cmd: 3162070400
2018-12-30 06:28:17.759 [bus info] scan 63 cmd: 3163070400
2018-12-30 06:28:17.759 [bus info] scan 64 cmd: 3164070400
2018-12-30 06:28:17.759 [bus info] scan 65 cmd: 3165070400
2018-12-30 06:28:17.759 [bus info] scan 66 cmd: 3166070400
2018-12-30 06:28:17.759 [bus info] scan 67 cmd: 3167070400
2018-12-30 06:28:17.759 [bus info] scan 68 cmd: 3168070400
2018-12-30 06:28:17.759 [bus info] scan 69 cmd: 3169070400
2018-12-30 06:28:17.759 [bus info] scan 6a cmd: 316a070400
2018-12-30 06:28:17.759 [bus info] scan 6b cmd: 316b070400
2018-12-30 06:28:17.759 [bus info] scan 6c cmd: 316c070400
2018-12-30 06:28:17.759 [bus info] scan 6d cmd: 316d070400
2018-12-30 06:28:17.759 [bus info] scan 6e cmd: 316e070400
2018-12-30 06:28:17.759 [bus info] scan 6f cmd: 316f070400
2018-12-30 06:28:17.759 [bus info] scan 72 cmd: 3172070400
2018-12-30 06:28:17.759 [bus info] scan 74 cmd: 3174070400
2018-12-30 06:28:17.759 [bus info] scan 75 cmd: 3175070400
2018-12-30 06:28:17.759 [bus info] scan 76 cmd: 3176070400
2018-12-30 06:28:17.759 [bus info] scan 78 cmd: 3178070400
2018-12-30 06:28:17.759 [bus info] scan 79 cmd: 3179070400
2018-12-30 06:28:17.759 [bus info] scan 7a cmd: 317a070400
2018-12-30 06:28:17.759 [bus info] scan 7b cmd: 317b070400
2018-12-30 06:28:17.759 [bus info] scan 7c cmd: 317c070400
2018-12-30 06:28:17.759 [bus info] scan 7d cmd: 317d070400
2018-12-30 06:28:17.759 [bus info] scan 7e cmd: 317e070400
2018-12-30 06:28:17.759 [bus info] scan 80 cmd: 3180070400
2018-12-30 06:28:17.759 [bus info] scan 81 cmd: 3181070400
2018-12-30 06:28:17.759 [bus info] scan 82 cmd: 3182070400
2018-12-30 06:28:17.759 [bus info] scan 83 cmd: 3183070400
2018-12-30 06:28:17.759 [bus info] scan 84 cmd: 3184070400
2018-12-30 06:28:17.759 [bus info] scan 85 cmd: 3185070400
2018-12-30 06:28:17.759 [bus info] scan 86 cmd: 3186070400
2018-12-30 06:28:17.760 [bus info] scan 87 cmd: 3187070400
2018-12-30 06:28:17.760 [bus info] scan 88 cmd: 3188070400
2018-12-30 06:28:17.760 [bus info] scan 89 cmd: 3189070400
2018-12-30 06:28:17.760 [bus info] scan 8a cmd: 318a070400
2018-12-30 06:28:17.760 [bus info] scan 8b cmd: 318b070400
2018-12-30 06:28:17.760 [bus info] scan 8c cmd: 318c070400
2018-12-30 06:28:17.760 [bus info] scan 8d cmd: 318d070400
2018-12-30 06:28:17.760 [bus info] scan 8e cmd: 318e070400
2018-12-30 06:28:17.760 [bus info] scan 8f cmd: 318f070400
2018-12-30 06:28:17.760 [bus info] scan 90 cmd: 3190070400
2018-12-30 06:28:17.760 [bus info] scan 91 cmd: 3191070400
2018-12-30 06:28:17.760 [bus info] scan 92 cmd: 3192070400
2018-12-30 06:28:17.760 [bus info] scan 93 cmd: 3193070400
2018-12-30 06:28:17.760 [bus info] scan 94 cmd: 3194070400
2018-12-30 06:28:17.760 [bus info] scan 95 cmd: 3195070400
2018-12-30 06:28:17.760 [bus info] scan 96 cmd: 3196070400
2018-12-30 06:28:17.760 [bus info] scan 97 cmd: 3197070400
2018-12-30 06:28:17.760 [bus info] scan 98 cmd: 3198070400
2018-12-30 06:28:17.760 [bus info] scan 99 cmd: 3199070400
2018-12-30 06:28:17.760 [bus info] scan 9a cmd: 319a070400
2018-12-30 06:28:17.760 [bus info] scan 9b cmd: 319b070400
2018-12-30 06:28:17.760 [bus info] scan 9c cmd: 319c070400
2018-12-30 06:28:17.760 [bus info] scan 9d cmd: 319d070400
2018-12-30 06:28:17.760 [bus info] scan 9e cmd: 319e070400
2018-12-30 06:28:17.760 [bus info] scan 9f cmd: 319f070400
2018-12-30 06:28:17.760 [bus info] scan a0 cmd: 31a0070400
2018-12-30 06:28:17.760 [bus info] scan a1 cmd: 31a1070400
2018-12-30 06:28:17.760 [bus info] scan a2 cmd: 31a2070400
2018-12-30 06:28:17.760 [bus info] scan a3 cmd: 31a3070400
2018-12-30 06:28:17.760 [bus info] scan a4 cmd: 31a4070400
2018-12-30 06:28:17.760 [bus info] scan a5 cmd: 31a5070400
2018-12-30 06:28:17.760 [bus info] scan a6 cmd: 31a6070400
2018-12-30 06:28:17.761 [bus info] scan a7 cmd: 31a7070400
2018-12-30 06:28:17.761 [bus info] scan a8 cmd: 31a8070400
2018-12-30 06:28:17.761 [bus info] scan ab cmd: 31ab070400
2018-12-30 06:28:17.761 [bus info] scan ac cmd: 31ac070400
2018-12-30 06:28:17.761 [bus info] scan ad cmd: 31ad070400
2018-12-30 06:28:17.761 [bus info] scan ae cmd: 31ae070400
2018-12-30 06:28:17.761 [bus info] scan af cmd: 31af070400
2018-12-30 06:28:17.761 [bus info] scan b0 cmd: 31b0070400
2018-12-30 06:28:17.761 [bus info] scan b1 cmd: 31b1070400
2018-12-30 06:28:17.761 [bus info] scan b2 cmd: 31b2070400
2018-12-30 06:28:17.761 [bus info] scan b3 cmd: 31b3070400
2018-12-30 06:28:17.761 [bus info] scan b4 cmd: 31b4070400
2018-12-30 06:28:17.761 [bus info] scan b5 cmd: 31b5070400
2018-12-30 06:28:17.761 [bus info] scan b6 cmd: 31b6070400
2018-12-30 06:28:17.761 [bus info] scan b7 cmd: 31b7070400
2018-12-30 06:28:17.761 [bus info] scan b8 cmd: 31b8070400
2018-12-30 06:28:17.761 [bus info] scan b9 cmd: 31b9070400
2018-12-30 06:28:17.761 [bus info] scan ba cmd: 31ba070400
2018-12-30 06:28:17.761 [bus info] scan bb cmd: 31bb070400
2018-12-30 06:28:17.761 [bus info] scan bc cmd: 31bc070400
2018-12-30 06:28:17.761 [bus info] scan bd cmd: 31bd070400
2018-12-30 06:28:17.761 [bus info] scan be cmd: 31be070400
2018-12-30 06:28:17.761 [bus info] scan bf cmd: 31bf070400
2018-12-30 06:28:17.761 [bus info] scan c0 cmd: 31c0070400
2018-12-30 06:28:17.761 [bus info] scan c1 cmd: 31c1070400
2018-12-30 06:28:17.761 [bus info] scan c2 cmd: 31c2070400
2018-12-30 06:28:17.761 [bus info] scan c3 cmd: 31c3070400
2018-12-30 06:28:17.761 [bus info] scan c4 cmd: 31c4070400
2018-12-30 06:28:17.761 [bus info] scan c5 cmd: 31c5070400
2018-12-30 06:28:17.761 [bus info] scan c6 cmd: 31c6070400
2018-12-30 06:28:17.761 [bus info] scan c7 cmd: 31c7070400
2018-12-30 06:28:17.761 [bus info] scan c8 cmd: 31c8070400
2018-12-30 06:28:17.762 [bus info] scan c9 cmd: 31c9070400
2018-12-30 06:28:17.762 [bus info] scan ca cmd: 31ca070400
2018-12-30 06:28:17.762 [bus info] scan cb cmd: 31cb070400
2018-12-30 06:28:17.762 [bus info] scan cc cmd: 31cc070400
2018-12-30 06:28:17.762 [bus info] scan cd cmd: 31cd070400
2018-12-30 06:28:17.762 [bus info] scan ce cmd: 31ce070400
2018-12-30 06:28:17.762 [bus info] scan cf cmd: 31cf070400
2018-12-30 06:28:17.762 [bus info] scan d0 cmd: 31d0070400
2018-12-30 06:28:17.762 [bus info] scan d1 cmd: 31d1070400
2018-12-30 06:28:17.762 [bus info] scan d2 cmd: 31d2070400
2018-12-30 06:28:17.762 [bus info] scan d3 cmd: 31d3070400
2018-12-30 06:28:17.762 [bus info] scan d4 cmd: 31d4070400
2018-12-30 06:28:17.762 [bus info] scan d5 cmd: 31d5070400
2018-12-30 06:28:17.762 [bus info] scan d6 cmd: 31d6070400
2018-12-30 06:28:17.762 [bus info] scan d7 cmd: 31d7070400
2018-12-30 06:28:17.762 [bus info] scan d8 cmd: 31d8070400
2018-12-30 06:28:17.762 [bus info] scan d9 cmd: 31d9070400
2018-12-30 06:28:17.762 [bus info] scan da cmd: 31da070400
2018-12-30 06:28:17.762 [bus info] scan db cmd: 31db070400
2018-12-30 06:28:17.762 [bus info] scan dc cmd: 31dc070400
2018-12-30 06:28:17.762 [bus info] scan dd cmd: 31dd070400
2018-12-30 06:28:17.762 [bus info] scan de cmd: 31de070400
2018-12-30 06:28:17.762 [bus info] scan df cmd: 31df070400
2018-12-30 06:28:17.762 [bus info] scan e0 cmd: 31e0070400
2018-12-30 06:28:17.762 [bus info] scan e1 cmd: 31e1070400
2018-12-30 06:28:17.762 [bus info] scan e2 cmd: 31e2070400
2018-12-30 06:28:17.762 [bus info] scan e3 cmd: 31e3070400
2018-12-30 06:28:17.762 [bus info] scan e4 cmd: 31e4070400
2018-12-30 06:28:17.762 [bus info] scan e5 cmd: 31e5070400
2018-12-30 06:28:17.762 [bus info] scan e6 cmd: 31e6070400
2018-12-30 06:28:17.762 [bus info] scan e7 cmd: 31e7070400
2018-12-30 06:28:17.763 [bus info] scan e8 cmd: 31e8070400
2018-12-30 06:28:17.763 [bus info] scan e9 cmd: 31e9070400
2018-12-30 06:28:17.763 [bus info] scan ea cmd: 31ea070400
2018-12-30 06:28:17.763 [bus info] scan eb cmd: 31eb070400
2018-12-30 06:28:17.763 [bus info] scan ec cmd: 31ec070400
2018-12-30 06:28:17.763 [bus info] scan ed cmd: 31ed070400
2018-12-30 06:28:17.763 [bus info] scan ee cmd: 31ee070400
2018-12-30 06:28:17.763 [bus info] scan ef cmd: 31ef070400
2018-12-30 06:28:17.763 [bus info] scan f2 cmd: 31f2070400
2018-12-30 06:28:17.763 [bus info] scan f4 cmd: 31f4070400
2018-12-30 06:28:17.763 [bus info] scan f5 cmd: 31f5070400
2018-12-30 06:28:17.763 [bus info] scan f6 cmd: 31f6070400
2018-12-30 06:28:17.763 [bus info] scan f8 cmd: 31f8070400
2018-12-30 06:28:17.763 [bus info] scan f9 cmd: 31f9070400
2018-12-30 06:28:17.763 [bus info] scan fa cmd: 31fa070400
2018-12-30 06:28:17.763 [bus info] scan fb cmd: 31fb070400
2018-12-30 06:28:17.763 [bus info] scan fc cmd: 31fc070400
2018-12-30 06:28:17.763 [bus info] scan fd cmd: 31fd070400
2018-12-30 06:28:17.763 [bus debug] ERR: read timeout during skip, switching to no signal
2018-12-30 06:28:17.763 [bus error] signal lost
2018-12-30 06:28:17.763 [main error] scan config 76: ERR: no signal
2018-12-30 06:28:17.765 [main debug] >>> r -f HwcOpTemp
2018-12-30 06:28:17.765 [main debug] <<< ERR: element not found
2018-12-30 06:28:17.766 [network info] [00009] connection closed
2018-12-30 06:28:17.815 [bus debug] ERR: SYN received during no signal, switching to ready
2018-12-30 06:28:17.815 [bus notice] signal acquired
2018-12-30 06:28:17.950 [update info] received MS cmd: 1076b51009000000ffffff050000 / 0101
2018-12-30 06:28:17.950 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2018-12-30 06:28:18.198 [bus debug] ERR: CRC error during receive command CRC, switching to receive command ACK
2018-12-30 06:28:18.242 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2018-12-30 06:28:18.720 [network debug] dead connection removed - 0
2018-12-30 06:28:19.991 [bus notice] device invalid
2018-12-30 06:28:20.892 [network info] [00010] client connection opened 127.0.0.1
2018-12-30 06:28:20.892 [network debug] [00010] wait for result
2018-12-30 06:28:20.894 [main debug] >>> r -f HwcOpMode
2018-12-30 06:28:20.894 [bus info] send message: 3115b52406020001000300
2018-12-30 06:28:24.991 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-12-30 06:28:24.991 [bus error] send to 15: ERR: no signal, give up
2018-12-30 06:28:24.991 [bus error] send message part 0: ERR: no signal
2018-12-30 06:28:24.991 [main debug] <<< ERR: no signal
2018-12-30 06:28:24.991 [bus debug] ERR: element not found during skip, switching to no signal
2018-12-30 06:28:24.991 [bus error] signal lost
2018-12-30 06:28:24.991 [bus notice] device invalid
2018-12-30 06:28:24.992 [network info] [00010] connection closed
2018-12-30 06:28:24.994 [mqtt debug] publish loxberry/global/uptime 48
2018-12-30 06:28:24.994 [mqtt debug] publish loxberry/global/signal false
2018-12-30 06:28:25.898 [network debug] dead connection removed - 0
2018-12-30 06:28:28.596 [network debug] [00011] wait for result
2018-12-30 06:28:28.596 [network info] [00011] client connection opened 127.0.0.1
2018-12-30 06:28:28.597 [main debug] performing regular tasks
2018-12-30 06:28:28.598 [main debug] >>> i
2018-12-30 06:28:28.598 [main debug] <<< version: ebusd 3.3.v3.3
signal: no signal
reconnects: 0
masters: 4
messages: 461
conditional: 0
poll ...
2018-12-30 06:28:28.599 [network info] [00011] connection closed
2018-12-30 06:28:29.598 [network debug] dead connection removed - 0
2018-12-30 06:28:30.007 [bus notice] re-opened /dev/ttyUSB0
2018-12-30 06:28:30.028 [bus notice] signal acquired
2018-12-30 06:28:30.754 [update info] received MS cmd: 1008b50702093c / 024102
2018-12-30 06:28:30.754 [update notice] received unknown MS cmd: 1008b50702093c / 024102
2018-12-30 06:28:30.974 [bus debug] ERR: read timeout during receive command, switching to skip
2018-12-30 06:28:33.612 [bus error] own master address 31 is used by another participant
2018-12-30 06:28:33.616 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2018-12-30 06:28:33.817 [bus debug] ERR: SYN received during receive command, switching to ready
2018-12-30 06:28:33.843 [bus debug] ERR: SYN received during receive response, switching to ready
2018-12-30 06:28:33.918 [bus debug] ERR: SYN received during receive response, switching to ready
2018-12-30 06:28:33.941 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2018-12-30 06:28:34.003 [bus notice] max. symbols per second: 157
2018-12-30 06:28:35.652 [bus notice] device invalid
2018-12-30 06:28:38.600 [main debug] performing regular tasks
2018-12-30 06:28:38.601 [bus info] scan 36 cmd: 3136070400
2018-12-30 06:28:40.012 [mqtt debug] publish loxberry/global/uptime 64
2018-12-30 06:28:40.012 [mqtt debug] publish loxberry/global/signal true
2018-12-30 06:28:40.666 [bus notice] re-opened /dev/ttyUSB0
2018-12-30 06:28:40.732 [bus debug] ERR: read timeout during skip, switching to no signal
2018-12-30 06:28:40.732 [main error] scan config 36: ERR: no signal
2018-12-30 06:28:40.732 [bus error] signal lost
2018-12-30 06:28:41.160 [bus debug] ERR: SYN received during no signal, switching to ready
2018-12-30 06:28:41.161 [bus notice] signal acquired
2018-12-30 06:28:41.365 [bus debug] ERR: generic device error during receive command CRC, switching to skip
2018-12-30 06:28:41.365 [bus notice] device invalid
2018-12-30 06:28:46.366 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-12-30 06:28:46.366 [bus debug] ERR: element not found during skip, switching to no signal
2018-12-30 06:28:46.366 [bus error] signal lost
2018-12-30 06:28:46.366 [bus notice] device invalid



dmesg:

[ 4843.103952] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[ 4848.125442] cp210x ttyUSB0: failed set request 0x0 status: -32
[ 4848.125450] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[ 4853.125937] cp210x ttyUSB0: failed set request 0x0 status: -32
[ 4853.125946] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[ 4858.146188] cp210x ttyUSB0: failed set request 0x0 status: -32
[ 4858.146196] cp210x ttyUSB0: cp210x_open - Unable to enable UART


Edit (10:03 Uhr):
Immer wenn ich das Modul abstecke und neu anstecke funktionierts wieder für ein paar Sekunden

signal: acquired
symbol rate: 174
max symbol rate: 176


hab von einem User ("usernobody") der glaub ich ein ähnliches Problem hatte (https://forum.fhem.de/index.php/topic,79600.255.html) und einen neuen UART benötigte...

und hier nochmal ein kompletter dmesg nach reboot

0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20 GMT 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85280, node_mem_map ba39f000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=adc524cf-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940232K/970752K available (7168K kernel code, 576K rwdata, 2076K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c9017c   ( 577 kB)
                      .bss : 0x80c97f04 - 0x80d468b0   ( 699 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25287 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000003] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000010] Switching to timer-based delay loop, resolution 52ns
[    0.000148] Console: colour dummy device 80x30
[    0.000158] console [tty1] enabled
[    0.000174] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000182] pid_max: default: 32768 minimum: 301
[    0.000354] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000364] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000912] Disabling memory control group subsystem
[    0.000956] CPU: Testing write buffer coherency: ok
[    0.001217] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001444] Setting up static identity map for 0x100000 - 0x10003c
[    0.001513] Hierarchical SRCU implementation.
[    0.001882] smp: Bringing up secondary CPUs ...
[    0.002356] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.002845] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.003311] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.003365] smp: Brought up 1 node, 4 CPUs
[    0.003371] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.003374] CPU: All CPU(s) started in HYP mode.
[    0.003376] CPU: Virtualization extensions available.
[    0.003916] devtmpfs: initialized
[    0.009097] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0
[    0.009472] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.009597] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.009607] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.009927] pinctrl core: initialized pinctrl subsystem
[    0.010386] NET: Registered protocol family 16
[    0.011855] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.014316] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.014320] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.014444] Serial: AMBA PL011 UART driver
[    0.015305] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.015540] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.031515] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1
[    0.032255] SCSI subsystem initialized
[    0.032376] usbcore: registered new interface driver usbfs
[    0.032403] usbcore: registered new interface driver hub
[    0.032448] usbcore: registered new device driver usb
[    0.040057] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-11-04 16:31
[    0.040783] clocksource: Switched to clocksource arch_sys_counter
[    0.080507] VFS: Disk quotas dquot_6.6.0
[    0.080556] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.080673] FS-Cache: Loaded
[    0.080828] CacheFiles: Loaded
[    0.085124] NET: Registered protocol family 2
[    0.085519] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.085574] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.085668] TCP: Hash tables configured (established 8192 bind 8192)
[    0.085743] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.085766] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.085889] NET: Registered protocol family 1
[    0.086149] RPC: Registered named UNIX socket transport module.
[    0.086152] RPC: Registered udp transport module.
[    0.086154] RPC: Registered tcp transport module.
[    0.086157] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.087015] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.088468] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.092575] FS-Cache: Netfs 'nfs' registered for caching
[    0.092898] NFS: Registering the id_resolver key type
[    0.092916] Key type id_resolver registered
[    0.092919] Key type id_legacy registered
[    0.092927] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.093926] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.093994] io scheduler noop registered
[    0.093998] io scheduler deadline registered (default)
[    0.094084] io scheduler cfq registered
[    0.094088] io scheduler mq-deadline registered
[    0.094091] io scheduler kyber registered
[    0.095576] BCM2708FB: allocated DMA memory fad10000
[    0.095592] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.100871] Console: switching to colour frame buffer device 82x26
[    0.103506] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.104211] bcm2835-rng 3f104000.rng: hwrng registered
[    0.104282] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.104505] vc-sm: Videocore shared memory driver
[    0.104647] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.109466] brd: module loaded
[    0.114144] loop: module loaded
[    0.114151] Loading iSCSI transport class v2.0-870.
[    0.114540] libphy: Fixed MDIO Bus: probed
[    0.114594] usbcore: registered new interface driver lan78xx
[    0.114621] usbcore: registered new interface driver smsc95xx
[    0.114630] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.142355] dwc_otg 3f980000.usb: base=0xf0980000
[    0.342467] Core Release: 2.80a
[    0.342472] Setting default values for core params
[    0.342491] Finished setting default values for core params
[    0.542633] Using Buffer DMA mode
[    0.542637] Periodic Transfer Interrupt Enhancement - disabled
[    0.542639] Multiprocessor Interrupt Enhancement - disabled
[    0.542643] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.542648] Dedicated Tx FIFOs mode
[    0.542853] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
[    0.542868] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.542872] dwc_otg: Microframe scheduler enabled
[    0.542897] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ea470
[    0.542902] WARN::hcd_init_fiq:460: FIQ ASM at 0x805ea7d8 length 36
[    0.542909] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[    0.542935] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.542952] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.542968] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.543004] Init: Port Power? op_state=1
[    0.543007] Init: Power Port (0)
[    0.543115] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.543120] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.543125] usb usb1: Product: DWC OTG Controller
[    0.543129] usb usb1: Manufacturer: Linux 4.14.79-v7+ dwc_otg_hcd
[    0.543133] usb usb1: SerialNumber: 3f980000.usb
[    0.543453] hub 1-0:1.0: USB hub found
[    0.543473] hub 1-0:1.0: 1 port detected
[    0.543739] dwc_otg: FIQ enabled
[    0.543742] dwc_otg: NAK holdoff enabled
[    0.543745] dwc_otg: FIQ split-transaction FSM enabled
[    0.543750] Module dwc_common_port init
[    0.543872] usbcore: registered new interface driver usb-storage
[    0.543958] mousedev: PS/2 mouse device common for all mice
[    0.543998] IR NEC protocol handler initialized
[    0.544001] IR RC5(x/sz) protocol handler initialized
[    0.544004] IR RC6 protocol handler initialized
[    0.544007] IR JVC protocol handler initialized
[    0.544009] IR Sony protocol handler initialized
[    0.544012] IR SANYO protocol handler initialized
[    0.544014] IR Sharp protocol handler initialized
[    0.544017] IR MCE Keyboard/mouse protocol handler initialized
[    0.544020] IR XMP protocol handler initialized
[    0.544383] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.544523] bcm2835-cpufreq: min=1200000 max=1200000
[    0.544711] sdhci: Secure Digital Host Controller Interface driver
[    0.544714] sdhci: Copyright(c) Pierre Ossman
[    0.544910] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.545077] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.545125] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.546191] ledtrig-cpu: registered to indicate activity on CPUs
[    0.546288] hidraw: raw HID events driver (C) Jiri Kosina
[    0.546367] usbcore: registered new interface driver usbhid
[    0.546369] usbhid: USB HID core driver
[    0.546776] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.547741] [vc_sm_connected_init]: start
[    0.554811] [vc_sm_connected_init]: end - returning 0
[    0.555148] Initializing XFRM netlink socket
[    0.555161] NET: Registered protocol family 17
[    0.555220] Key type dns_resolver registered
[    0.555446] Registering SWP/SWPB emulation handler
[    0.555739] registered taskstats version 1
[    0.558967] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.559007] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.559831] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 166, base_baud = 50000000) is a 16550
[    0.560299] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.560303] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.611138] sdhost: log_buf @ bad07000 (fad07000)
[    0.647041] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.648535] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.650027] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.652725] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.690790] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.691331] of_cfs_init
[    0.691382] of_cfs_init: OK
[    0.691725] Waiting for root device PARTUUID=adc524cf-02...
[    0.727517] random: fast init done
[    0.757842] mmc0: host does not support reading read-only switch, assuming write-enable
[    0.760405] mmc0: new high speed SDHC card at address 0007
[    0.760710] mmcblk0: mmc0:0007 SD16G 14.5 GiB
[    0.761066] Indeed it is in host mode hprt0 = 00021501
[    0.821997]  mmcblk0: p1 p2
[    0.826902] mmc1: new high speed SDIO card at address 0001
[    0.853253] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    0.853257] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    0.970803] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    0.970884] Indeed it is in host mode hprt0 = 00001101
[    1.210995] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.211003] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.211353] hub 1-1:1.0: USB hub found
[    1.211403] hub 1-1:1.0: 5 ports detected
[    1.530795] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.660923] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.660929] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.663232] smsc95xx v1.0.6
[    1.752621] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a9:ef:2c
[    1.850791] usb 1-1.4: new full-speed USB device number 4 using dwc_otg
[    2.041005] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60
[    2.041010] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.041015] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
[    2.041019] usb 1-1.4: Manufacturer: Silicon Labs
[    2.041023] usb 1-1.4: SerialNumber: 0001
[   12.518477] EXT4-fs (mmcblk0p2): recovery complete
[   12.547723] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   12.547758] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[   12.556734] devtmpfs: mounted
[   12.558392] Freeing unused kernel memory: 1024K
[   12.991546] systemd[1]: System time before build time, advancing clock.
[   13.118506] NET: Registered protocol family 10
[   13.119186] Segment Routing with IPv6
[   13.128018] ip_tables: (C) 2000-2006 Netfilter Core Team
[   13.144754] random: systemd: uninitialized urandom read (16 bytes read)
[   13.148052] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[   13.148353] systemd[1]: Detected architecture arm.
[   13.158122] systemd[1]: Set hostname to <raspberrypi>.
[   13.194907] random: systemd: uninitialized urandom read (16 bytes read)
[   13.215675] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
[   13.553877] systemd[1]: Created slice System Slice.
[   13.554378] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[   13.554714] systemd[1]: Created slice system-autologin.slice.
[   13.554927] systemd[1]: Listening on udev Control Socket.
[   13.555066] systemd[1]: Listening on Syslog Socket.
[   13.555253] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   13.555321] systemd[1]: Reached target Swap.
[   13.648904] i2c /dev entries driver
[   14.063023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   14.095797] systemd-journald[86]: Received request to flush runtime journal from PID 1
[   14.464071] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[   14.466860] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[   14.587583] usbcore: registered new interface driver usbserial
[   14.587813] usbcore: registered new interface driver usbserial_generic
[   14.588033] usbserial: USB Serial support registered for generic
[   14.602753] usbcore: registered new interface driver cp210x
[   14.602998] usbserial: USB Serial support registered for cp210x
[   14.603268] cp210x 1-1.4:1.0: cp210x converter detected
[   14.612126] usb 1-1.4: cp210x converter now attached to ttyUSB0
[   14.626330] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   14.630905] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[   14.631111] usbcore: registered new interface driver brcmfmac
[   14.874060] random: crng init done
[   14.874069] random: 7 urandom warning(s) missed due to ratelimiting
[   14.888832] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[   14.889450] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14
[   16.533874] uart-pl011 3f201000.serial: no DMA platform data
[   16.825236] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   16.825246] brcmfmac: power management disabled
[   16.904886] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[   17.292322] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   18.880382] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[   22.545758] Bluetooth: Core ver 2.22
[   22.545818] NET: Registered protocol family 31
[   22.545821] Bluetooth: HCI device and connection manager initialized
[   22.545836] Bluetooth: HCI socket layer initialized
[   22.545844] Bluetooth: L2CAP socket layer initialized
[   22.545864] Bluetooth: SCO socket layer initialized
[   22.568314] Bluetooth: HCI UART driver ver 2.3
[   22.568322] Bluetooth: HCI UART protocol H4 registered
[   22.568325] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   22.568449] Bluetooth: HCI UART protocol Broadcom registered
[   32.522123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.522131] Bluetooth: BNEP filters: protocol multicast
[   32.522145] Bluetooth: BNEP socket layer initialized
[   32.571104] Bluetooth: RFCOMM TTY layer initialized
[   32.571183] Bluetooth: RFCOMM socket layer initialized
[   32.571204] Bluetooth: RFCOMM ver 1.11
[   32.896342] fuse init (API version 7.26)
[   71.008659] cp210x ttyUSB0: failed get req 0x8 size 1 status: 0
[   84.850258] dwc_otg: DEVICE:004 : update_urb_state_xfer_comp:747:trimming xfer length
[   85.767662] cp210x ttyUSB0: failed get req 0x8 size 1 status: -32
[   85.767789] cp210x ttyUSB0: failed set req 0x1e size 4 status: -32
[   85.767794] cp210x ttyUSB0: failed to set baud rate to 9600
[   85.768162] cp210x ttyUSB0: failed to get comm status: -71
[   85.768286] cp210x ttyUSB0: failed set request 0x7 status: -71
[   85.768410] cp210x ttyUSB0: failed set request 0x12 status: -71
[   85.768535] cp210x ttyUSB0: failed set request 0x0 status: -71
[  104.039052] cp210x ttyUSB0: failed get req 0x8 size 1 status: -71
[  104.039162] cp210x ttyUSB0: failed set req 0x1e size 4 status: -71
[  104.039168] cp210x ttyUSB0: failed to set baud rate to 9600
[  104.039286] cp210x ttyUSB0: failed to get comm status: -71
[  104.039411] cp210x ttyUSB0: failed set request 0x7 status: -71
[  104.039535] cp210x ttyUSB0: failed set request 0x12 status: -71
[  104.039660] cp210x ttyUSB0: failed set request 0x0 status: -71
[  109.990800] cp210x ttyUSB0: failed get req 0x8 size 1 status: -71
[  109.991037] cp210x ttyUSB0: failed to get comm status: -71
[  109.991161] cp210x ttyUSB0: failed set request 0x7 status: -71
[  109.991285] cp210x ttyUSB0: failed set request 0x12 status: -71
[  109.991410] cp210x ttyUSB0: failed set request 0x0 status: -71
[  125.437049] cp210x ttyUSB0: failed get req 0x8 size 1 status: -71
[  125.437288] cp210x ttyUSB0: failed to get comm status: -71
[  125.437412] cp210x ttyUSB0: failed set request 0x7 status: -71
[  125.437536] cp210x ttyUSB0: failed set request 0x12 status: -71
[  125.437968] cp210x ttyUSB0: failed set request 0x0 status: -71
[  137.588051] cp210x ttyUSB0: failed get req 0x8 size 1 status: -71
[  137.588287] cp210x ttyUSB0: failed to get comm status: -71
[  137.588412] cp210x ttyUSB0: failed set request 0x7 status: -71
[  137.588536] cp210x ttyUSB0: failed set request 0x12 status: -71
[  137.588660] cp210x ttyUSB0: failed set request 0x0 status: -71


Reinhart

cp210x ttyUSB0: failed get req 0x8 size 1 status: -32

ah ja, der scheint defekt zu sein!
Du bist eh aus Österreich (Inlandsporto) , wenn du willst kann ich dir einen anderen zusenden! Aber die sind alle aus derselben Serie! Ich habe auch neue bestellt, aber die dauern noch ein paar Tage bis ich sie habe, die liegen noch in Wien am Zoll.

LG
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa