[gelöst] Osram Smart+ Plug mit MQTT schalten

sprudelverduenner · 11 Mai 2020, 08:29:30

Guten morgen zusammen,

ich habe zwei Osram Smart+ Plug, die ich in der Hauptsache als Zigbee Repeater einsetzen möchte / werde.

Ich habe den CC2531 Stick und habe auch bereits einige Xiaomi und Ikea Sensoren am laufen.

Der STATE der Steckdosen wird beim manuellen Schalten an der Steckdose selber auch in FEHM erkannt - ich kann jedoch die Steckdosen nicht aus FHEM heraus schalten, so dass ich von einer falschen Konfiguration im eigentlichen Device ausgehe.

Vielleicht könnt Ihr bitte mal über meine Konfiguration drüber schauen ?

List osram.steckdose:

Code Auswählen

Internals:
   CFGFN      
   CID        zigbee_0xf0d1b800001350d6
   DEF        zigbee_0xf0d1b800001350d6
   DEVICETOPIC zigbee2mqtt/0xf0d1b800001350d6
   FUUID      5eb8e09e-f33f-8d5d-9500-9f8601b546bc7538
   IODev      MQTT2_SERVER
   LASTInputDev MQTT2_SERVER
   MQTT2_SERVER_MSGCNT 15
   MQTT2_SERVER_TIME 2020-05-11 08:20:25
   MSGCNT     15
   NAME       osram.steckdose
   NR         73221
   STATE      off
   TYPE       MQTT2_DEVICE
   READINGS:
     2020-05-11 07:20:31   associatedWith  MQTT2_zigbee_pi
     2020-05-11 08:20:25   linkquality     39
     2020-05-11 08:20:25   state           OFF
Attributes:
   IODev      MQTT2_SERVER
   devicetopic zigbee2mqtt/0xf0d1b800001350d6
   eventMap   { dev=>{ON=>'on',OFF=>'off'} }
   genericDeviceType switch
   model      zigbee2mqtt_plug
   readingList $DEVICETOPIC:.* { json2nameValue($EVENT) }
   room       MQTT2_DEVICE
   setList    on:noArg $DEVICETOPIC/set {"state":"ON"}
  off:noArg $DEVICETOPIC/set {"state":"OFF"}
   setStateList on off
   webCmd     :

Ich habe schon vieles nach einigen Foren Beiträgen probiert - danach ging dann oftmals noch nicht einmal der STATE ....

LG, Sprudelverduenner

Beta-User · 11 Mai 2020, 17:02:15

Hi sprudelverdünner,
zumindest von hier aus sieht die Konfiguration soweit ok aus (ich habe zigbee2mqtt aber schon länger nicht mehr im Einsatz, daher unter Vorbehalt).

Das sieht so aus, also hättest du ein MQTT2_SERVER-Device als Server im Einsatz, von daher dürfte das Problem eher auf der Strecke zwischen FHEM/MQTT-Server und zigbee2mqtt liegen. Bist du sicher, dass diese Verbindung "gut" ist, oder hast du da irgendwelche Hänger? Wäre ggf. sinnvoll, mal zu erläutern, wo der zigbee2mqtt-Dienst sitzt, wie der auf die USB-Schnittstelle zugreift und ähnliches...

sprudelverduenner · 11 Mai 2020, 21:00:42

Hi Beta-User,

Ich versuche gerne alle Deine Fragen zu beantworten.

Ich betreibe einen Raspberry Pi mit buster und dem CC2531 an der USB Schnittstelle.
Es läuft der MQTT2_Server und eine MQTT2_zigbee Bridge.

List von der Bridge:

Code Auswählen

nternals:
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC MQTT2_zigbee_bridge
   FUUID      5cb23241-f33f-fbf8-06a8-956f7ddde9cfdc83
   IODev      MQTT2_SERVER
   LASTInputDev MQTT2_SERVER
   MQTT2_SERVER_MSGCNT 10
   MQTT2_SERVER_TIME 2020-05-11 07:20:17
   MSGCNT     10
   NAME       MQTT2_zigbee_bridge
   NR         714
   STATE      online
   TYPE       MQTT2_DEVICE
   READINGS:
     2020-04-28 19:04:12   commit          da4d26a
     2020-04-28 19:04:12   coordinator_meta_maintrel 3
     2020-04-28 19:04:12   coordinator_meta_majorrel 2
     2020-04-28 19:04:12   coordinator_meta_minorrel 6
     2020-04-28 19:04:12   coordinator_meta_product 0
     2020-04-28 19:04:12   coordinator_meta_revision 20190608
     2020-04-28 19:04:12   coordinator_meta_transportrev 2
     2020-04-28 19:04:12   coordinator_type zStack12
     2020-05-11 07:20:17   log             {"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0xf0d1b800001350d6","model":"AC10691","vendor":"OSRAM","description":"Smart+ plug","supported":true}}
     2020-04-28 19:04:12   log_level       info
     2020-04-28 19:04:12   permit_join     true
     2020-05-09 17:11:04   state           online
     2020-04-28 19:04:12   version         1.8.0
