RFXCOM 2.0 binding

klex · November 22, 2015, 5:09pm

Hi,

just discovered there is an initial RFXCOM 2.0 binding for OH2. This is great. Before I was running OH2 with the binding from 1.8.
I updated my config immediately to build 20151122 and with the PaperUI it discovered my RFXtrx433E USB 433.92MHz Transceiver.
So far so good, but it remains offline and earlier items that I coupled via the older binding don’t seem to work anymore.
Should I remove some settings from the older binding?

Thanks for the progress on this binding, it is promising!

klex · November 24, 2015, 6:22pm

any ideas anyone?
The status keeps saying offline and the log says “Connection to RFXCOM transceiver failed”
I’m now reverting to an earlier build to keep things running.

pauli_anttila · November 25, 2015, 4:23pm

Hi Alex,

which OS are you using? Could you enable debug logs for rfxcom and post log here?

-Pali

klex · November 25, 2015, 6:31pm

Hi Pauli,

thanks for your feedback and the hard work you put in to the binding.

I’m running openHAB 2 on a Raspberry Pi B 2 with a Raspbian OS.
To make I sure there were no loose ends I updated the FW of the Raspberry and updated Raspbian to the latest version.
I also did a clean install of the nightly build from last night and put only the new RFXCOM binding in the addons folder.
No change to start.sh was made nor a rfxcom.cfg file was created.

Below you see the log after I initiated a manual discovery on the RFXCOM binding.

