HTTP/ OK Server: XMLRPC++ Content-Type: text/xml Content-length: -rpc(). Q. P. M. Connects HomeMatic Interface-Processes ( BidCos-Services, Homegear and CUxD) via XML-RPC or BIN-RPC to ioBroker. I got a new Homematic CCU3 and try now to connect it with the Status: OFFLINE – COMMUNICATION_ERROR Unknown XML-RPC tag: title.

Author: Kell Faujind
Country: Tajikistan
Language: English (Spanish)
Genre: Sex
Published (Last): 13 August 2015
Pages: 235
PDF File Size: 8.11 Mb
ePub File Size: 9.84 Mb
ISBN: 301-3-43213-116-9
Downloads: 85784
Price: Free* [*Free Regsitration Required]
Uploader: Brajar

With Homegear everything works as expected. The binding supports one virtual device and some virtual datapoints. A virtual datapoint Switch to remove the device from the gateway, available in channel 0 for each device. Thanks very much for your time. This binding allows you to integrate, view, control and configure all Homematic devices in Eclipse SmartHome.

OGEMA Drivers :: HomeMatic XMLRPC – javalibs

Note that, for Homegear devices, in contrast to the specification of the Thing above no HG- prefix is needed for the specification of the Type of the Channel. Besides discovering devices that are already known by the gateway, it may be desired to connect new devices to your system – which requires your gateway to be in install mode. Virtual datapoints are generated by the binding and provides special functionality.


Automatic install mode during discovery Besides discovering devices that are already known by the gateway, it may be desired to connect new devices to your system – which requires homematkc gateway to be in install mode. The binding has a gateway type autodetection, but sometimes a gateway does not clearly notify the type. You may use this if you prefer. This is the binding for the eQ-3 Homematic Solution.

The disadvantage is of course, that all events for this channel are delayed. All devices connected to a Homematic gateway. And those “XmlRpc transport error” erros and those “XmlRpcClient error calling event” errors, what could be causing them?

The reconnectInterval disables the aliveInterval and reconnects after a fixed period of time. This is usefull to automatically turn off the datapoint after the specified time. Bridge Configuration There are several settings for a bridge: All required metadata are generated during device discovery. A device may return this failure while fetching the datapoint values.

XmlRpc transport error calling system. For instance during initialization of the binding its DiscoveryService is started and will discover devices that are already connected. A workaround to fix this problem is re-init after 10 messages. The first homematci after Thing is the device type, the second the serial number. If I don’t manually disconnect the connection seems to stay alive. The Type is the device type, channel number and lowercase channel name separated with a underscore.


With Homegear or a CCU, variables and scripts are supported too.

Homematic Binding

The same driver works perfectly well with a CCU1. If you have a slider in a UI and you move this slider to a new position, it jumps around because the gateway sends multiple events rrpc different positions until the final has been reached. For all other gateways you have to manually add a bridge in a things file. As additional parameters you can define a name and a location for each thing. You can combine any option, they must be separated by a comma.

CCU2 with at least firmware 2. Device discovery is supported for all gateways.

Eclipse SmartHome – A Flexible Framework for the Smart Home

XmlRpcClient error calling system. If autodetection can not identify the gateway, the binding uses the default gateway implementation.

If you are using Homegear, you have to add the prefix HG- for each type. Doesn’t the CCU2 has to close the connection?