nanoCUL disconnected und unzuverlässig

Begonnen von linuxq, 08 Oktober 2017, 11:29:07

Vorheriges Thema - Nächstes Thema

linuxq

Hallo,

ich habe seit Monaten einen funktionierende nanoCUL mit MAX! Fensterkontakten und Thermostaten zuverlässig laufen. Diese Woche habe ich auf einem 2. Raspberry einen RaspberryMatic mit dem ELV-Bausatz und eine Hue-Bridge zusätzlich in Betrieb genommen.

Ich habe gestern festgestellt,  dass die Fensterkontakte nicht mehr zuverlässig funktionieren. Im Log erscheint regelmäßig die Info, dass der CUL868 disconnected ist. Was kann das Problem sein?

Zitat2017-10-08 11:28:18 CUL CUL868 DISCONNECTED
2017-10-08 11:28:18 CUL CUL868 cmds:  A B C E e F f G h i K k l M m R T t U V W X x Y Z z
2017-10-08 11:28:18 CUL CUL868 Initialized
2017-10-08 11:28:18 CUL CUL868 CONNECTED
2017-10-08 11:28:21 CUL CUL868 DISCONNECTED
2017-10-08 11:28:21 CUL CUL868 cmds:  A B C E e F f G h i K k l M m R T t U V W X x Y Z z
2017-10-08 11:28:21 CUL CUL868 Initialized
2017-10-08 11:28:21 CUL CUL868 CONNECTED



Zitatpi@raspberrypi3:/opt/fhem/log $ tail -f fhem-2017-10.log
2017.10.08 11:04:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:04:47 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:05:00 3: tado_temp: Read callback: Error: connect to https://my.tado.com:443 timed out
2017.10.08 11:05:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:05:47 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:06:02 3: MAX_18342d_weblink: space is not allowed in FileLog definition: 4:desiredTemperature:0:
2017.10.08 11:06:02 3: MAX_18342d_weblink: space is not allowed in FileLog definition: 4:temperature:0:
2017.10.08 11:06:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:06:47 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:07:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:07:47 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:08:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:08:47 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
2017.10.08 11:08:52 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 disconnected, waiting to reappear (CUL868)2017.10.08 11:08:52 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.08 11:08:52 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.08 11:08:52 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 reappeared (CUL868)
2017.10.08 11:08:58 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 disconnected, waiting to reappear (CUL868)2017.10.08 11:08:58 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.08 11:08:58 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.08 11:08:58 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 reappeared (CUL868)
2017.10.08 11:09:13 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 disconnected, waiting to reappear (CUL868)2017.10.08 11:09:13 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.08 11:09:13 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.08 11:09:13 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 reappeared (CUL868)
2017.10.08 11:09:17 3: CUL868_Reconnect: CUL868 version => V 1.67 nanoCUL868
Gesendet von meinem STH100-2 mit Tapatalk


linuxq

#1
ZitatCMDS

ABCEeFfGhiKklMmRTtUVWXxYZz

CUL868_MSGCNT

222

CUL868_TIME

2017-10-08 11:29:50

Clients

:CUL_MAX:HMS:CUL_IR:STACKABLE_CC:TSSTACKED:STACKABLE:

DEF

/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400 0000

DeviceName

/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400

FD

57

FHTID

0000

NAME

CUL868

NR

302

PARTIAL

RAWMSG

? (��V is unknown) Use one of A B C E e F f G h i K k l M m R T t U V W X x Y Z z

RSSI

-74

STATE

Initialized

TYPE

CUL

VERSION

V 1.67 nanoCUL868

initString

X21 Zr Za123456 Zw111111

Readings

ccconf

freq:868.300MHz bWidth:101KHz rAmpl:33dB sens:8dB

2017-10-08 09:33:51

cmds

A B C E e F f G h i K k l M m R T t U V W X x Y Z z

2017-10-08 11:29:53

credit10ms

900

2017-10-08 11:29:17

raw

is00000FF0FFF0

2017-10-08 11:19:05

state

Initialized

2017-10-08 11:29:53

uptime

0 06:55:12

2017-10-08 09:34:24

version

V 1.67 nanoCUL868