2015-11-25 19:22:49 [DEBUG] [i.DiscoveryServiceRegistryImpl:333 ] - Triggering scan for thing types ‘[rfxcom:RFXtrx433, rfxcom:RFXtrx315, rfxcom:RFXrec433]’ on ‘RFXComBridgeDiscovery’…
2015-11-25 19:22:49 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:67 ] - Start discovery scan for RFXCOM transceivers
/jni/linux/arm-hf/libjd2xx.so
2015-11-25 19:22:49 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:91 ] - Discovering RFXCOM transceiver devices by JD2XX version 66055
2015-11-25 19:22:49 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:98 ] - Discovered 1 FTDI device(s)
2015-11-25 19:22:49 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:145 ] - Discovered RFXCOM transceiver, bridgeType=‘rfxcom:RFXtrx433’, bridgeId=‘A1XR580Z’
2015-11-25 19:22:49 [INFO ] [s.c.d.internal.PersistentInbox:125 ] - Added new thing ‘rfxcom:RFXtrx433:A1XR580Z’ to inbox.
2015-11-25 19:22:49 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:122 ] - Discovery done
2015-11-25 19:22:49 [DEBUG] [.core.common.ThreadPoolManager:171 ] - Created thread pool ‘safeCall’ with size 3-10
2015-11-25 19:22:49 [INFO ] [marthome.event.InboxAddedEvent:43 ] - Discovery Result with UID ‘rfxcom:RFXtrx433:A1XR580Z’ has been added.
2015-11-25 19:22:58 [DEBUG] [s.c.d.internal.PersistentInbox:253 ] - Discovery result removed from inbox, because it was added as a Thing to the ThingRegistry.
2015-11-25 19:22:58 [INFO ] [rthome.event.InboxRemovedEvent:43 ] - Discovery Result with UID ‘rfxcom:RFXtrx433:A1XR580Z’ has been removed.
2015-11-25 19:22:58 [INFO ] [marthome.event.ThingAddedEvent:43 ] - Thing ‘rfxcom:RFXtrx433:A1XR580Z’ has been added.
2015-11-25 19:22:58 [DEBUG] [.c.thing.internal.ThingManager:370 ] - Thing ‘rfxcom:RFXtrx433:A1XR580Z’ is tracked by ThingManager.
2015-11-25 19:22:58 [DEBUG] [.c.thing.internal.ThingManager:494 ] - Calling registerHandler handler for thing ‘rfxcom:RFXtrx433:A1XR580Z’ at ‘org.openhab.binding.rfxcom.internal.RFXComHandlerFactory@14d9437’.
2015-11-25 19:22:58 [INFO ] [ome.event.ThingStatusInfoEvent:43 ] - ‘rfxcom:RFXtrx433:A1XR580Z’ updated: INITIALIZING
2015-11-25 19:22:58 [INFO ] [nt.ThingStatusInfoChangedEvent:43 ] - ‘rfxcom:RFXtrx433:A1XR580Z’ changed from UNINITIALIZED to INITIALIZING
2015-11-25 19:22:58 [DEBUG] [.core.common.ThreadPoolManager:141 ] - Created scheduled thread pool ‘thingHandler’ of size 3
2015-11-25 19:22:58 [DEBUG] [.r.handler.RFXComBridgeHandler:96 ] - Initializing RFXCOM bridge handler
2015-11-25 19:22:58 [INFO ] [ome.event.ThingStatusInfoEvent:43 ] - ‘rfxcom:RFXtrx433:A1XR580Z’ updated: OFFLINE
2015-11-25 19:22:58 [INFO ] [nt.ThingStatusInfoChangedEvent:43 ] - ‘rfxcom:RFXtrx433:A1XR580Z’ changed from INITIALIZING to OFFLINE
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (String) A1XR580Z to field ‘bridgeId’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) true to field ‘ignoreConfig’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableUndecoded’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableImagintronixOpus’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableByronSX’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableRSL’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableLighting4’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableFineOffsetViking’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableRubicson’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableAEBlyss’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableBlindsT1T2T3T4’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableBlindsT0’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:69 ] - Skipping field ‘enableProGuard’, because it’s primitive data type and value is not set
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:69 ] - Skipping field ‘enableFS20’, because it’s primitive data type and value is not set
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableLaCrosse’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableHidekiUPM’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableADLightwaveRF’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableMertik’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:69 ] - Skipping field ‘enableVisonic’, because it’s primitive data type and value is not set
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableATI’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableOregonScientific’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableMeiantech’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableHomeEasyEU’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableAC’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableARC’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.e.s.config.core.Configuration:89 ] - Setting value (boolean) false to field ‘enableX10’ in configuration class org.openhab.binding.rfxcom.internal.config.RFXComBridgeConfiguration
2015-11-25 19:22:58 [DEBUG] [.r.handler.RFXComBridgeHandler:106 ] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2015-11-25 19:22:58 [DEBUG] [.r.handler.RFXComBridgeHandler:136 ] - Connecting to RFXCOM transceiver
2015-11-25 19:22:59 [DEBUG] [.c.thing.internal.ThingManager:84 ] - Thing handler for thing ‘rfxcom:RFXtrx433:A1XR580Z’ added.
2015-11-25 19:22:59 [DEBUG] [.c.thing.internal.ThingManager:259 ] - Assigning handler for thing ‘rfxcom:RFXtrx433:A1XR580Z’.
2015-11-25 19:22:59 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:78 ] - Disconnecting
2015-11-25 19:22:59 [DEBUG] [.c.c.r.AbstractManagedProvider:62 ] - Added new element rfxcom:RFXtrx433:A1XR580Z to ManagedThingProvider.
2015-11-25 19:22:59 [INFO ] [o.b.r.i.c.RFXComJD2XXConnector:52 ] - Connecting to RFXCOM device ‘A1XR580Z’.
2015-11-25 19:22:59 [ERROR] [.r.handler.RFXComBridgeHandler:212 ] - Connection to RFXCOM transceiver failed
2015-11-25 19:22:59 [INFO ] [smarthome.event.ItemAddedEvent:43 ] - Item ‘rfxcom_RFXtrx433_A1XR580Z’ has been added.
2015-11-25 19:22:59 [DEBUG] [.c.c.r.AbstractManagedProvider:62 ] - Added new element rfxcom_RFXtrx433_A1XR580Z to ManagedItemProvider.
2015-11-25 19:22:59 [DEBUG] [.c.t.internal.ThingLinkManager:328 ] - Assigning linked group item ‘rfxcom_RFXtrx433_A1XR580Z’ to thing ‘rfxcom:RFXtrx433:A1XR580Z’.
2015-11-25 19:22:59 [INFO ] [.event.ItemThingLinkAddedEvent:43 ] - Link ‘rfxcom_RFXtrx433_A1XR580Z-rfxcom:RFXtrx433:A1XR580Z’ has been added.
2015-11-25 19:22:59 [DEBUG] [.c.c.r.AbstractManagedProvider:62 ] - Added new element rfxcom_RFXtrx433_A1XR580Z -> rfxcom:RFXtrx433:A1XR580Z to ManagedItemThingLinkProvider.
2015-11-25 19:22:59 [DEBUG] [i.DiscoveryServiceRegistryImpl:309 ] - Trying to start 2 scans with an aggregating listener.
2015-11-25 19:22:59 [DEBUG] [i.DiscoveryServiceRegistryImpl:333 ] - Triggering scan for thing types ‘[rfxcom:RFXtrx433, rfxcom:RFXtrx315, rfxcom:RFXrec433]’ on ‘RFXComBridgeDiscovery’…
2015-11-25 19:22:59 [DEBUG] [.e.s.i.r.c.d.DiscoveryResource:88 ] - Scan for binding ‘rfxcom’ successfully finished.
2015-11-25 19:22:59 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:67 ] - Start discovery scan for RFXCOM transceivers
2015-11-25 19:22:59 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:91 ] - Discovering RFXCOM transceiver devices by JD2XX version 66055
2015-11-25 19:22:59 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:98 ] - Discovered 1 FTDI device(s)
2015-11-25 19:22:59 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:145 ] - Discovered RFXCOM transceiver, bridgeType=‘rfxcom:RFXtrx433’, bridgeId=‘A1XR580Z’
2015-11-25 19:22:59 [DEBUG] [s.c.d.internal.PersistentInbox:141 ] - Discovery result with thing ‘rfxcom:RFXtrx433:A1XR580Z’ not added as inbox entry. It is already present as thing in the ThingRegistry.
2015-11-25 19:22:59 [DEBUG] [.b.r.i.d.RFXComBridgeDiscovery:122 ] - Discovery done
2015-11-25 19:22:59 [DEBUG] [i.DiscoveryServiceRegistryImpl:333 ] - Triggering scan for thing types ‘[rfxcom:lighting1, rfxcom:lighting2, rfxcom:lighting3, rfxcom:lighting4, rfxcom:lighting5, rfxcom:lighting6, rfxcom:chime, rfxcom:fan, rfxcom:curtain1, rfxcom:blinds1, rfxcom:security1, rfxcom:camera1, rfxcom:remotecontrol, rfxcom:thermostat1, rfxcom:thermostat2, rfxcom:thermostat3, rfxcom:bbqtemperature, rfxcom:temperaturerain, rfxcom:temperature, rfxcom:humidity, rfxcom:temperaturehumidity, rfxcom:barometric, rfxcom:temperaturehumiditybarometric, rfxcom:rain, rfxcom:wind, rfxcom:uv, rfxcom:datetime, rfxcom:current, rfxcom:energyusage, rfxcom:currentenergy, rfxcom:power, rfxcom:weightingscale, rfxcom:gasusage, rfxcom:waterusage, rfxcom:rfxsensor, rfxcom:rfxmeter, rfxcom:fs20, rfxcom:rfy]’ on ‘RFXComDeviceDiscoveryService’…
2015-11-25 19:23:00 [DEBUG] [i.DiscoveryServiceRegistryImpl:69 ] - Finished 1 of 2 discovery services.
2015-11-25 19:23:09 [DEBUG] [i.DiscoveryServiceRegistryImpl:69 ] - Finished 2 of 2 discovery services.
2015-11-25 19:23:09 [DEBUG] [.e.s.i.r.c.d.DiscoveryResource:88 ] - Scan for binding ‘rfxcom’ successfully finished.
2015-11-25 19:23:42 [DEBUG] [.c.t.internal.ThingLinkManager:376 ] - Removing linked group item from thing ‘rfxcom:RFXtrx433:A1XR580Z’.
2015-11-25 19:23:42 [DEBUG] [.c.t.internal.ThingLinkManager:328 ] - Assigning linked group item ‘rfxcom_RFXtrx433_A1XR580Z’ to thing ‘rfxcom:RFXtrx433:A1XR580Z’.
2015-11-25 19:23:42 [DEBUG] [.r.handler.RFXComBridgeHandler:79 ] - Handler disposed.
2015-11-25 19:23:42 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:78 ] - Disconnecting
2015-11-25 19:23:42 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:95 ] - Close serial port
2015-11-25 19:23:42 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:104 ] - Closed
2015-11-25 19:23:42 [DEBUG] [.r.handler.RFXComBridgeHandler:96 ] - Initializing RFXCOM bridge handler
2015-11-25 19:23:42 [INFO ] [ome.event.ThingStatusInfoEvent:43 ] - ‘rfxcom:RFXtrx433:A1XR580Z’ updated: OFFLINE