Attributes:
   IODev      MQTT2_SERVER
   bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]*)[/]?.*:.* "zigbee_$1"
   comment    To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
   getList    devicelist:noArg log zigbee2mqtt/bridge/config/devices
  networkmap_raw:noArg raw zigbee2mqtt/bridge/networkmap raw
  networkmap_graphviz:noArg graphviz zigbee2mqtt/bridge/networkmap graphviz
   model      zigbee2mqtt_bridge
   readingList zigbee2mqtt/bridge/state:.* state
  zigbee2mqtt/bridge/config/devices:.* {}
  zigbee2mqtt/bridge/config/log_level:.* log_level
  zigbee2mqtt/bridge/config/permit_join:.* permit_join
  zigbee2mqtt/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }
  zigbee2mqtt/bridge/log:.*\"type\".\"devices\".\"message\".* devices
  zigbee2mqtt/bridge/log:.* log
  zigbee2mqtt/bridge/networkmap:.* {}
  zigbee2mqtt/bridge/networkmap/graphviz:.* graphviz
  zigbee2mqtt/bridge/networkmap/raw:.* raw
  zigbee2mqtt/bridge/config:.* { json2nameValue($EVENT) }
   room       9.6_ZigBee
   setList    log_level:debug,info,warn,error zigbee2mqtt/bridge/config/log_level $EVTPART1
  permit_join:true,false zigbee2mqtt/bridge/config/permit_join $EVTPART1
  remove:textField zigbee2mqtt/bridge/config/remove $EVTPART1
  y_device_setting:textField zigbee2mqtt/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}
  x_bind:textField zigbee2mqtt/bridge/bind/$EVTPART1 $EVTPART2
  x_bind_unbind:textField zigbee2mqtt/bridge/unbind/$EVTPART1 $EVTPART2
  x_device_options:textField zigbee2mqtt/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}
  x_group_add_to:textField zigbee2mqtt/bridge/group/$EVTPART1/add $EVTPART2
  x_group_rm_from:textField zigbee2mqtt/bridge/group/$EVTPART1/remove $EVTPART2
  x_group_rm_from_all:textField zigbee2mqtt/bridge/group/$EVTPART1/remove_all $EVTPART2
  x_group_add_group:textField zigbee2mqtt/bridge/config/add_group $EVTPART1
  x_group_rm_group:textField zigbee2mqtt/bridge/config/remove_group $EVTPART1
  z_elapsed:textField zigbee2mqtt/bridge/config/elapsed $EVTPART1
  z_last_seen:disable,ISO_8601,epoch,ISO_8601_local zigbee2mqtt/bridge/config/last_seen $EVTPART1
  z_ban:textField zigbee2mqtt/bridge/config/ban $EVTPART1
  z_rename:textField zigbee2mqtt/bridge/config/rename  {"old":"$EVTPART1","new":"$EVTPART2"}
  z_reset_CC:noArg zigbee2mqtt/bridge/config/reset
   setStateList on off

Neben den Steckdosen betreibe ich sonst nur Sensoren - das heißt Fernbedienungen, Bewegungsmelder und Öffnungsmelder.
Soweit ich das beurteilen kann laufen die ganzen Sensoren ohne ,,Hänger" - heißt eine Reaktion in FHEM ist unverzüglich nach einem Auslösen zu sehen.

LG, Sprudelverduenner

Beta-User · 12 Mai 2020, 10:32:46

Ein paar Infos aus der yaml wären gut: wie wird der USB-Stick da angesprochen? by-id oder ttyACM0? Wie der MQTT2-Server? localhost?

Und: gibt es weitere USB-Devices an diesem Rechner?

sprudelverduenner · 13 Mai 2020, 08:38:02

Here we go....

cofiguration.yaml

Code Auswählen

  GNU nano 3.2                                            /opt/zigbee2mqtt/data/configuration.yaml

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://localhost'
serial:
  port: /dev/ttyACM0