Gesendet von meinem STH100-2 mit Tapatalk


gloob

Hängt alles am gleichen Raspi oder an 2 getrennten? USB Hub? Netzteil stark genug?
Raspberry Pi 3 | miniCUL 433MHz | nanoCUL 868 MHz | nanoCUL 433 MHz | MySensors WLAN Gateway | LaCrosse WLAN Gateway | SignalESP 433 MHz | SignalESP 868 MHz | HM-MOD-UART WLAN Gateway | IR - 360 Grad WLAN Gateway

linuxq

Der Raspi3 hat ein Netzteil mit 1,9 A. Der nanoCUL UND der USB300 (Enocean) hängen an einem Usb-Hub, der mit einem 2A-Netzteil versorgt ist. Der Enocean-Stick disconnected auch ab und zu für nur eine Sekunde, läuft aber zuverlässig. Ich habe auch schon den Enocean-Stick entfernt und neu gebootet. Gleiches Problem bestand weiter.

Gesendet von meinem STH100-2 mit Tapatalk


viegener

Wenn beim hinzufügen eines "verbrauchers" am PI die vorhandenen Geräte instabil werden (disconnects) würde ich mit hoher Wahrscheinlichkeit auf Stromversorgungsprobleme tippen. Was passiert ohne den powered hub und ohne raspberrymatic?