after that I’m getting continuously:

2015-11-25 19:30:43 [DEBUG] [.r.handler.RFXComBridgeHandler:106 ] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2015-11-25 19:30:43 [DEBUG] [.r.handler.RFXComBridgeHandler:136 ] - Connecting to RFXCOM transceiver
2015-11-25 19:30:43 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:78 ] - Disconnecting
2015-11-25 19:30:43 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:95 ] - Close serial port
2015-11-25 19:30:43 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:104 ] - Closed
2015-11-25 19:30:43 [INFO ] [o.b.r.i.c.RFXComJD2XXConnector:52 ] - Connecting to RFXCOM device ‘A1XR580Z’.
2015-11-25 19:30:43 [ERROR] [.r.handler.RFXComBridgeHandler:212 ] - Connection to RFXCOM transceiver failed

pauli_anttila · November 25, 2015, 7:06pm

I just created PR to fix RFXCOM binding error logging. Then we should see the reason why connection to transceiver fails.

Meanwhile, you can configure rfxcom transceiver manually from the Paper UI: Setup Wizard -> Blue + -> RFXCOM Binding -> ADD MANUALLY -> RFXCOM USB Transceiver and configure serial port, etc.

-Pali

klex · November 25, 2015, 7:24pm

Many thanks Pauli.

