RFXCOM win7/win10 OH2.1.0 problem connecting RFXTRX433 offline

Tags: #<Tag:0x00007f616dc78438> #<Tag:0x00007f616dc78320> #<Tag:0x00007f616dc78208>

I have installed new version of OH2.1.0 on an win10 machine with java 8u101
(I also have tried on WIN7 )
THe RFXtrx works with the RFXCOM manager software including fetching temperature data but not in openhab.

I have a problem in that I cannot get the RFXTRX433 receiver to work

Sometimes it does not show up in paper ui during discover - sometimes it does after delete.
I tried adding manually with COM7 .

both automatic and manual added have status OFFLINE

I tried to remove the FTDI driver package using powershell

first command
pnputil.exe -e
gives response
Published name : oem69.inf
Driver package provider : FTDI
Class : USB-styrenheter
Driver date and version : 08/16/2017 2.12.28.0
Signer name : Microsoft Windows Hardware Compatibility Publisher

Published name : oem70.inf
Driver package provider : FTDI
Class : Portar (COM och LPT)
Driver date and version : 08/16/2017 2.12.28.0
Signer name : Microsoft Windows Hardware Compatibility Publisher

so I try with commands
pnputil.exe -d oem69.inf
pnputil.exe -d oem70.inf
response is
Deleting the driver package failed : at least on unit is installed with the INF-file

I remove the RFXTRX433 and then I am able to delete oem69,inf but not oem.70inf
When I insert RFXtrx433 into USB it seems as drivers are installed again.

is there something I am missing?

some loginfo:

----------openhab.log
2017-10-06 17:27:50.605 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1WRPW4D’ using JD2XX.
2017-10-06 17:27:50.607 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
java.io.IOException: device not opened (3)
at jd2xx.JD2XX.openEx(Native Method)[182:org.openhab.binding.rfxcom:2.1.0]
at jd2xx.JD2XX.openBySerialNumber(JD2XX.java:806)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.internal.connector.RFXComJD2XXConnector.connect(RFXComJD2XXConnector.java:45)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:183)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.access$7(RFXComBridgeHandler.java:163)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler$1.run(RFXComBridgeHandler.java:156)[182:org.openhab.binding.rfxcom:2.1.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)[:1.8.0_101]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[:1.8.0_101]
at java.lang.Thread.run(Unknown Source)[:1.8.0_101]
2017-10-06 17:27:50.608 [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-10-06 17:28:15.507 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1WRPW4D’ using JD2XX.
2017-10-06 17:28:15.620 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error
2017-10-06 17:28:31.020 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘COM7’ using JD2XX.
2017-10-06 17:28:31.143 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed
java.io.IOException: device not found (2)
at jd2xx.JD2XX.openEx(Native Method)[182:org.openhab.binding.rfxcom:2.1.0]
at jd2xx.JD2XX.openBySerialNumber(JD2XX.java:806)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.internal.connector.RFXComJD2XXConnector.connect(RFXComJD2XXConnector.java:45)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:183)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler.access$7(RFXComBridgeHandler.java:163)[182:org.openhab.binding.rfxcom:2.1.0]
at org.openhab.binding.rfxcom.handler.RFXComBridgeHandler$1.run(RFXComBridgeHandler.java:156)[182:org.openhab.binding.rfxcom:2.1.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)[:1.8.0_101]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[:1.8.0_101]
at java.lang.Thread.run(Unknown Source)[:1.8.0_101]
2017-10-06 17:28:40.935 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘rfxcom:RFXtrx433:A1WRPW4D’ to inbox.
2017-10-06 17:29:01.965 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1WRPW4D’ using JD2XX.
2017-10-06 17:29:15.044 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1WRPW4D’ using JD2XX.
2017-10-06 17:30:15.161 [INFO ] [ernal.connector.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1WRPW4D’ using JD2XX.
2017-10-06 17:30:15.274 [ERROR] [g.rfxcom.handler.RFXComBridgeHandler] - Error occurred: io error

----------event.log
2017-10-06 17:29:01.958 [ThingAddedEvent ] - Thing ‘rfxcom:RFXtrx433:A1WRPW4D’ has been added.
2017-10-06 17:29:01.965 [hingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1WRPW4D’ changed from INITIALIZING to OFFLINE
2017-10-06 17:29:01.965 [hingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1WRPW4D’ changed from UNINITIALIZED to INITIALIZING
2017-10-06 17:29:15.044 [ThingUpdatedEvent ] - Thing ‘rfxcom:RFXtrx433:A1WRPW4D’ has been updated.
2017-10-06 17:30:15.473 [hingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1WRPW4D’ changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR)
2017-10-06 17:30:24.946 [hingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1WRPW4D’ changed from OFFLINE (COMMUNICATION_ERROR) to OFFLINE
2017-10-06 17:30:24.946 [ThingUpdatedEvent ] - Thing ‘rfxcom:RFXtrx433:A1WRPW4D’ has been updated.
2017-10-06 17:30:24.951 [ThingUpdatedEvent ] - Thing ‘rfxcom:RFXtrx433:A1WRPW4D’ has been updated.
2017-10-06 17:31:25.377 [hingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1WRPW4D’ changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR)
2017-10-06 17:32:31.979 [ExtensionEvent ] - Extension ‘ui-habmin’ has been installed.

One should not be tired when reading instructions.:roll_eyes:

Now I set up a manual RFXtrx433 device in PaperUI using the generic RFXCOM device named RFXCOM USB Transceiver.

as in manual…
To do that via the PaperUI, manually add the generic RFXCOM device named RFXCOM USB Transceiver, with the description “This is universal RFXCOM transceiver bridge for manual configuration purposes.”

before I wrongly tried using
"RFXtrx433E USB 433.92MHz Transceiver"

Now I do get automatic disovered temperature devices etc.

My manually created “RFXCOM USB Transceiver” is still listed status offline

and presently my openhab session (from .bat file shuts down al the time - but it is seeing things so improved

I will try to start over with new Openhab setup and see if some errors disappear

----------event log
2017-10-06 21:02:43.165 [ThingAddedEvent ] - Thing ‘rfxcom:bridge:6656a430’ has been added.
2017-10-06 21:02:48.262 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from UNINITIALIZED to INITIALIZING
2017-10-06 21:02:48.266 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from INITIALIZING to OFFLINE
2017-10-06 21:03:23.217 [InboxAddedEvent ] - Discovery Result with UID ‘rfxcom:humidity:6656a430:9728’ has been added.
2017-10-06 21:06:12.005 [ThingAddedEvent ] - Thing ‘rfxcom:bridge:6656a430’ has been added.
2017-10-06 21:06:17.957 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from UNINITIALIZED to INITIALIZING
2017-10-06 21:06:17.957 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from INITIALIZING to OFFLINE
2017-10-06 21:06:34.070 [InboxAddedEvent ] - Discovery Result with UID ‘rfxcom:temperature:6656a430:11264’ has been added.
2017-10-06 21:08:09.252 [ThingAddedEvent ] - Thing ‘rfxcom:bridge:6656a430’ has been added.
2017-10-06 21:08:14.301 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from INITIALIZING to OFFLINE
2017-10-06 21:08:14.301 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from UNINITIALIZED to INITIALIZING
2017-10-06 21:09:51.115 [ThingAddedEvent ] - Thing ‘rfxcom:bridge:6656a430’ has been added.
2017-10-06 21:09:56.853 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from UNINITIALIZED to INITIALIZING
2017-10-06 21:09:56.853 [hingStatusInfoChangedEvent] - ‘rfxcom:bridge:6656a430’ changed from INITIALIZING to OFFLINE

----------openhab.log
2017-10-06 21:09:51.936 [WARN ] [org.eclipse.jetty.server.HttpChannel] - Could not send response error 500: javax.servlet.ServletException: javax.servlet.ServletException: A MultiException has 1 exceptions. They are:

  1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_1,2,977834) has been shut down

I’m having the same problems. I’ve tried new install as well ( 2.3).

I believe the binding might have problems and wondering a new version is being worked on?