Achso: Und verwende doch bitte auch code tags für log files etc (# button)
Kein Support über PM - Anfragen gerne im Forum - Damit auch andere profitieren und helfen können

KölnSolar

Das "Backpowering" Thema durch den aktiven USB-Hub  :-\

Mach doch mal dmesg, um zu bestatigen, dass die disconnects auf Rpi-Ebene stattfinden.(Nur so als Bestätigung, dass es kein FHEM-Problem ist, sondern definitiv ein Rpi-Thema).

Grüße Markus
RPi3/2 buster/stretch-SamsungAV_E/N-RFXTRX-IT-RSL-NC5462-Oregon-CUL433-GT-TMBBQ-01e-CUL868-FS20-EMGZ-1W(GPIO)-DS18B20-CO2-USBRS232-USBRS422-Betty_Boop-EchoDot-OBIS(Easymeter-Q3/EMH-KW8)-PCA301(S'duino)-Deebot(mqtt2)-zigbee2mqtt

linuxq

Raspberrymatic läuft auf einem 2. Raspberry. Das dürfte nicht das Problem sein. Ich hatte gestern nochmal alles mit CUL in der Konfig gelöscht und die Sticks mehrfach umgesteckt. Ich habe nun den EnOcean am USB-Hub und den nanoCUL am Raspberry. Nun scheinen keine Disconnects mehr zu kommen. Enocean läuft zuverlässig.

Der Status in FHEM sieht auch besser aus nun.

CUL868 Initialized

Internals
CMDS ABCEeFfGhiKklMmRTtUVWXxYZz
Clients :CUL_MAX:HMS:CUL_IR:STACKABLE_CC:TSSTACKED:STACKABLE:
DEF /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400 0000
DeviceName /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400
FD 46
FHTID 0000
NAME CUL868
NR 356
PARTIAL
STATE Initialized
TYPE CUL
VERSION V 1.67 nanoCUL868
initString X21 Zr Za123456 Zw111111

Readings
cmds A B C E e F f G h i K k l M m R T t U V W X x Y Z z 2017-10-09 21:09:11
credit10ms 150 2017-10-09 00:34:43
state Initialized 2017-10-09 21:09:11



Allerdings bekomme ich meine MAX Fensterkontakte und den Thermostat nicht mehr gepairt.

DMESG des heutigen Tages (Reboot vor ca. 15 Stunden):
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.35-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1014 SMP Fri Jun 30 14:47:43 BST 2017
[    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] cma: Reserved 8 MiB at 0x2e400000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 192512
[    0.000000] free_area_init_node: node 0, pgdat 80c6ee40, node_mem_map add64000
[    0.000000]   Normal zone: 1692 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 192512 pages, LIFO batch:31
[    0.000000] percpu: Embedded 14 pages/cpu @aefa7000 s25600 r8192 d23552 u57344
[    0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 190820
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=720 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait plymouth.enable=0
[    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: 741416K/770048K available (7168K kernel code, 484K rwdata, 2012K rodata, 1024K init, 778K bss, 20440K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xaf800000 - 0xff800000   (1280 MB)
    lowmem  : 0x80000000 - 0xaf000000   ( 752 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80800000   (8160 kB)
      .init : 0x80b00000 - 0x80c00000   (1024 kB)
      .data : 0x80c00000 - 0x80c79014   ( 485 kB)
       .bss : 0x80c7b000 - 0x80d3da64   ( 779 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] arm_arch_timer: Architected 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.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000025] Switching to timer-based delay loop, resolution 52ns
[    0.000334] Console: colour dummy device 80x30
[    0.001243] console [tty1] enabled
[    0.001291] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001361] pid_max: default: 32768 minimum: 301
[    0.001725] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001767] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002802] Disabling cpuset control group subsystem
[    0.002996] CPU: Testing write buffer coherency: ok
[    0.003064] ftrace: allocating 22390 entries in 66 pages
[    0.055819] CPU0: update cpu_capacity 1024
[    0.055887] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.055985] Setting up static identity map for 0x100000 - 0x100034
[    0.058215] CPU1: update cpu_capacity 1024
[    0.058222] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.058936] CPU2: update cpu_capacity 1024
[    0.058943] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.059608] CPU3: update cpu_capacity 1024
[    0.059614] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.059696] Brought up 4 CPUs
[    0.059868] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.059897] CPU: All CPU(s) started in HYP mode.
[    0.059923] CPU: Virtualization extensions available.
[    0.060716] devtmpfs: initialized
[    0.071869] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.072187] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.072249] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.072809] pinctrl core: initialized pinctrl subsystem
[    0.073729] NET: Registered protocol family 16
[    0.076057] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.084957] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.085006] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.085211] Serial: AMBA PL011 UART driver
[    0.087085] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.087631] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.156419] bcm2835-dma 3f007000.dma: DMA legacy API manager at af80f000, dmachans=0x1
[    0.158282] SCSI subsystem initialized
[    0.158464] usbcore: registered new interface driver usbfs
[    0.158566] usbcore: registered new interface driver hub
[    0.158681] usbcore: registered new device driver usb
[    0.165369] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
[    0.166851] clocksource: Switched to clocksource arch_sys_counter
[    0.213696] VFS: Disk quotas dquot_6.6.0
[    0.213808] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.214030] FS-Cache: Loaded
[    0.214300] CacheFiles: Loaded
[    0.226523] NET: Registered protocol family 2
[    0.227463] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.227601] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.227812] TCP: Hash tables configured (established 8192 bind 8192)
[    0.227925] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.227993] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.228225] NET: Registered protocol family 1
[    0.228656] RPC: Registered named UNIX socket transport module.
[    0.228689] RPC: Registered udp transport module.
[    0.228717] RPC: Registered tcp transport module.
[    0.228744] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.229754] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.232063] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.248218] FS-Cache: Netfs 'nfs' registered for caching
[    0.249216] NFS: Registering the id_resolver key type
[    0.249266] Key type id_resolver registered
[    0.249294] Key type id_legacy registered
[    0.251738] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.251885] io scheduler noop registered
[    0.251916] io scheduler deadline registered (default)
[    0.252242] io scheduler cfq registered
[    0.257896] BCM2708FB: allocated DMA memory ee510000
[    0.257949] BCM2708FB: allocated DMA channel 0 @ af80f000
[    0.284221] Console: switching to colour frame buffer device 160x45
[    0.300683] bcm2835-rng 3f104000.rng: hwrng registered
[    0.300935] vc-cma: Videocore CMA driver
[    0.301054] vc-cma: vc_cma_base      = 0x00000000
[    0.301190] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.301341] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.301696] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    0.317202] brd: module loaded
[    0.326180] loop: module loaded
[    0.326302] Loading iSCSI transport class v2.0-870.
[    0.327009] usbcore: registered new interface driver smsc95xx
[    0.331566] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.564132] Core Release: 2.80a
[    0.568588] Setting default values for core params
[    0.573115] Finished setting default values for core params
[    0.778057] Using Buffer DMA mode
[    0.782532] Periodic Transfer Interrupt Enhancement - disabled
[    0.787069] Multiprocessor Interrupt Enhancement - disabled
[    0.791578] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.796040] Dedicated Tx FIFOs mode
[    0.800801] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xae504000 dma = 0xee504000 len=9024
[    0.805466] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[    0.828571] dwc_otg: Microframe scheduler enabled
[    0.828621] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058ef90
[    0.833240] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058f300 length 36
[    0.837783] WARN::hcd_init_fiq:486: MPHI regs_base at 0xaf87a000
[    0.842318] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.846826] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.851425] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.856035] Init: Port Power? op_state=1
[    0.860529] Init: Power Port (0)
[    0.865094] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.869631] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.874187] usb usb1: Product: DWC OTG Controller
[    0.878743] usb usb1: Manufacturer: Linux 4.9.35-v7+ dwc_otg_hcd
[    0.883328] usb usb1: SerialNumber: 3f980000.usb
[    0.888779] hub 1-0:1.0: USB hub found
[    0.893334] hub 1-0:1.0: 1 port detected
[    0.898484] dwc_otg: FIQ enabled
[    0.898489] dwc_otg: NAK holdoff enabled
[    0.898493] dwc_otg: FIQ split-transaction FSM enabled
[    0.898508] Module dwc_common_port init
[    0.898745] usbcore: registered new interface driver usb-storage
[    0.903499] mousedev: PS/2 mouse device common for all mice
[    0.909092] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.914061] bcm2835-cpufreq: min=600000 max=1200000
[    0.919220] sdhci: Secure Digital Host Controller Interface driver
[    0.923962] sdhci: Copyright(c) Pierre Ossman
[    0.928874] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[    0.935830] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.940777] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.948221] ledtrig-cpu: registered to indicate activity on CPUs
[    0.953256] hidraw: raw HID events driver (C) Jiri Kosina
[    0.958329] usbcore: registered new interface driver usbhid
[    0.963181] usbhid: USB HID core driver
[    0.968810] vchiq: vchiq_init_state: slot_zero = 0xae580000, is_master = 0
[    0.975477] Initializing XFRM netlink socket
[    0.980399] NET: Registered protocol family 17
[    0.985345] Key type dns_resolver registered
[    0.990609] Registering SWP/SWPB emulation handler
[    0.996143] registered taskstats version 1
[    1.001195] vc-sm: Videocore shared memory driver
[    1.005795] [vc_sm_connected_init]: start
[    1.058185] [vc_sm_connected_init]: end - returning 0
[    1.068768] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    1.075182] sdhost: log_buf @ ae507000 (ee507000)
[    1.116977] Indeed it is in host mode hprt0 = 00021501
[    1.206882] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.209276] random: fast init done
[    1.218690] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.223538] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.286947] of_cfs_init
[    1.291762] of_cfs_init: OK
[    1.297421] Waiting for root device /dev/mmcblk0p2...
[    1.315422] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.320213] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.325130] Indeed it is in host mode hprt0 = 00001101
[    1.390923] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.397238] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.404714] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.427444] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.435656] mmc0: new high speed SDHC card at address aaaa
[    1.441152] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
[    1.451131]  mmcblk0: p1 p2
[    1.522152] mmc1: new high speed SDIO card at address 0001
[    1.555264] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.557241] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.557250] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.558040] hub 1-1:1.0: USB hub found
[    1.558132] hub 1-1:1.0: 5 ports detected
[    1.579016] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.587093] devtmpfs: mounted
[    1.593492] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[    1.867326] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    1.872803] systemd[1]: Detected architecture 'arm'.
[    1.876915] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.007237] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.012455] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.018268] NET: Registered protocol family 10
[    2.023759] smsc95xx v1.0.5
[    2.024977] systemd[1]: Inserted module 'ipv6'
[    2.029330] systemd[1]: Set hostname to <raspberrypi3>.
[    2.130574] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:0a:49:8b
[    2.226909] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[    2.357408] usb 1-1.3: New USB device found, idVendor=1a40, idProduct=0101
[    2.362814] usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.368179] usb 1-1.3: Product: USB 2.0 Hub
[    2.374344] hub 1-1.3:1.0: USB hub found
[    2.379851] hub 1-1.3:1.0: 4 ports detected
[    2.476918] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
[    2.540566] systemd[1]: Cannot add dependency job for unit regenerate_ssh_host_keys.service, ignoring: Unit regenerate_ssh_host_keys.service failed to load: No such file or directory.
[    2.552875] systemd[1]: Found ordering cycle on basic.target/start
[    2.558736] systemd[1]: Found dependency on paths.target/start
[    2.564494] systemd[1]: Found dependency on cups.path/start
[    2.570297] systemd[1]: Found dependency on sysinit.target/start
[    2.576131] systemd[1]: Found dependency on kbd.service/start
[    2.634454] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001
[    2.634464] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.634471] usb 1-1.5: Product: FT232R USB UART
[    2.634477] usb 1-1.5: Manufacturer: FTDI
[    2.634483] usb 1-1.5: SerialNumber: A9M9DV3R
[    2.706905] usb 1-1.3.3: new low-speed USB device number 6 using dwc_otg
[    2.848287] usb 1-1.3.3: New USB device found, idVendor=4555, idProduct=1031
[    2.853020] usb 1-1.3.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.866973] input: HID 4555:1031 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/0003:4555:1031.0001/input/input0
[    2.894933] fuse init (API version 7.26)
[    2.940636] i2c /dev entries driver
[    2.942376] hid-generic 0003:4555:1031.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 4555:1031] on usb-3f980000.usb-1.3.3/input0
[    2.961830] input: HID 4555:1031 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.1/0003:4555:1031.0002/input/input1
[    3.037496] hid-generic 0003:4555:1031.0002: input,hidraw1: USB HID v1.10 Mouse [HID 4555:1031] on usb-3f980000.usb-1.3.3/input1
[    3.136924] usb 1-1.3.4: new full-speed USB device number 7 using dwc_otg
[    3.297361] usb 1-1.3.4: New USB device found, idVendor=0403, idProduct=6001
[    3.297375] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.297383] usb 1-1.3.4: Product: EnOcean USB 300 DB
[    3.297391] usb 1-1.3.4: Manufacturer: EnOcean GmbH
[    3.297398] usb 1-1.3.4: SerialNumber: FT1M2JS3
[    3.447546] systemd-udevd[158]: starting version 215
[    4.169239] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.193610] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    4.985223] ip_tables: (C) 2000-2006 Netfilter Core Team
[    5.017600] nf_conntrack version 0.5.0 (12288 buckets, 49152 max)
[    5.080222] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    5.541648] usbcore: registered new interface driver usbserial
[    5.541742] usbcore: registered new interface driver usbserial_generic
[    5.541818] usbserial: USB Serial support registered for generic
[    5.554697] usbcore: registered new interface driver ftdi_sio
[    5.554802] usbserial: USB Serial support registered for FTDI USB Serial Device
[    5.555181] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[    5.556283] usb 1-1.5: Detected FT232RL
[    5.557226] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0
[    5.557517] ftdi_sio 1-1.3.4:1.0: FTDI USB Serial Device converter detected
[    5.557694] usb 1-1.3.4: Detected FT232RL
[    5.558626] usb 1-1.3.4: FTDI USB Serial Device converter now attached to ttyUSB1
[    6.110809] uart-pl011 3f201000.serial: no DMA platform data
[    7.329426] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    8.204472] random: crng init done
[    8.750924] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
[    9.895808] warning: process `colord-sane' used the deprecated sysctl system call with
[    9.895821] 8.
[    9.895827] 1.
[    9.895830] 2.

[   10.585286] Bluetooth: Core ver 2.22
[   10.585356] NET: Registered protocol family 31
[   10.585361] Bluetooth: HCI device and connection manager initialized
[   10.585381] Bluetooth: HCI socket layer initialized
[   10.585396] Bluetooth: L2CAP socket layer initialized
[   10.585428] Bluetooth: SCO socket layer initialized
[   10.597066] Bluetooth: HCI UART driver ver 2.3
[   10.597077] Bluetooth: HCI UART protocol H4 registered
[   10.597083] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   10.597255] Bluetooth: HCI UART protocol Broadcom registered
[   10.774163] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.774175] Bluetooth: BNEP filters: protocol multicast
[   10.774196] Bluetooth: BNEP socket layer initialized
[   15.203772] systemd-journald[155]: Received request to flush runtime journal from PID 1
[   15.552545] Adding 102396k swap on /var/swap.  Priority:-1 extents:4 across:167932k SSFS
[   40.365702] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[  119.130324] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[38202.888943] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[38214.849219] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[51960.306754] usb 1-1.5: USB disconnect, device number 5
[51960.307055] ftdi_sio ttyUSB0: error from flowcontrol urb
[51960.307389] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[51960.307428] ftdi_sio 1-1.5:1.0: device disconnected
[51964.692994] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
[51964.850627] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001
[51964.850643] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[51964.850651] usb 1-1.5: Product: FT232R USB UART
[51964.850658] usb 1-1.5: Manufacturer: FTDI
[51964.850666] usb 1-1.5: SerialNumber: A9M9DV3R
[51964.860074] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[51964.860259] usb 1-1.5: Detected FT232RL
[51964.861348] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0
[51992.275362] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[51993.677872] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32


Bei [51960.306754]  kam es zum disconnect, als ich heute Abend den CUL mal abgezogen habe. Was bedeutet das:
ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

less /opt/fhem/log/fhem-2017-10.log | grep CUL
pi@raspberrypi3:~ $ less /opt/fhem/log/fhem-2017-10.log | grep CUL
2017.10.09 06:43:31 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0
2017.10.09 06:43:31 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.09 06:43:34 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.09 06:43:34 3: CUL868 device opened
2017.10.09 06:43:34 2: Switched CUL868 rfmode to MAX
2017.10.09 06:43:34 3: CUL_MAX_Check: Detected firmware version 167 of the CUL-compatible IODev
2017.10.09 06:43:56 3: Probing CUL device /dev/ttyAMA0
2017.10.09 17:18:10 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0
2017.10.09 17:18:10 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.09 17:18:13 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.09 17:18:13 3: CUL868 device opened
2017.10.09 17:18:13 2: Switched CUL868 rfmode to MAX
2017.10.09 17:18:13 3: CUL_MAX_Check: Detected firmware version 167 of the CUL-compatible IODev
2017.10.09 17:18:37 3: Probing CUL device /dev/ttyAMA0
2017.10.09 21:08:57 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 disconnected, waiting to reappear (CUL868)
2017.10.09 21:09:07 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.10.09 21:09:11 3: CUL868: Possible commands: ABCEeFfGhiKklMmRTtUVWXxYZz
2017.10.09 21:09:11 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 reappeared (CUL868)


connormcl

Ich hatte das auch ab und zu und per google nicht wirklich was gefunden zu urb -32...

Nachdem ich folgendes verwendet habe, war es weg:

- Bessere nanos
- USB-Kabel gekürzt
- Raspberry Pi 3 Netzteil mit 2,5A
- Powered USB-Hub mit 3,5A Netzteil

Das mit den besseren nanos ist übrigens nicht zu vernachlässigen:
Du verwendest billigst China-Clone, zu erkennen an der gefakten FTDI Seriennr. A9M9DV3R. Da gibt es deutlich bessere Clones mit echtem FTDI-Chip und insgesamt besserer Fertigungsqualität...


linuxq

Die Geräte sind wieder gepairt, aber die Abbrüche auch wieder da :( Thermostat geht zu bedienen, aber die Kontakte gehen fast nie. Ich habe auch schon USB-Kabel getauscht und alles andere am USB entfernt. Bei jedem Befehl, den ich an den Thermostaten sende kommt ein disconnect.

Welches sind denn bessere nanos? Ich hatte es im Amazon-Marketplace gekauft. Mit Antenne, ...  :'( Bisher lief es fehlerfrei. Könnte kotzen.

Ich habe nur 1 Thermostat und 2 Kontakte. Da überlege ich, ob ich vielleicht dann doch auf Home-Matic wechsle. Aber die Komponenten sind erheblich teurer.

connormcl

Habe gute Erfahrungen mit nanos von Eckstein Komponente...auf ebay oder deren Homepage für ca. 7 EUR...die haben nen original FTDI und sind gut verarbeitet...

Dazu müsstest du aber den bisherigen nano herunterlöten und den neuen drauf...und dann das ganze mit passender culfw flashen...

schnitzelbrain

Hallo,
Ich hatte vor einem Jahr mit dem selbstgebauten nanoCUL und raspi 2b das gleiche Problem. Usb kabel, Netzteile, hubs, cul umlöten, abschirmen alles getestet.

Die cul chip sind China Ware.

Wochenlang gefrickelt und immer wieder disconnect der max Fenster Sensoren.
Am Ende hatte ich mein fhem Projekt eingestellt.

Jetzt hab ich mich nochmal ran getraut.

1. Richtige nanoCUL Platinen benutzt statt eigener Verkabelung.
2. Fhem auf der synology unter chroot statt raspi.
3. Seit 2 Monaten der cul mit max sensor ohne Ausfall am laufen.

Jetzt würde ich gerne auf eine extra Hardware (raspi, bananapi, oder???) umziehen aber befürchte die gleichen Probleme wie vorher.
Zumal die syno gefühlt wesentlich flotter als die raspi ist.

Ich denke es ist ein raspi Problem.
Wenn du die Möglichkeit hast teste doch mal an einem pc unter linux oder generell andere hardware.

Wenn jemand von euch einen Tipp hat was sich so problemlos und gut supported wie die raspi einrichten lässt aber die leidigen usb Probleme nicht hat, dann gebt doch bitte mal Bescheid.


Gesendet von meinem SM-G930F mit Tapatalk


KölnSolar

ZitatDie Geräte sind wieder gepairt, aber die Abbrüche auch wieder da

ZitatWochenlang gefrickelt und immer wieder disconnect der max Fenster Sensoren.

beide m. mode=MAX Zufall ? Oder Zusammenhang max + FTDI-Clone + (Rpi) ?
RPi3/2 buster/stretch-SamsungAV_E/N-RFXTRX-IT-RSL-NC5462-Oregon-CUL433-GT-TMBBQ-01e-CUL868-FS20-EMGZ-1W(GPIO)-DS18B20-CO2-USBRS232-USBRS422-Betty_Boop-EchoDot-OBIS(Easymeter-Q3/EMH-KW8)-PCA301(S'duino)-Deebot(mqtt2)-zigbee2mqtt

schnitzelbrain

Zitat von: KölnSolar am 10 Oktober 2017, 07:54:39
beide m. mode=MAX Zufall ? Oder Zusammenhang max + FTDI-Clone + (Rpi) ?
Max kann ich ausschließen da die gleichen Sensoren jetzt seit Wochen ihren Dienst tun. FTDI clone auch nicht die Chips selbst da dies jetzt auch die gleichen sind.

Bleibt meines Erachtens nur fehleranfälliger cul aufbau auf raster Platine (mehrere Versionen gelötet und gesteckte Aufbauten ) oder Raspi.


Gesendet von meinem SM-G930F mit Tapatalk


linuxq

Ich habe den fertigen nanoCUL mit Antenne im Mai per Ebay gekauft und es lief bis jetzt ohne Probleme. Umlöten auf einen anderen nano ist frikelig und ich weiß nicht, ob dann alles wieder auftaucht.

Läuft der Busware CUL erfahrungsgemäß stabiler?

Gesendet von meinem STH100-2 mit Tapatalk


gloob

#14
Kannst du vielleicht mal ein Bild von dem CUL zeigen? Grüne Platine mit Schrumpfschlauch?

Es gab hier schön öfter Probleme mit CULs von eBay.
Raspberry Pi 3 | miniCUL 433MHz | nanoCUL 868 MHz | nanoCUL 433 MHz | MySensors WLAN Gateway | LaCrosse WLAN Gateway | SignalESP 433 MHz | SignalESP 868 MHz | HM-MOD-UART WLAN Gateway | IR - 360 Grad WLAN Gateway