Adding manually is working!

micware · November 27, 2015, 4:37pm

where can I find/download the RFXCOM 2.0 binding for OH2? I like to try it
Thx,

Michiel

klex · November 27, 2015, 7:58pm

Hi Michiel,
Checkout the nightly builds at:
https://openhab.ci.cloudbees.com/job/openHAB2/

pauli_anttila · November 27, 2015, 8:44pm

Hi Alex,

could you test with the latest nightly build, as the connection logging should be fixed now on error situation. Hopefully log could then give hint why discovered transceiver does not work on your environment.

-Pali

klex · November 28, 2015, 1:28pm

Hi Pali,

I’m getting now;
2015-11-28 14:25:20.784 [INFO ] [s.c.d.internal.PersistentInbox] - Added new thing ‘rfxcom:RFXtrx433:A1XR580Z’ to inbox.
2015-11-28 14:25:20.785 [INFO ] [marthome.event.InboxAddedEvent] - Discovery Result with UID ‘rfxcom:RFXtrx433:A1XR580Z’ has been added.
2015-11-28 14:25:27.900 [INFO ] [rthome.event.InboxRemovedEvent] - Discovery Result with UID ‘rfxcom:RFXtrx433:A1XR580Z’ has been removed.
2015-11-28 14:25:27.903 [INFO ] [marthome.event.ThingAddedEvent] - Thing ‘rfxcom:RFXtrx433:A1XR580Z’ has been added.
2015-11-28 14:25:27.907 [INFO ] [ome.event.ThingStatusInfoEvent] - ‘rfxcom:RFXtrx433:A1XR580Z’ updated: INITIALIZING
2015-11-28 14:25:27.912 [INFO ] [nt.ThingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1XR580Z’ changed from UNINITIALIZED to INITIALIZING
2015-11-28 14:25:27.936 [INFO ] [ome.event.ThingStatusInfoEvent] - ‘rfxcom:RFXtrx433:A1XR580Z’ updated: OFFLINE
2015-11-28 14:25:27.941 [INFO ] [nt.ThingStatusInfoChangedEvent] - ‘rfxcom:RFXtrx433:A1XR580Z’ changed from INITIALIZING to OFFLINE
2015-11-28 14:25:28.005 [INFO ] [o.b.r.i.c.RFXComJD2XXConnector] - Connecting to RFXCOM device ‘A1XR580Z’.
2015-11-28 14:25:28.020 [ERROR] [.r.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed: device not opened (3)

trying it with the manual setup again.

micware · November 28, 2015, 10:58pm

Thanks I wil try it as soon as I have openhab 2 running in my test environment.

At the moment I only see “Rest api” and “Classic UI” when I goto http:/IP_openhab2:8080

No Paper UI!!, I have to solve that first.

I have used https://openhab.ci.cloudbees.com/job/openHAB2/421/

Kai · November 29, 2015, 10:18am

Paper UI should be back with the next build https://openhab.ci.cloudbees.com/job/openHAB2/424.

micware · November 29, 2015, 10:36am

Thank you Kai, I wil try it

cschneider111 · December 19, 2015, 3:04pm

I am seeing the same problem in the snapshot build loaded today.
My transceiver is discovered as: RFXtrx433E USB 433.92MHz Transceiver.

It then stays offline though.

I configured the thing manually using this config:
Bridge rfxcom:bridge:usb0 [ serialPort="/dev/ttyUSB0" ] {}
Using this config it worked. I was then able to activate the protocols I need and auto discovery also way able to find intertechno as well as X10 based actuators when I pressed buttons on the remotes.

So I assume the automatic discovery might choose the wrong device name. Using the UI I was not able to see which device it chose. I was also not able to find any config file generated by the discovery. It seems the discovered things are stored somewhere. Does anyone know where?

Btw. This is what I see in the log when starting in debug mode:
2015-12-19 15:04:48 [DEBUG] [.r.handler.RFXComBridgeHandler:106 ] - Checking RFXCOM transceiver connection, thing status = ONLINE
2015-12-19 15:04:34 [DEBUG] [.r.handler.RFXComBridgeHandler:106 ] - Checking RFXCOM transceiver connection, thing status = OFFLINE
2015-12-19 15:04:34 [DEBUG] [.r.handler.RFXComBridgeHandler:136 ] - Connecting to RFXCOM transceiver
2015-12-19 15:04:34 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:78 ] - Disconnecting
2015-12-19 15:04:34 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:95 ] - Close serial port
2015-12-19 15:04:34 [DEBUG] [o.b.r.i.c.RFXComJD2XXConnector:104 ] - Closed
2015-12-19 15:04:34 [INFO ] [o.b.r.i.c.RFXComJD2XXConnector:52 ] - Connecting to RFXCOM device ‘A1YIM80K’.
2015-12-19 15:04:34 [ERROR] [.r.handler.RFXComBridgeHandler:212 ] - Connection to RFXCOM transceiver failed: device not opened (3)

