[SOLVED] RFXCOM not working since OH 2.1 upgrade

Hi guys, my RFXCOM is no longer working with OH2.1 since the upgrade a few days ago. was working fine before, have tried removing.adding the binding…no luck…

I have upgraded the firmware to the latest version 1020. device is a 433e

Here are the entries from the log file

2017-09-17 10:33:12.638 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-09-17 10:33:12.654 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-09-17 10:33:12.654 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-09-17 10:33:12.755 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-09-17 10:33:12.956 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-09-17 10:33:12.957 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped
2017-09-17 10:34:12.533 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-09-17 10:34:12.533 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-09-17 10:34:12.533 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-09-17 10:34:12.533 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Interrupt serial listener
2017-09-17 10:34:12.533 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial out stream
2017-09-17 10:34:12.533 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial in stream
2017-09-17 10:34:12.533 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial port
2017-09-17 10:34:12.644 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-09-17 10:34:12.644 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-09-17 10:34:12.659 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-09-17 10:34:12.659 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-09-17 10:34:12.760 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-09-17 10:34:12.960 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-09-17 10:34:12.961 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped

Cheers
Colin

Have you tried rebooting the whole machine?

If the reboot didn’t work…

I had some issues with read errors on a remote rfxcom (ser2net). Using the 2.2 binding solved my problems

cheers

Han

Can you check via the the karat console what binding version you have running. From what version did you upgrade? What hardware are you running on? Where you using j2dxx connection before as well?

Reboot didnt fix the problem.

I’m using the 2.1 online version of OH2.1 and of the binding.

I think i was using the 2.0 online version previously.

What command do i use to get the binding version info from Karaf please?

I’m running a Windows 10 server.

I was using j2dxx on my previous version - which i am again running and RFXCOM works OK again.

Where can i download RFXCOM 2.2 please?

Cheers

Colin

bundle:list | grep -i rfxcom

Should do the job

Is this literal, I can not easily find it back in the current code, but I can find back a I/O error.

Where can i download RFXCOM 2.2 please?

http://docs.openhab.org/installation/index.html

this problem ‘went away’ some time ago.

i now find myself wanting a fresh install of OH2 and the problem is back again :frowning:

here’s my debug log:
2017-11-03 13:24:23.435 [DEBUG] [org.openhab.binding.rfxcom ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=315, service.bundleid=186, service.scope=singleton} - org.openhab.binding.rfxcom
2017-11-03 13:24:23.446 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Initializing RFXCOM bridge handler
2017-11-03 13:24:23.448 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 13:24:23.448 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 13:24:23.448 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 13:24:23.448 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 13:24:23.449 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 13:24:23.460 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-11-03 13:24:23.460 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-11-03 13:24:23.562 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped
2017-11-03 13:24:23.761 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-11-03 13:25:18.232 [DEBUG] [org.openhab.binding.rfxcom ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=316, service.bundleid=186, service.scope=singleton} - org.openhab.binding.rfxcom
2017-11-03 13:25:18.248 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Initializing RFXCOM bridge handler
2017-11-03 13:25:18.249 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 13:25:18.249 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 13:25:18.249 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 13:25:18.249 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 13:25:18.249 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 13:25:18.251 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
java.io.IOException: device not opened (3)
at jd2xx.JD2XX.openEx(Native Method)[186:org.openhab.binding.rfxcom:2.1.0]
at jd2xx.JD2XX.openBySerialNumber(JD2XX.java:806)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.internal.connector.RFXComJD2XXConnector.connect(RFXComJD2XXConnector.java:45)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:183)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.access$7(RFXComBridgeHandler.java:163)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler$1.run(RFXComBridgeHandler.java:156)[186:org.openhab.binding.rfxcom:2.1.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
2017-11-03 13:25:18.253 [INFO ] [g.rfxcom.handler.RFXComBridgeHandler] - Automatically Discovered RFXCOM bridges use FTDI chip driver (D2XX). Reason for this error normally is related to operating system native FTDI drivers, which prevent D2XX driver to open device. To solve this problem, uninstall OS FTDI native drivers or add manually universal bridge ‘RFXCOM USB Transceiver’, which use normal serial port driver rather than D2XX.
2017-11-03 13:25:18.520 [DEBUG] [rnal.discovery.RFXComBridgeDiscovery] - Start discovery scan for RFXCOM transceivers
2017-11-03 13:25:18.520 [DEBUG] [rnal.discovery.RFXComBridgeDiscovery] - Discovering RFXCOM transceiver devices by JD2XX version 197138
2017-11-03 13:25:18.521 [DEBUG] [rnal.discovery.RFXComBridgeDiscovery] - Discovered 1 FTDI device(s)
2017-11-03 13:25:18.522 [DEBUG] [rnal.discovery.RFXComBridgeDiscovery] - Discovery done
2017-11-03 13:25:23.449 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 13:25:23.449 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 13:25:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 13:25:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Interrupt serial listener
2017-11-03 13:25:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial out stream
2017-11-03 13:25:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial in stream
2017-11-03 13:25:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial port
2017-11-03 13:25:23.556 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 13:25:23.556 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 13:25:23.572 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-11-03 13:25:23.572 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-11-03 13:25:23.673 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-11-03 13:25:23.873 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-11-03 13:25:23.874 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped
2017-11-03 13:26:18.250 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 13:26:18.250 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 13:26:18.250 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 13:26:18.250 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial port
2017-11-03 13:26:18.251 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 13:26:18.251 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 13:26:18.252 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
java.io.IOException: device not opened (3)
at jd2xx.JD2XX.openEx(Native Method)[186:org.openhab.binding.rfxcom:2.1.0]
at jd2xx.JD2XX.openBySerialNumber(JD2XX.java:806)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.internal.connector.RFXComJD2XXConnector.connect(RFXComJD2XXConnector.java:45)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:183)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.access$7(RFXComBridgeHandler.java:163)[186:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler$1.run(RFXComBridgeHandler.java:156)[186:org.openhab.binding.rfxcom:2.1.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
2017-11-03 13:26:18.253 [INFO ] [g.rfxcom.handler.RFXComBridgeHandler] - Automatically Discovered RFXCOM bridges use FTDI chip driver (D2XX). Reason for this error normally is related to operating system native FTDI drivers, which prevent D2XX driver to open device. To solve this problem, uninstall OS FTDI native drivers or add manually universal bridge ‘RFXCOM USB Transceiver’, which use normal serial port driver rather than D2XX.
2017-11-03 13:26:23.449 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 13:26:23.449 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 13:26:23.449 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 13:26:23.450 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Interrupt serial listener
2017-11-03 13:26:23.450 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial out stream
2017-11-03 13:26:23.450 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial in stream
2017-11-03 13:26:23.450 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial port
2017-11-03 13:26:23.562 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 13:26:23.562 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 13:26:23.578 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-11-03 13:26:23.579 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-11-03 13:26:23.679 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-11-03 13:26:23.880 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-11-03 13:26:23.882 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped

im running windows 10. my old installation still has functioning RFXCOM, but the fresh install doesnt.

ive tried adding both the auto-discovered thing as well as adding it manually. i cant get either to work

TIA

Colin

Did you try what binding proposes?

I havent uninstalled te FTDI drivers, I was thinking this wasnt the problem as i have 2 parallel OH2.1 installs, one works fine, one does not. these are both on the same windows 10 machine.

I have tried adding the the birgde manually, but get the same results
Colin

If you get the same errors related to JD2XX, you have added wrong bridge.

:frowning: now my installation that had a working rfx bridge has stopped working with the same error. i didn’t make any config changes. just stopped working. time to look at removing ftdi

Could you paste the log here?

Thanks Pauli

2017-11-03 19:20:40.369 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped
2017-11-03 19:21:39.949 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 19:21:39.949 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 19:21:39.949 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Disconnecting
2017-11-03 19:21:39.949 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Interrupt serial listener
2017-11-03 19:21:39.950 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial out stream
2017-11-03 19:21:39.950 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial in stream
2017-11-03 19:21:39.950 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Close serial port
2017-11-03 19:21:40.056 [DEBUG] [ernal.connector.RFXComJD2XXConnector] - Closed
2017-11-03 19:21:40.056 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1YHQTKH’ using JD2XX.
2017-11-03 19:21:40.071 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Reset controller
2017-11-03 19:21:40.071 [TRACE] [ernal.connector.RFXComJD2XXConnector] - Send data (len=14): 0D00000000000000000000000000
2017-11-03 19:21:40.072 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener started
2017-11-03 19:21:40.173 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-11-03 19:21:40.373 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Get status of controller
2017-11-03 19:21:40.373 [TRACE] [ernal.connector.RFXComJD2XXConnector] - Send data (len=14): 0D00000102000000000000000000
2017-11-03 19:21:40.374 [DEBUG] [nternal.connector.RFXComStreamReader] - Data listener stopped

You still using JD2XX driver based bridge not universal ‘RFXCOM USB Transceiver’ bridge.

Ah yes, corrected.

2017-11-03 20:01:09.099 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2017-11-03 20:01:09.099 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Connecting to RFXCOM transceiver
2017-11-03 20:01:09.099 [DEBUG] [rnal.connector.RFXComSerialConnector] - Disconnecting
2017-11-03 20:01:09.099 [DEBUG] [rnal.connector.RFXComSerialConnector] - Closed
2017-11-03 20:01:09.102 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
gnu.io.PortInUseException: Unknown Application
at gnu.io.CommPortIdentifier.open(CommPortIdentifier.java:475)[184:com.neuronrobotics.nrjavaserial:3.12.0.OH]
at org.openhab.binding.rfxcom.internal.connector.RFXComSerialConnector.connect(RFXComSerialConnector.java:51)[216:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:183)[216:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.access$7(RFXComBridgeHandler.java:163)[216:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler$1.run(RFXComBridgeHandler.java:156)[216:org.openhab.binding.rfxcom:2.1.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]

It seems that port is in use. There is no full log, so I could not find your serial port configuration and operating system?

Pauli my original config is working again now. After i swapped the bridge as you advised it OH started to get back to normal. I will check my new installation over the next few days to see if i can figure out whats going wrong with that.

I dont understand why i needed to change the RFXCOM bridge though, as i hadn’t been making any changes to my original install, i’d only been making changes to the new install. so really not sure what went wrong or why your suggestion works. I’m very glad it does work of course, so thank you very much for your help.
Colin.