devices:
  '0x00158d0003cb832b':
    friendly_name: '0x00158d0003cb832b'
  '0x90fd9ffffedf660b':
    friendly_name: '0x90fd9ffffedf660b'
  '0x00158d00044e7aec':
    friendly_name: '0x00158d00044e7aec'
  '0x00158d00027ce0d2':
    friendly_name: '0x00158d00027ce0d2'
  '0x00158d00044cabe1':
    friendly_name: '0x00158d00044cabe1'
  '0x00158d0003501c21':
    friendly_name: '0x00158d0003501c21'
  '0x00158d0003f3ce06':
    friendly_name: '0x00158d0003f3ce06'
  '0x00158d0004458c88':
    friendly_name: '0x00158d0004458c88'
  '0x00158d00039dcbf6':
    friendly_name: '0x00158d00039dcbf6'
  '0x00158d0004038e3c':
    friendly_name: '0x00158d0004038e3c'
  '0x7cb03eaa0a0016c6':
    friendly_name: '0x7cb03eaa0a0016c6'
  '0x00158d00029b1013':
    friendly_name: '0x00158d00029b1013'
  '0x00158d0002ea2fd3':
    friendly_name: '0x00158d0002ea2fd3'
  '0xf0d1b800001350d6':
    friendly_name: '0xf0d1b800001350d6'

Also nicht per ID. Es ist aber auch der einzige USB-Stick am RasPi.

Welche Infos brauchst Du evtl. noch weiter??

Danke für Deine Hilfe.

Beta-User · 13 Mai 2020, 13:02:06

Hmm, dann sieht das auf der Seite erst mal sauber aus... (das auch in der yaml by-id zu machen ist aber auch eine gute Idee, sonst hast du das evtl. irgendwann später dann ggf. vergessen).

Da du sonst nur Sensorik hast, könnte es auch ein Stromproblem (senden kostet mehr Energie) sein, aber sonst fällt mir im Moment dazu auch nicht mehr viel ein. Schau' mal, ob du in "dmesg" was findest. Müßte so passen:

Code Auswählen

dmesg | grep -i usb
Falls da häufige reconnects stehen, ist an der Stelle was faul.

sprudelverduenner · 13 Mai 2020, 17:25:03

Ich glaube Du hast ins schwarze getroffen!?

Mein

Code Auswählen

dmesg | grep -i usb ergab:

Code Auswählen