juergen_richtsfeld · January 5, 2016, 9:34pm

@pauli_anttila: Hi, I just started to investigate OH2 and setup my IDE. I’m curious you didn’t include my changes from the OH1 series (especially the ones about synchronization). Is there any reason for that?

pauli_anttila · January 12, 2016, 8:29pm

Linux have the same problem than OS X. Both operating systems provides native driver for FTDI chip which RFXCOM is using. And this prevent to open connection to the device.

I have documented OS X behaviour on the bindings README file, but I didn’t test the binding on Linux system.

Linux behaviour is documented FTDI chip application note: http://www.ftdichip.com/Support/Documents/AppNotes/AN_220_FTDI_Drivers_Installation_Guide_for_Linux%20.pdf

This is unfortunate feature for the binding, which makes the auto discovery pretty useless at least on OS X and Linux. User can disable native drivers, but in most of the cases that does not make sense.

-Pali

pauli_anttila · January 12, 2016, 8:37pm

Hi Juergen,

the reason why I didn’t include your changes is pretty obvious, I started to port binding to OH2 earlier than you made you changes to OH1 binding.

OH2 binding also lack support for some new message types which are introduces lately on the OH1 binding.

curlyel · January 20, 2016, 10:11am

Hi @pauli_anttila,
you’ve mentioned new message types which have been introduced in OH1 binding recently: What are these message types? Are they all listed in the wiki? I’m missing espacially the TEMPERATUR_RAIN implementation in OH1 binding 1.8.0.

I’m wondering, if you are going to implement TEMPERATURE_RAIN message at least in the OH2 binding (f.e. issued by RFXtrx433e when an Alecto WS-1200 is reporting outside temperature and rain gauge reading).

Thanks,
Dirk

Lolodomo · February 2, 2016, 9:06pm

@pauli_anttila: I have a problem with the RFXCOM binding: My things (attached to temperature/humidity Oregon Scientific sensors) remains in state INITIALIZING. Could you provide any help ?

matti_airas · February 14, 2016, 6:04pm

I am having the exact same problem with the latest OpenHAB2 snapshot online binary. The RFXCOM binding gets initialized just fine when added manually. Device auto-detection works beautifully. However, any devices added from the inbox (NEXA switches, some temperature sensors) remain indefinitely INITIALIZING. The same problem also occurs when manually adding things for my NEXA dimmers and such.