I have installed the latest snapshot now.
Things have not changed.
==> /var/log/openhab2/events.log <==
2016-12-16 15:51:49.795 [ThingUpdatedEvent ] - Thing 'rfxcom:bridge:2ae6 286c' has been updated.
2016-12-16 15:51:50.169 [hingStatusInfoChangedEvent] - 'rfxcom:bridge:2ae6286c' changed from OFFLINE to ONLINE
==> /var/log/openhab2/openhab.log <==
2016-12-16 15:52:39.393 [ERROR] [rnal.discovery.RFXComBridgeDiscovery] - Error o ccured during discovery
java.io.IOException: device not found (2)
at jd2xx.JD2XX.listDevices(Native Method)
at jd2xx.JD2XX.listDevicesByDescription(JD2XX.java:826)
at org.openhab.binding.rfxcom.internal.discovery.RFXComBridgeDiscovery.d iscoverRfxcom(RFXComBridgeDiscovery.java:90)
at org.openhab.binding.rfxcom.internal.discovery.RFXComBridgeDiscovery.s tartScan(RFXComBridgeDiscovery.java:67)
at org.eclipse.smarthome.config.discovery.AbstractDiscoveryService.start Scan(AbstractDiscoveryService.java:199)
at org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegis tryImpl.startScan(DiscoveryServiceRegistryImpl.java:381)
at org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegis tryImpl.startScans(DiscoveryServiceRegistryImpl.java:357)
What I don’t understand is why, with an explicit installation of the binding for “RFXCOM USB Transceiver” with a serial port, instead of the generic JD2xx version “RFXtrx433E USB 433.92MHz Transceiver”, it still tries to use JD2xx for a new thing discovery.
RFXComBridgeHandler.java explicitely has a connection method for serial port -not using jd2xx-:
private void connect() {
logger.debug("Connecting to RFXCOM transceiver");
try {
if (configuration.serialPort != null) {
if (connector == null) {
connector = new RFXComSerialConnector();
}
} else if (configuration.bridgeId != null) {
if (connector == null) {
connector = new RFXComJD2XXConnector();
}
} else if (configuration.host != null) {
if (connector == null) {
connector = new RFXComTcpConnector();
}