Good morning,
I changed raspeberry and went to openhab version 5.14
my rfxcom does not connect:
19:29:24.165 [INFO ] [del.core.internal.ModelRepositoryImpl] - Loading DSL model ‘rfxtrx.things’
19:29:24.259 [ERROR] [.internal.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
org.openhab.binding.rfxcom.internal.exceptions.RFXComException: No serial port /dev/ttyUSB0
at org.openhab.binding.rfxcom.internal.connector.RFXComSerialConnector.connect(RFXComSerialConnector.java:60) ~[?:?]
at org.openhab.binding.rfxcom.internal.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:211) ~[?:?]
at org.openhab.binding.rfxcom.internal.handler.RFXComBridgeHandler.lambda$0(RFXComBridgeHandler.java:184) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]
19:29:24.259 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing ‘rfxcom:bridge:usb0’ changed from INITIALIZING to OFFLINE
19:29:24.262 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing ‘rfxcom:bridge:usb0’ changed from UNINITIALIZED to INITIALIZING
if I use:
root@Raspberry:~# udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci->
KERNEL==“ttyUSB0”
SUBSYSTEM==“tty”
DRIVER==“”
ATTR{power/control}==“auto”
ATTR{power/runtime_active_time}==“0”
ATTR{power/runtime_status}==“unsupported”
ATTR{power/runtime_suspended_time}==“0”
looking at parent device '/devices/platform/axi/1000120000.pcie/1f00300000.us>
KERNELS==“ttyUSB0”
SUBSYSTEMS==“usb-serial”
DRIVERS==“ftdi_sio”
ATTRS{event_char}==“(not readable)”
ATTRS{latency_timer}==“16”
ATTRS{port_number}==“0”
lines 1-23…skipping…
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci->
KERNEL==“ttyUSB0”
SUBSYSTEM==“tty”
DRIVER==“”
ATTR{power/control}==“auto”
ATTR{power/runtime_active_time}==“0”
ATTR{power/runtime_status}==“unsupported”
ATTR{power/runtime_suspended_time}==“0”
looking at parent device '/devices/platform/axi/1000120000.pcie/1f00300000.us>
KERNELS==“ttyUSB0”
SUBSYSTEMS==“usb-serial”
DRIVERS==“ftdi_sio”
ATTRS{event_char}==“(not readable)”
ATTRS{latency_timer}==“16”
ATTRS{port_number}==“0”
ATTRS{power/control}==“auto”
ATTRS{power/runtime_active_time}==“0”
ATTRS{power/runtime_status}==“unsupported”
ATTRS{power/runtime_suspended_time}==“0”
looking at parent device '/devices/platform/axi/1000120000.pcie/1f00300000.us>
KERNELS==“3-2:1.0”
SUBSYSTEMS==“usb”
DRIVERS==“ftdi_sio”
ATTRS{authorized}==“1”
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}==“ff”
ATTRS{bInterfaceNumber}==“00”
ATTRS{bInterfaceProtocol}==“ff”
ATTRS{bInterfaceSubClass}==“ff”
ATTRS{bNumEndpoints}==“02”
ATTRS{interface}==“RFXtrx433”
ATTRS{supports_autosuspend}==“1”
The Raspberry Pi correctly sees the RFXCOM.
Thank you for your help.
Arnaud