[    0.071210] usbcore: registered new interface driver usbfs
[    0.071292] usbcore: registered new interface driver hub
[    0.071404] usbcore: registered new device driver usb
[    0.306242] usbcore: registered new interface driver lan78xx
[    0.308701] usbcore: registered new interface driver smsc95xx
[    0.341370] dwc_otg 3f980000.usb: base=(ptrval)
[    0.786132] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.788394] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.790716] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[    0.797704] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.802240] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.804655] usb usb1: Product: DWC OTG Controller
[    0.807020] usb usb1: Manufacturer: Linux 4.19.75-v7+ dwc_otg_hcd
[    0.809440] usb usb1: SerialNumber: 3f980000.usb
[    0.812402] hub 1-0:1.0: USB hub found
[    0.817756] usbcore: registered new interface driver usb-storage
[    0.849295] usbcore: registered new interface driver usbhid
[    0.851949] usbhid: USB HID core driver
[    1.241809] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.482112] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    1.487428] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.490947] hub 1-1:1.0: USB hub found
[    1.811805] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.942130] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    1.947602] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.045675] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:48:1a:64
[    2.151896] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[    2.251868] usb 1-1.5: device descriptor read/64, error -32
[    2.481813] usb 1-1.5: device descriptor read/64, error -32
[    2.701811] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
[    2.801802] usb 1-1.5: device descriptor read/64, error -32
[    3.031843] usb 1-1.5: device descriptor read/64, error -32
[    3.152076] usb 1-1-port5: attempt power cycle
[    3.811870] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
[    4.251837] usb 1-1.5: device not accepting address 6, error -32
[    4.351873] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
[    4.791849] usb 1-1.5: device not accepting address 7, error -32
[    4.792011] usb 1-1-port5: unable to enumerate USB device
[    5.108521] usbcore: registered new interface driver brcmfmac
[   82.651949] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
[   82.971944] usb 1-1.5: device descriptor read/64, error -32
[   83.631966] usb 1-1.5: device not accepting address 8, error -32
[   83.951968] usb 1-1.5: new full-speed USB device number 9 using dwc_otg
[   84.051948] usb 1-1.5: device descriptor read/64, error -32
[   84.272028] usb 1-1.5: device descriptor read/64, error -32
[   84.392110] usb 1-1-port5: attempt power cycle
[   85.052137] usb 1-1.5: new full-speed USB device number 10 using dwc_otg
[   85.491966] usb 1-1.5: device not accepting address 10, error -32
[   85.591986] usb 1-1.5: new full-speed USB device number 11 using dwc_otg
[   86.031984] usb 1-1.5: device not accepting address 11, error -32
[   86.032106] usb 1-1-port5: unable to enumerate USB device
[   86.781988] usb 1-1.5: new full-speed USB device number 12 using dwc_otg
[   86.934405] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[   86.934422] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   86.934427] usb 1-1.5: Product: TI CC2531 USB CDC
[   86.934431] usb 1-1.5: Manufacturer: Texas Instruments
[   86.934436] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[   86.975667] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[   86.977737] usbcore: registered new interface driver cdc_acm
[   86.977747] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   87.729669] usb 1-1.5: USB disconnect, device number 12
[   88.021968] usb 1-1.5: new full-speed USB device number 13 using dwc_otg
[   88.157713] usb 1-1.5: unable to read config index 0 descriptor/all
[   88.157725] usb 1-1.5: can't read configurations, error -32
[   91.872013] usb 1-1.5: new full-speed USB device number 15 using dwc_otg
[   92.019878] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[   92.019890] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   92.019895] usb 1-1.5: Product: TI CC2531 USB CDC
[   92.019900] usb 1-1.5: Manufacturer: Texas Instruments
[   92.019905] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[   92.022254] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[   92.081768] usb 1-1.5: USB disconnect, device number 15
[   93.142065] usb 1-1.5: new full-speed USB device number 16 using dwc_otg
[   99.672036] usb 1-1.5: new full-speed USB device number 17 using dwc_otg
[   99.821006] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[   99.821017] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   99.821022] usb 1-1.5: Product: TI CC2531 USB CDC
[   99.821027] usb 1-1.5: Manufacturer: Texas Instruments
[   99.821032] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[   99.823640] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  109.233957] usb 1-1.5: USB disconnect, device number 17
[  110.582015] usb 1-1.5: new full-speed USB device number 18 using dwc_otg
[  110.735138] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  110.735148] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  110.735153] usb 1-1.5: Product: TI CC2531 USB CDC
[  110.735158] usb 1-1.5: Manufacturer: Texas Instruments
[  110.735163] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[  110.737244] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  111.025712] usb 1-1.5: USB disconnect, device number 18
[  111.322016] usb 1-1.5: new full-speed USB device number 19 using dwc_otg
[  111.478506] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  111.478517] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  111.478522] usb 1-1.5: Product: TI CC2531 USB CDC
[  111.478527] usb 1-1.5: Manufacturer: Texas Instruments
[  111.478532] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[  111.481580] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  111.793743] usb 1-1.5: USB disconnect, device number 19
[  112.102031] usb 1-1.5: new full-speed USB device number 20 using dwc_otg
[  112.254142] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  112.254153] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  112.254158] usb 1-1.5: Product: TI CC2531 USB CDC
[  112.254163] usb 1-1.5: Manufacturer: Texas Instruments
[  112.254170] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[  112.257235] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  117.425721] usb 1-1.5: USB disconnect, device number 20
[  118.992154] usb 1-1.5: new full-speed USB device number 21 using dwc_otg
[  124.622019] usb 1-1.5: new full-speed USB device number 22 using dwc_otg
[  124.780983] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  124.780994] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  124.780999] usb 1-1.5: Product: TI CC2531 USB CDC
[  124.781004] usb 1-1.5: Manufacturer: Texas Instruments
[  124.781008] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[  124.783244] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  125.362976] usb 1-1.5: USB disconnect, device number 22
[  125.662047] usb 1-1.5: new full-speed USB device number 23 using dwc_otg
[  125.814134] usb 1-1.5: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  125.814144] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  125.814149] usb 1-1.5: Product: TI CC2531 USB CDC
[  125.814154] usb 1-1.5: Manufacturer: Texas Instruments
[  125.814158] usb 1-1.5: SerialNumber: __0X00124B0014D9D9CD
[  125.816899] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[  126.385718] usb 1-1.5: USB disconnect, device number 23
[  132.822056] usb 1-1.4: new full-speed USB device number 24 using dwc_otg
[  132.969870] usb 1-1.4: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[  132.969881] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  132.969886] usb 1-1.4: Product: TI CC2531 USB CDC
[  132.969891] usb 1-1.4: Manufacturer: Texas Instruments
[  132.969896] usb 1-1.4: SerialNumber: __0X00124B0014D9D9CD
[  132.972168] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device

Hier hatte ich die DISCONNECTS gesehen und das Hochzählen der DEVICE NUMBER.
Ich habe dann die configuration.yaml so umgestellt dass der CC2531 per Serial eingebunden wird:

Code Auswählen


homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://localhost'
serial:
#  port: /dev/ttyACM0
  port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D9D9CD-if00
devices:
  '0x00158d0003cb832b':
    friendly_name: '0x00158d0003cb832b'
  '0x90fd9ffffedf660b':
    friendly_name: '0x90fd9ffffedf660b'
  '0x00158d00044e7aec':
    friendly_name: '0x00158d00044e7aec'
  '0x00158d00027ce0d2':
    friendly_name: '0x00158d00027ce0d2'
  '0x00158d00044cabe1':
    friendly_name: '0x00158d00044cabe1'
  '0x00158d0003501c21':
    friendly_name: '0x00158d0003501c21'
  '0x00158d0003f3ce06':
    friendly_name: '0x00158d0003f3ce06'
  '0x00158d0004458c88':
    friendly_name: '0x00158d0004458c88'
  '0x00158d00039dcbf6':
    friendly_name: '0x00158d00039dcbf6'
  '0x00158d0004038e3c':
    friendly_name: '0x00158d0004038e3c'
  '0x7cb03eaa0a0016c6':
    friendly_name: '0x7cb03eaa0a0016c6'
  '0x00158d00029b1013':
    friendly_name: '0x00158d00029b1013'
  '0x00158d0002ea2fd3':
    friendly_name: '0x00158d0002ea2fd3'
  '0xf0d1b800001350d6':
    friendly_name: '0xf0d1b800001350d6'

Dann einen Neustart. Das Ergebnis von

Code Auswählen

dmesg | grep -i usb sieht nun so aus:

Code Auswählen

[    0.071193] usbcore: registered new interface driver usbfs
[    0.071275] usbcore: registered new interface driver hub
[    0.071387] usbcore: registered new device driver usb
[    0.306285] usbcore: registered new interface driver lan78xx
[    0.308741] usbcore: registered new interface driver smsc95xx
[    0.341372] dwc_otg 3f980000.usb: base=(ptrval)
[    0.786164] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.788430] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.790755] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[    0.797747] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.802290] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.804708] usb usb1: Product: DWC OTG Controller
[    0.807078] usb usb1: Manufacturer: Linux 4.19.75-v7+ dwc_otg_hcd
[    0.809500] usb usb1: SerialNumber: 3f980000.usb
[    0.812466] hub 1-0:1.0: USB hub found
[    0.817830] usbcore: registered new interface driver usb-storage
[    0.849434] usbcore: registered new interface driver usbhid
[    0.852096] usbhid: USB HID core driver
[    1.241802] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.482096] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    1.487300] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.490814] hub 1-1:1.0: USB hub found
[    1.811807] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.942102] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    1.947576] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.045564] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:48:1a:64
[    2.151872] usb 1-1.4: new full-speed USB device number 4 using dwc_otg
[    2.300451] usb 1-1.4: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[    2.306653] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.309786] usb 1-1.4: Product: TI CC2531 USB CDC
[    2.312843] usb 1-1.4: Manufacturer: Texas Instruments
[    2.312854] usb 1-1.4: SerialNumber: __0X00124B0014D9D9CD
[    4.985600] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
[    4.987793] usbcore: registered new interface driver cdc_acm
[    4.987805] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    5.152749] usbcore: registered new interface driver brcmfmac

Und prompt konnte ich beide Steckdosen schalten...

Vielen, vielen Dank.

Beta-User · 13 Mai 2020, 17:30:11

Klingt gut

, Danke für die Rückmeldung

Bleibt die Frage, was da dazwischengepfuscht hat. Denn eigentlich hat sich nichts wesentliches geändert...

Kannst du mal deine fhem.cfg durchflözen und nachschauen, ob da auch was auf ttyACM0 zugreifen will? Eine alte, längst vergessene CUL-Definition, um mal was völlig willkürliches zu nennen

?

(und deaktiviere oder lösche bitte initialUsbCheck, falls noch nicht geschehen.)

sprudelverduenner · 13 Mai 2020, 17:42:18

Also in meiner fhem.cfg ist nichts mit ttyACM0 drin - ich hatte auch noch nie einen anderen USB-Stick am RasPi / FHEM dran.

Danke für den TIPP mit

Code Auswählen

attr initialUsbCheck disable 1

Habe ich noch ausgeführt.

Beta-User · 13 Mai 2020, 17:55:29

Gut.
Dann würde ich das jetzt an deiner Stelle noch ein, zwei Mal testen, dass es wirklich nach einem Neustart auch wieder tut, dann sollte tatsächlich gut sein?